Skip to content

add /KEEPMESH uninstaller switch to leave the mesh agent installed - #91

Open
Deenyoro wants to merge 1 commit into
amidaware:developfrom
Deenyoro:feat/uninstall-keepmesh
Open

Deenyoro wants to merge 1 commit into
amidaware:developfrom
Deenyoro:feat/uninstall-keepmesh

Conversation

@Deenyoro

@Deenyoro Deenyoro commented Nov 2, 2026

Copy link
Copy Markdown

Adds a /KEEPMESH switch to the Windows uninstaller so the RMM agent can be removed without also removing the mesh agent:

"C:\Program Files\TacticalAgent\unins000.exe" /VERYSILENT /KEEPMESH

This helps when the mesh agent is managed by a separate MeshCentral server, or when only the RMM agent should come off a machine. It's the uninstall counterpart to -nomesh (see also amidaware/tacticalrmm#2191). Without the switch, the uninstall does exactly what it does today. The agent and the server aren't changed.

Notes:

  • The mesh -fulluninstall and the Mesh Agent folder removal moved from [UninstallRun]/[UninstallDelete] into CurUninstallStepChanged. A Check: on those sections is evaluated at install time, so it can't see the uninstaller's command line. I tested that variant and it still removed mesh with /KEEPMESH.
  • UninstallLogMode=overwrite: Inno appends to the existing uninstall log on update. So without this, an agent updated from an older version keeps the old meshrm entry, and the mesh agent is still removed even with /KEEPMESH. {app} is already deleted as a whole, so nothing else depends on the appended entries.

Tested on Windows 11 with Inno Setup 6.7.4. I used a copy of setup.iss with its own AppId, paths and process names (so it couldn't touch the real agent on the box), with stub exes standing in for tacticalrmm.exe and meshagent.exe:

install path uninstall args mesh kept TacticalAgent dir / ARP entry removed
fresh /KEEPMESH yes yes
fresh /keepmesh yes yes
fresh (none) no yes
fresh /KEEPMESHX no yes
current develop installer, then this one /KEEPMESH yes yes
current develop installer, then this one (none) no yes
develop, then this one twice /KEEPMESH yes yes
this one twice (none) no yes
current develop installer only (baseline) (none) no yes

Useful when the mesh agent is managed by a separate MeshCentral, or when only the RMM agent should come off a machine. Without the switch the uninstall behaves as before. UninstallLogMode=overwrite so agents updated from older versions don't keep the old mesh uninstall entry.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant