[GH-ISSUE #465] Feature Request: Unique installation path & service name #2232

New issue

Open

opened 2026-03-14 03:07:54 +03:00 by kerem · 0 comments

kerem commented

2026-03-14 03:07:54 +03:00

Owner

Originally created by @davidrudduck on GitHub (May 3, 2021).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/465

This should maybe be limited to those with a code signed version.

The idea would be that every TRMM server has a unique GUID and when an agent is installed it installs into a unique folder based on that GUID and sets the service name also based on that GUID - aka how ScreenConnect does it.

The goal is to be able to install two vendors TRMM agent side by side on the same machine.

We have run into numerous problems in the past where we have needed to install our CWA agent on machines and the incumbent has theirs own, but we don't want to be pulling theirs off yet. This would alleviate this problem from day one by giving each installation a unique name/install path.

Originally created by @davidrudduck on GitHub (May 3, 2021). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/465 This should maybe be limited to those with a code signed version. The idea would be that every TRMM server has a unique GUID and when an agent is installed it installs into a unique folder based on that GUID and sets the service name also based on that GUID - aka how ScreenConnect does it. The goal is to be able to install two vendors TRMM agent side by side on the same machine. We have run into numerous problems in the past where we have needed to install our CWA agent on machines and the incumbent has theirs own, but we don't want to be pulling theirs off _yet_. This would alleviate this problem from day one by giving each installation a unique name/install path.