BatchPatch. It is a cheap third party tool. We use it to manage all our Windows patching. You can setup jobs that: Download, install, and reboot, check for new updates, download, install, and reboot, install a new version of AV software that you have packaged, update registry keys, check for updates, and the list goes on.
We've been using it for about 4 years and it's been EASILY the best software purchase in my 25+ years in IT. On Mon, Jul 24, 2017 at 10:59 AM, Michael Leone <oozerd...@gmail.com> wrote: > I'd like some advice, please. So this past weekend, we applied our monthly > updates, and for the first time, half of my servers applied them using a > scheduled installation time from my WSUS v3 server. And yes, the patches > were applied, the servers rebooted, no human intervention needed. Yay! > > BUT ... some servers then came back saying that another patch needed to be > installed (apparently on some servers, the June Monthly Quality update > failed, hence why it's still waiting to be installed). What that means is > that this coming Sunday, those servers will apply this waiting patch and > reboot (which I don't want to happen, because it's outside of the monthly > maintenance window). > > I might be able to apply that patch offhours, before next Sunday. > > So how does everyone else handle this issue - the issue of installing a > patch, and then having another patch now needing to be installed, or - as > with me - a patch that failed to install the first time attempt to re-try? > So how to avoid having the server reboot the next weekend, during a > non-scheduled window? > > Thanks >
