[GH-ISSUE #216] Server 2019 - Patching Behavior & Online/Offline not working. #2076

New issue

Closed

opened 2026-03-14 02:22:17 +03:00 by kerem · 3 comments

kerem commented

2026-03-14 02:22:17 +03:00

Owner

Originally created by @JerresonJ on GitHub (Dec 19, 2020).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/216

Patching Behavior

Clean install of Server 2019, brand new machine.
No server roles configured, it does nothing right now but hold files on a shared drive.

Patch Behavior is weird...
RMM shows they were installed and has a timestamp. However Timestamps are off a bit, they jumped from 23:30 to 05:14 in the same update run and reboots. The only thing was the server crossed midnight during the patching but I would expect it to go 23:30 ish to 01:00 not jump to 05:00 hours.

RMM will show reboot pending but even after a reboot all patches still show as "pending install" in Windows Update.
I ran patch scan and install until there were no more shown as pending and no reboot pending was shown.
Then I rebooted manually & still the patches show as "pending install" in Windows Update.
So I went ahead and clicked install in windows update and it zipped through them and cleared the list. Then I clicked check updates again and it reported all up to date.

So it appears the updates were actually installed completely via RMM but Windows Update didn't get the memo here and kept showing them until I manually clicked to install them.

Is this due to how RMM handles patches or is it a Microsoft disconnect between patching via different commands vs the GUI options?

Online / Offline

Online/Offline doesn't work for this same server. MeshCentral will show when it is offline but no matter how many times I refresh RMM it still shows it green and online. Anything to check here?

Thanks.

Originally created by @JerresonJ on GitHub (Dec 19, 2020). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/216 **Patching Behavior** Clean install of Server 2019, brand new machine. No server roles configured, it does nothing right now but hold files on a shared drive. Patch Behavior is weird... RMM shows they were installed and has a timestamp. However Timestamps are off a bit, they jumped from 23:30 to 05:14 in the same update run and reboots. The only thing was the server crossed midnight during the patching but I would expect it to go 23:30 ish to 01:00 not jump to 05:00 hours. RMM will show reboot pending but even after a reboot all patches still show as "pending install" in Windows Update. I ran patch scan and install until there were no more shown as pending and no reboot pending was shown. Then I rebooted manually & still the patches show as "pending install" in Windows Update. So I went ahead and clicked install in windows update and it zipped through them and cleared the list. Then I clicked check updates again and it reported all up to date. So it appears the updates were actually installed completely via RMM but Windows Update didn't get the memo here and kept showing them until I manually clicked to install them. Is this due to how RMM handles patches or is it a Microsoft disconnect between patching via different commands vs the GUI options? **Online / Offline** Online/Offline doesn't work for this same server. MeshCentral will show when it is offline but no matter how many times I refresh RMM it still shows it green and online. Anything to check here? Thanks.

kerem closed this issue

2026-03-14 02:22:22 +03:00

kerem commented

2026-03-14 02:22:28 +03:00

Author

Owner

@JerresonJ commented on GitHub (Dec 19, 2020):

Possibly related to here #191
But I have confirmed the timezone is correct on the server2019 and the RMM Server.
RMM Server is America/New_York
Default Agent Timezone is America/New_York
Server2019 is (UTC-05:00) Eastern Time (US & Canada)

Online/Offline
I think is simply because the server rebooted before the 6 minute yellow threshold. Testing Theory, turned off Tactical Agent Service to see if it reports yellow in 6 minutes.
Confirmed
Issue was due to server rebooting faster than the 6 minute threshold.

@JerresonJ commented on GitHub (Dec 19, 2020): Possibly related to here #191 But I have confirmed the timezone is correct on the server2019 and the RMM Server. RMM Server is America/New_York Default Agent Timezone is America/New_York Server2019 is (UTC-05:00) Eastern Time (US & Canada) **Online/Offline** I think is simply because the server rebooted before the 6 minute yellow threshold. Testing Theory, turned off Tactical Agent Service to see if it reports yellow in 6 minutes. _Confirmed_ Issue was due to server rebooting faster than the 6 minute threshold.

kerem commented

2026-03-14 02:22:33 +03:00

Author

Owner

@wh1te909 commented on GitHub (Dec 30, 2020):

Hi yes the rmm installs updates using the windows update API which doesn't appear to sync automatically with the GUI. Am rewriting the windows update module though so we'll see if it still happens once that's done.

@wh1te909 commented on GitHub (Dec 30, 2020): Hi yes the rmm installs updates using the windows update API which doesn't appear to sync automatically with the GUI. Am rewriting the windows update module though so we'll see if it still happens once that's done.

kerem commented

2026-03-14 02:22:38 +03:00

Author

Owner

@JerresonJ commented on GitHub (Dec 30, 2020):

Comment to close - Questions and Issues addressed.

@JerresonJ commented on GitHub (Dec 30, 2020): Comment to close - Questions and Issues addressed.

kerem referenced this issue

2026-03-14 06:55:48 +03:00

[GH-ISSUE #2076] SSO Microsoft: Error AADSTS500113: No reply address is registered for the application. #3237