Hey everyone, I'm looking for some advice on handling driver management across a variety of devices, specifically HP, Lenovo, and Surface models. We're currently using Autopatch for deploying these drivers with a pretty strict deployment schedule: drivers follow a deferred Windows update policy of two days. While we automatically approve each driver, it can be a real hassle keeping track of them all. We've had issues with users unexpectedly interrupted by driver installations, especially when it comes to graphics or audio drivers during presentations. I'd love to hear if anyone has found effective strategies for notifying users of pending updates and giving them the option to postpone if necessary. I'd also appreciate any tips for managing this smoothly across different manufacturers.
1 Answer
One of the main headaches with driver updates is the reboots they often require. To make things easier, consider establishing a regular review schedule for your updates. If you're manually approving drivers, syncing your approval dates with events like Patch Tuesday might help. For auto approvals, try pausing new updates temporarily before re-approving them at a later date. This way, you can manage the timing better and reduce those annoying interruptions. We're also looking into ways to align updates more effectively with the regular patching cycle to smooth out these issues.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures