How to Control Automatic Update Behavior in Win 10 Clients from Server 2012 R2
Posted on 2016-10-04
We have some accounting software that users often leave running without posting their changes. If their stations restart due to automatic updates, they lose their work.
What we're looking to accomplish is a way of controlling the behavior on a station by station basis. If the user is conscientious and always posts their changes before the end of a day, we want to allow automatic updating. On other stations, we want the updates to download but let the users decide when to apply.
We used to simply exclude certain stations from the Group Policy for automatic updates and then use the settings built-in to Windows 7 to control the behavior.
Now that Windows 10 has removed the option to download but not install the updates, what's the preferred method for stopping stations from restarting automatically and allowing manual application of updates and restarts? Is there a specific Group Policy template for Win 10 that needs to be applied, or is it built into WSUS?
Environment is all Win 10 Pro stations running the craptacular Anniversary update, along with Server 2012 R2 Essentials.