I use WSUS v3. I've been experimenting via GPO to have my WSUS server automatically install patches, and reboot the clients. I have half a dozen test VMs - Win 2012, Win 2008 (not R2), Win 7, Win 2008 R2.
As a test, I approved a bunch of updates, and set the GPO to install Wed at 2PM. Each of the clients did show that there were updates waiting - Win 2008 R2: 43 updates, Win 2012 - 8 Updates, Win 2008 - 7 updates, Win 7 - 12 updates. All good so far. Here's the odd thing - the Win 2012 server applied patches and rebooted just fine. The Win 7 and Win 2008 applied patches, but didn't reboot (which I found odd, but is possible, I suppose). The Win 2008 R2 servers didn't seem to do anything. I manually rebooted them, and then they started installing their 40+ patches. But why? I looked in the event logs before rebooting them, and didn't see any errors - nothing GPO related, no update related. So what's up with just those 2? I ran a GPO Modeling Wizard, and it was the same for all test clients - Configured for Automatic Updates, every Wed, 2 PM. And that's it, no other update options set in the GPO. So why did just these 2 not apply the patches and reboot? And instead didn't apply them until I manually rebooted them. Confusing, it is ... I can't roll this out for 120 clients this way. They've all got to install and reboot, if necessary, on schedule. And regardless of anyone logged in, BTW. Where did I go wrong, or where should I start looking?
