How Do You Manage Patching Routine for Devices?

It sounds like Pulseway might not be the best fit for your needs. It can push updates but lacks approval controls, compliance reporting, and proper handling of patch deferrals. If you’re using M365, consider switching to Intune; it's more organized. For a free option, WSUS is a solid choice, but ensure you manage patch testing rigorously—set up testing rings. When your laptops are offline, set a compliance deadline to force installation after a few days. This can really help with that 90% gap you're seeing.

We utilize VMware for our virtual desktops, maintaining and patching a 'gold image' that our users are linked to. This method simplifies the patch management process significantly. Have you considered this approach? It can take the pressure off manual patching.

The key to smoother updates might start with analyzing what's causing the failures. Ideally, your patch process should be fully automated, only requiring users to delay installation during busy hours. I usually recommend patching everything except Mondays and conducting a pilot test of new releases before rolling them out organization-wide. Have you tried piloting updates using virtual machines?

I manage patching using NinjaOne, and honestly, it's been pretty smooth sailing for OS updates! Software updates can be trickier, especially for devices that were set up before we started using NinjaOne. I suggest checking the logs for any issues, and if you're still having troubles, Pulseway's support might give you some useful insights.

We use SCCM for patching, but Microsoft usually rolls out patches once a month. With a massive fleet of 100,000 computers, we’ve built an automatic reboot tool that runs between midnight and 3 AM. It's mostly about handling the reboots. Are your compliance requirements strict enough to adhere to a 14-day update window? That might influence your update strategies.