[GH-ISSUE #267] Update 0.3.3 to 0.4.5 - Agents don't appear to be updating #174

Closed
opened 2026-03-02 02:14:13 +03:00 by kerem · 6 comments
Owner

Originally created by @JerresonJ on GitHub (Feb 2, 2021).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/267

Following update.sh, I tried to update 0.3.3 to 0.4.5 expecting agents to update automatically but they don't seem to be updating? What is the delay on agents updating? Just wait longer here?

Originally created by @JerresonJ on GitHub (Feb 2, 2021). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/267 Following update.sh, I tried to update 0.3.3 to 0.4.5 expecting agents to update automatically but they don't seem to be updating? What is the delay on agents updating? Just wait longer here?
kerem closed this issue 2026-03-02 02:14:13 +03:00
Author
Owner

@wh1te909 commented on GitHub (Feb 2, 2021):

what versions are the agents that are not updating

<!-- gh-comment-id:771909264 --> @wh1te909 commented on GitHub (Feb 2, 2021): what versions are the agents that are not updating
Author
Owner

@JerresonJ commented on GitHub (Feb 2, 2021):

Reporting as 1.2.1

I looked for some method of updating the entire system one step up from 0.3.3 to 0.4.0 first to get 0.4.0 and agent 1.3.0 but the update script from release 0.4.0 updates itself to latest release during run So update.sh forces the entire system to 0.4.5 regardless of where you get the update.sh script from.

<!-- gh-comment-id:771912097 --> @JerresonJ commented on GitHub (Feb 2, 2021): Reporting as 1.2.1 I looked for some method of updating the entire system one step up from 0.3.3 to 0.4.0 first to get 0.4.0 and agent 1.3.0 but the update script from release 0.4.0 updates itself to latest release during run So update.sh forces the entire system to 0.4.5 regardless of where you get the update.sh script from.
Author
Owner

@JerresonJ commented on GitHub (Feb 2, 2021):

I just had two agents jump to 1.3.0, should they jump to 1.4.1 on their own? They just took a while to get up to 1.3.0

<!-- gh-comment-id:771921589 --> @JerresonJ commented on GitHub (Feb 2, 2021): I just had two agents jump to 1.3.0, should they jump to 1.4.1 on their own? They just took a while to get up to 1.3.0
Author
Owner

@JerresonJ commented on GitHub (Feb 2, 2021):

Commenting to close, to prevent any confusion. The agents are updating they are just slow to update, made it look like something was wrong.

<!-- gh-comment-id:771922650 --> @JerresonJ commented on GitHub (Feb 2, 2021): Commenting to close, to prevent any confusion. The agents are updating they are just slow to update, made it look like something was wrong.
Author
Owner

@wh1te909 commented on GitHub (Feb 2, 2021):

that's fine, the rmm will automatically take care of making sure agents first go to 1.3.0 before going any further, even on 0.4.5
so even if you do Agents > Update Agents > select all, even tho the version says 1.4.2 the rmm will still send the agent 1.3.0 first and then next time u do it will send the latest

there have been some changes to agent update recently, please read thru the discussion in ticket #262

<!-- gh-comment-id:771922839 --> @wh1te909 commented on GitHub (Feb 2, 2021): that's fine, the rmm will automatically take care of making sure agents first go to 1.3.0 before going any further, even on 0.4.5 so even if you do Agents > Update Agents > select all, even tho the version says 1.4.2 the rmm will still send the agent 1.3.0 first and then next time u do it will send the latest there have been some changes to agent update recently, please read thru the discussion in ticket #262
Author
Owner

@JerresonJ commented on GitHub (Feb 2, 2021):

This has been excellent work so far. Thanks.

<!-- gh-comment-id:771931546 --> @JerresonJ commented on GitHub (Feb 2, 2021): This has been excellent work so far. Thanks.
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#174
No description provided.