Hi There,
We've had this issue for a while now with 2012 R2 servers, but as we are currently migrating our remaining 2008 servers to Server 2016, this is increasingly becoming an issue. We've never had a problem with scheduling updates for 2008 servers so that they
update and restart out of production hours. However, servers from 2012 onward appear to ignore this setting.
The standard Group Policy setting we've had until now has been -
Configure Automatic Updates, option 4 selected with a scheduled time set weekly for 2am
Allow automatic updates immediate installation - Disabled
Reschedule automatic updates - Disabled
Set intranet updates service location - set to our local WSUS server
We've had numerous server restarts during production hours which have had a serious impact on the business and as a result of this, we've had to resort to manual updates only for critical servers, which is not really a practical solution going forward.
Questions -
1. Should Configure automatic updates option 4 work on 2012 and 2016 servers, and if not, why not?
2. What Group Policy configuration can we apply to 2012/ 2016 servers that will produce predictable restart behaviour?
3. Should we manage different servers with different OSs on different Group Policy configurations?
4. Do we need to test Group Policy for updates on all future iterations of Windows servers?
5. The setting Configure Automatic updates option 4 appears to force the setting for Turn off auto-restart for updates during active hours to the default setting of 08:00-17:00 - should this be the case?
6. Should the active hours setting actually work on 2012 Servers?
I appreciate any help you can give on this.
Regards,
Richard