Our standard patch policy includes a weekly scan, and deployment at 1am on 3rd Saturday, and and force reboot after the patching. There are many more nuances then this but that's the jist. What we're running into the occasional servicing stack updates throwing us for a loop - the policy processes, the servicing stack installs, the server reboots, and then we miss the Cumulative Update for the month.
How are you guys handling this? I can only set one reboot and patching action per policy - are you running multiple policies for each server?
Bumpity Bump. Anyone running into this? Finding a way around it?
There are four patches that we have not been able to get installed at all, even manually on the workstations. Are they supposed to be installed in a specific order or something?