[GH-ISSUE #1228] Feature Request: Agents should use the TRMM instance to get the new executable when updating #2702

Open
opened 2026-03-14 05:10:01 +03:00 by kerem · 2 comments
Owner

Originally created by @JoachimVeulemans on GitHub (Jul 28, 2022).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1228

Originally assigned to: @wh1te909 on GitHub.

Is your feature request related to a problem? Please describe.
Agents that have access to internet are updating fine. Agents that are in a isolated network can not update automatically. This means I have to upload the new executable to each device and execute a command to update it.

Describe the solution you'd like
If the internet download fails, fall back to downloading the new executable through TRMM. This can be a relay to the online link or the files could be saved in TRMM locally.

Describe alternatives you've considered

  • Manually updating the agents, one by one
  • Writing a script to update the agents, did not work out because almost all ports are closed between some agents and TRMM and Powershell does not support TLS1.2 on Windows 7 without installing a new version of it.

Additional context
/

Originally created by @JoachimVeulemans on GitHub (Jul 28, 2022). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1228 Originally assigned to: @wh1te909 on GitHub. **Is your feature request related to a problem? Please describe.** Agents that have access to internet are updating fine. Agents that are in a isolated network can not update automatically. This means I have to upload the new executable to each device and execute a command to update it. **Describe the solution you'd like** If the internet download fails, fall back to downloading the new executable through TRMM. This can be a relay to the online link or the files could be saved in TRMM locally. **Describe alternatives you've considered** - Manually updating the agents, one by one - Writing a script to update the agents, did not work out because almost all ports are closed between some agents and TRMM and Powershell does not support TLS1.2 on Windows 7 without installing a new version of it. **Additional context** /
Author
Owner

@wh1te909 commented on GitHub (Jul 29, 2022):

This is something I have been wanting to do for a while I will try to prioritize it. Trmm server should download the agent from either github or if code signed, the code signing server and then agent should download it from trmm. This is actually how installing a new agent with a deployment link works so I have already implemented the logic just need to apply it to agent updates.

<!-- gh-comment-id:1198919756 --> @wh1te909 commented on GitHub (Jul 29, 2022): This is something I have been wanting to do for a while I will try to prioritize it. Trmm server should download the agent from either github or if code signed, the code signing server and then agent should download it from trmm. This is actually how installing a new agent with a deployment link works so I have already implemented the logic just need to apply it to agent updates.
Author
Owner

@JSuenram commented on GitHub (Nov 15, 2022):

  • TRMM and Powershell does not support TLS1.2 on Windows 7 without installing a new version of it.

Indeed you can instruct Windows 7 to support TLS 1.2 by registry changes which you can script with TRMM and also Powershell 2 and newer support TLS 1.2 by command....

Add this before your powershell one-liners or in your script.
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12

<!-- gh-comment-id:1315511394 --> @JSuenram commented on GitHub (Nov 15, 2022): > * TRMM and Powershell does not support TLS1.2 on Windows 7 without installing a new version of it. Indeed you can instruct Windows 7 to support TLS 1.2 by registry changes which you can script with TRMM and also Powershell 2 and newer support TLS 1.2 by command.... Add this before your powershell one-liners or in your script. [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/tacticalrmm#2702
No description provided.