These WSUS settings are 'computer policy', so this must happen before they can be applied to the system based on the group it's in, in AD. When you add a computer or server to a group in Active Directory, a reboot is required before the system will know it's in that new group.

You can change this easily in the group policy and do a gpupdate /force on the effected systems to make it take effect before Saturday for example comes around.ġ. then if you have it set for Saturday at 3am, the updates will install on the systems at 3am, and then will reboot immediately after updates finished, or 15 minutes afterwards if someone is logged in. If you already have the correct day and time set in the group policy of when you want this to happen, all you need to do is approve the updates you want, to the WSUS groups you want them to apply to. You haven't yet approved any updates, but now the time has come when you want to do a planned Server 2016 or Win10 update and reboot. You have some test Win10 computers and some test Win2016 servers in the appropriate AD groups, and have the appropriate Group Policies configured as above and they are being applied correctly to the computers and servers you specified. Okay, so you've followed exactly up to this point. Again, use the proper tools for the job if you want the benefits of control and configurability. The same reason you would use a Server OS to host AD or File Shares, versus doing it with local user accounts and a Win7 file server. but I ask you back, if you have a machine or server that is so important you need to control the updates/reboots, why don't you have the infrastructure to support it? How much can your data be worth if you can't properly support it? If you want control, use the proper products/tools. You may argue why should you need to have WSUS to control updates if you only have one server or one Win10 machine. If you want granular and complete control over updates and reboots for Windows 10 and Windows Server 2016, then this How-to is for you. If anyone notices if/when it gets fixed before I do, please let me know in the comments and I'll update this status! Thanks. * Windworks perfectly fine, the above issue is with 1607 *. However, the below methods in the How-to can and will stop updates completely. The PC's still show up in WSUS, but do not show that updates are needed, and Win10 PC's may not get updates from the WSUS server. Windows 10 version 1607 (anniversary update) seems to have some actual issues with WSUS that still haven't yet been ironed out by Microsoft.

I no longer have any Win10 machines running pre-1607, so I can't comment on those. It's been a while and thought I should finally update this to let everyone know all seems to be working well between WSUS, Win10, and Server 2016 without issue.

Perforce client windows server 2016