{"id":1119,"date":"2015-10-09T12:20:29","date_gmt":"2015-10-09T18:20:29","guid":{"rendered":"http:\/\/www.RiptideHosting.com\/blog\/?p=1119"},"modified":"2019-10-18T15:33:44","modified_gmt":"2019-10-18T15:33:44","slug":"how-to-modify-timing-of-windows-updates-in-2012-2012-r2-to-control-timing-of-updates-and-restarts","status":"publish","type":"post","link":"https:\/\/www.RiptideHosting.com\/blog\/how-to-modify-timing-of-windows-updates-in-2012-2012-r2-to-control-timing-of-updates-and-restarts\/","title":{"rendered":"How to modify timing of Windows Updates in 2012 \/ 2012 R2 to control timing of updates and restarts"},"content":{"rendered":"

Issue:<\/strong>
\nWindows Server 2012 or 2012 R2 reboots after installing Windows Updates during inconvenient times that don\u2019t make sense and you would like to modify settings in a more similar way as with Windows Server 2008 R2. Windows 2012 by default restarts 3 days after the installation of Windows Updates instead of 15 minutes which was used in 2008 R2, BUT the restart counter only begins counting down when a user can see it (see Microsoft Technet link below). In addition, it appears that in some situations the restart counter is temporarily disabled when you logoff\/disconnect. According to the MSDN blog post below, if after 3 days it is detected that critical applications are open or running in the background or the PC is locked, etc., Windows Update will wait to automatically restart the next time a user logs on with a warning that the machine will be rebooted within 15 minutes.<\/p>\n

Although these changes are meant to minimize data loss by providing additional time and warnings prior to reboots, this change in logic can cause confusing timing of reboots of the server and you may wish to have more control over the timing.<\/p>\n

Resolution:<\/strong>
\nIf using Windows 2012, make sure KB2885694 (included in update rollup KB2883201 which is what you will see in installed updates) is installed on your server which should already be there since it was released in year 2013. Windows 2012 R2 already includes these new group policy settings.<\/p>\n

Modify the group policy settings located here. Open Local Group Policy Editor by typing Gpedit.msc. Go to: Computer Configuration \/ Administrative Templates \/ Windows Components \/ Windows Update.<\/p>\n

1. Enable the \u201cConfigure Automatic Updates\u201d group policy. Use value of 4. If you want to select a schedule day & time, do NOT check the automatic maintenance box.<\/p>\n

2. Enable the \u201cAlways automatically restart at the schedule time\u201d group policy. This will allow reboots\/restarts approximately 15 minutes after the updates are installed instead of 3 days later. The restart timer can\u2019t be postponed once started and a restart will occur even if users are signed on.<\/p>\n

These changes should make automatic updates act similar to the behavior experienced in Windows Server 2008.<\/p>\n

 <\/p>\n\n\n\n\n
Scenario<\/strong><\/td>\nRecommended configuration<\/strong><\/td>\n<\/tr>\n
Force updates and restarts at a specific time. For example:<\/p>\n
    \n
  • Install updates on Friday nights at 11PM<\/li>\n
  • Force a restart soon after installation<\/li>\n<\/ul>\n<\/td>\n
Use the Configure Automatic Updates <\/strong>policy:<\/p>\n