[GH-ISSUE #1456] Agent Installation GPO #909

New issue

Closed

opened 2026-03-02 02:19:52 +03:00 by kerem · 3 comments

kerem commented

2026-03-02 02:19:52 +03:00

Owner

Originally created by @Len-SVACS on GitHub (Mar 21, 2023).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1456

Pretty new to Tactical so forgive me if this has been brought up previously.

Installing the Agent via group policy can be quite cumbersome. The ability to not have the agent expire would go along way here. If security is the main reason for this having an expiry at all to begin with then in this scenario you could potentially make the agent not expire, but then have a toggle to allow the agents to connect back into Tactical. Essentially a toggle to either accept or deny agents upon installation if the toggle is on/or off.

Originally created by @Len-SVACS on GitHub (Mar 21, 2023). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1456 Pretty new to Tactical so forgive me if this has been brought up previously. Installing the Agent via group policy can be quite cumbersome. The ability to not have the agent expire would go along way here. If security is the main reason for this having an expiry at all to begin with then in this scenario you could potentially make the agent not expire, but then have a toggle to allow the agents to connect back into Tactical. Essentially a toggle to either accept or deny agents upon installation if the toggle is on/or off.

kerem closed this issue

2026-03-02 02:19:52 +03:00

kerem commented

2026-03-02 02:19:53 +03:00

Author

Owner

@wh1te909 commented on GitHub (Mar 21, 2023):

if you are using the deployment link method (which you probably are for GPO deployments) then set the expire year to 3030. if you are using the dynamic, powershell or manual method then just set expire hours to 999999. now you have agents that don't expire :)

@wh1te909 commented on GitHub (Mar 21, 2023): if you are using the deployment link method (which you probably are for GPO deployments) then set the expire year to 3030. if you are using the dynamic, powershell or manual method then just set expire hours to 999999. now you have agents that don't expire :)

kerem commented

2026-03-02 02:19:53 +03:00

Author

Owner

@Len-SVACS commented on GitHub (Mar 21, 2023):

Great Idea. Thank you. I have tried setting the expiry higher but at the time the installation via GPO seemed to be hit and miss, this was most likely just my environment however. The user accounts on the devices I'm trying to deploy to are not administrators unfortunately and the agent requires admin

@Len-SVACS commented on GitHub (Mar 21, 2023): Great Idea. Thank you. I have tried setting the expiry higher but at the time the installation via GPO seemed to be hit and miss, this was most likely just my environment however. The user accounts on the devices I'm trying to deploy to are not administrators unfortunately and the agent requires admin

kerem commented

2026-03-02 02:19:53 +03:00

Author

Owner

@silversword411 commented on GitHub (Mar 22, 2023):

I think this is solved, closing. Post if needs reopening

@silversword411 commented on GitHub (Mar 22, 2023): I think this is solved, closing. Post if needs reopening

kerem referenced this issue

2026-03-02 02:24:43 +03:00

[PR #909] [MERGED] Update get_mesh_exe_url command to use MESH_WS_URL for docker #1780

kerem referenced this issue

2026-03-14 07:35:58 +03:00