mirror of
https://github.com/amidaware/tacticalrmm.git
synced 2026-04-26 06:55:52 +03:00
[GH-ISSUE #1228] Feature Request: Agents should use the TRMM instance to get the new executable when updating #2702
Labels
No labels
In Process
bug
bug
dev-triage
documentation
duplicate
enhancement
fixed
good first issue
help wanted
integration
invalid
pull-request
question
requires agent update
security
ui tweak
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/tacticalrmm#2702
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
Additional context
/
@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.
@JSuenram commented on GitHub (Nov 15, 2022):
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