[GH-ISSUE #1672] Movable agents for Non-Persistent Desktops #2989

New issue

Open

opened 2026-03-14 06:10:16 +03:00 by kerem · 0 comments

kerem commented

2026-03-14 06:10:16 +03:00

Owner

Originally created by @samalsalem on GitHub (Nov 9, 2023).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1672

Is your feature request related to a problem? Please describe.

When installing the agent on a template used in a virtual desktop pool with non-persistence, the agent installs and registers new agents over and over again. It is frustrating having to clean up old machines that are no longer online.

Describe the solution you'd like

It would be nice to have the agent "overwrite" the agent record of a machine with a matching hostnames, as virtual desktop hostnames are ABC-nnn where nnn is a sequential number that is recycled. Alternatively, if we can know what key / authentication mechanism is being used to identify the agent to the service, we can back that up by a script that stores / recalls the key / authentication on compose.

Describe alternatives you've considered

We have considered writing an automated script that logs into rmm and removing certain agents from the sites where the pools register in when the agents are offline.

Additional context

When a user logs into a new desktop in a virtual desktop environment, they get a golden image. Our golden image runs the powershell install script on composition from group policy. This leads to hundreds of agents in the website, most of which are offline. We spend quite some time cleaning up the list of agents. We would like the ability to backup / restore the agent identification mechanism to our server. Really, this could be done without further development, If we only understood where the agent id / key / authentication on the agent software is stored, so we could restore it and bounce the service.

Originally created by @samalsalem on GitHub (Nov 9, 2023). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1672 **Is your feature request related to a problem? Please describe.** When installing the agent on a template used in a virtual desktop pool with non-persistence, the agent installs and registers new agents over and over again. It is frustrating having to clean up old machines that are no longer online. **Describe the solution you'd like** It would be nice to have the agent "overwrite" the agent record of a machine with a matching hostnames, as virtual desktop hostnames are ABC-nnn where nnn is a sequential number that is recycled. Alternatively, if we can know what key / authentication mechanism is being used to identify the agent to the service, we can back that up by a script that stores / recalls the key / authentication on compose. **Describe alternatives you've considered** We have considered writing an automated script that logs into rmm and removing certain agents from the sites where the pools register in when the agents are offline. **Additional context** When a user logs into a new desktop in a virtual desktop environment, they get a golden image. Our golden image runs the powershell install script on composition from group policy. This leads to hundreds of agents in the website, most of which are offline. We spend quite some time cleaning up the list of agents. We would like the ability to backup / restore the agent identification mechanism to our server. Really, this could be done without further development, If we only understood where the agent id / key / authentication on the agent software is stored, so we could restore it and bounce the service.