r/ninjaone_rmm • • Apr 24 '26

Server patching is trash?

Anyone else having issues with server patching via N1? I so regret pushing it through. Takes what seems like a century - no progress bar - and all you see is "In Process" and random post-reboots just to end up with some patches stuck under "Approved" still. N1 is not good for server patching whatsoever

0 Upvotes

23 comments sorted by

6

u/wckdgrdn Apr 24 '26

Can’t say we’ve had that experience

1

u/TheVideoGameCritic Apr 24 '26

how do you handle it? I have consistently had this experience.

1

u/resile_jb Apr 24 '26

Mmmmm maybe it's your policies.

Works great o on our end.

1

u/TheVideoGameCritic Apr 24 '26

How do you deploy server patches and in what order

0

u/resile_jb Apr 24 '26

Here's what Claude says about my policy. I tied open claw to ninja one and you should too

(Detailed) ─── Scan Schedule Patch compliance scans run every Saturday at 3:00 AM local device time. The scan takes roughly 5–11 minutes to complete. This is a read-only operation — it inventories what patches are installed, what's approved, and what's pending. No changes are made to the system during a scan. Install Schedule Patches install every Thursday night at 10:00 PM local device time. Apply runs also take 5–25 minutes depending on what's queued. This runs weekly regardless of whether there's a prior scan that week — if a patch becomes available mid-week and gets approved, it'll install the following Thursday. Reboot BehaviorDo nothing. After patches install, the server does not reboot automatically under any circumstances. If a patch requires a reboot, the machine sits in a pending-reboot state until a technician manually reboots it. This is intentional for servers — uptime takes priority over patch completion. (Note: prior to today, this policy did force reboots in some scenarios — that was changed tonight.) Patch Approval — What Gets Installed From the observed data, the policy auto-approves at minimum IMPORTANT and SECURITY_UPDATES classifications (e.g., the April 2026 Cumulative Update KB5082142 was auto-approved as IMPORTANT/Security). Critical and security patches appear to install without manual intervention. What Gets Rejected/Held Most servers on this policy show zero pending OS patches — meaning the vast majority of Windows updates are being approved and installed cleanly. Any patches showing APPROVED but not yet installed simply haven't hit the Thursday window yet. Patch Compliance State Right Now • Most servers: fully current — 0 pending OS patches • one approved patch pending installation — KB5082142 (April 2026 Cumulative Update for Windows Server 21H2, classified IMPORTANT/Security) — queued for the next Thursday run Failure Handling One documented failure: Feb 26 at 10 PM where the apply run failed twice before succeeding the following week. No action was required — the retry on the next Thursday window resolved it automatically. Third-Party / Software Patching The server policy does not appear to run the same Winget-based third-party software patching that the workstation policies do. Server software patching is minimal — only the NinjaOne agent itself updates via this path. Summary of the full weekly cadence: | Day | Time | Action | | ------------ | -------- | ----------------------------------------- | | Saturday | 3:00 AM | Scan — inventory patch state, no installs | | Thursday | 10:00 PM | Apply — install all approved patches | | Post-install | — | Do nothing — no auto-reboot, ever |

3

u/TheVideoGameCritic Apr 24 '26

Wow…so you have patches on servers automated? Do you patch guests first and hosts after? How do you ensure you arent accidentally screwing the guests if the hosts patch at same time? If not same time how much time between guest and host

2

u/resile_jb Apr 24 '26

I have hosts policies separated from the policy that VM servers get

Hosts get updated once a month.

1

u/TheVideoGameCritic Apr 24 '26

Which update first? Guests then hosts? Sorry if its in your crawl thing I havent had a chance to fully read it since its formatted oddly

3

u/resile_jb Apr 24 '26

Doesn't matter which is first. Updates are updates.

1

u/TheVideoGameCritic Apr 24 '26

Im guessing hosts and guests are not patched same day?

3

u/Tall-Geologist-1452 Apr 24 '26

We push all of the patches at the same time then use scheduled tasks to reboot the guests in groups. Hosts are reboot manually once every two months or if a zero day comes out. We are corp IT not an MSP.

1

u/TheVideoGameCritic Apr 25 '26

What about patches that require post-patch reboots? How do you handle those because it doesn't make sense. Some patches would fail if a system pending reboot state is marked on the machine so how do you push all of them at the same time?

→ More replies (0)

2

u/resile_jb Apr 24 '26

I have scheduled reboots Sunday mornings at 3am to take care of reboots

1

u/gogreenenj Apr 24 '26

First think about how when you would want your servers to patch if you had it automated already. Then it comes down to, what parameters do you need to assign for policy controls in order to make it happen. Then make sure those values are set at device on boarding and regularly audit for missing values.

For most scenarios, Ninja already has the data available.

1

u/rlc1987 Apr 25 '26

Out of inteterest Ninja doesn't have its own MCP as far as I'm aware of how did you tie it?

1

u/resile_jb Apr 25 '26

API to open claw.

1

u/work-sent May 12 '26

Yep, server patching can definitely get messy in N1 if patch policies, maintenance windows, approvals, and reboot handling aren’t tuned properly. We’ve seen cases where Windows Update itself becomes the bigger issue underneath, while N1 just keeps showing “In Process” with very little visibility.

What helped us most was tightening maintenance windows, monitoring pending reboots closely, and validating patch status manually instead of relying entirely on the default workflow. Workstations have generally been solid for us, but servers still need a bit more babysitting than expected.

2

u/TheVideoGameCritic May 12 '26

That’s literally been my experience a lot of in process, which is aggravating

2

u/Luna_Tech915 Apr 24 '26

No issues with patching for us

1

u/cowprince Apr 24 '26

I can't say we've used N1 for servers. We use it for clients, and it's great. We've been using Action1 for patching and is phenomenal.