N00b2015
asked on
Server 2012 reboots automatically after Windows updates
Hi all,
Thank you for taking the time to help a noob out!
Basically, we have a couple of Windows 2012 R2 servers which reboots after Windows Updates have been downloaded/installed. Yes, i know, it's what they do but*, i'd prefer it if they did it atleast out of hours, such as midnight or something! Another issue is when I remote onto the server during the day, I get a 15 second counter which notifies me the server will reboot, which it does! It may be that, every time I RDP onto the server i get the counter and it reboots other than it doing it randomly after updates but either way, i want it to stop and have it set to reboot only around certain times. I have googled this and have read it may be possible to do this via registry?
Thank you for taking the time to help a noob out!
Basically, we have a couple of Windows 2012 R2 servers which reboots after Windows Updates have been downloaded/installed. Yes, i know, it's what they do but*, i'd prefer it if they did it atleast out of hours, such as midnight or something! Another issue is when I remote onto the server during the day, I get a 15 second counter which notifies me the server will reboot, which it does! It may be that, every time I RDP onto the server i get the counter and it reboots other than it doing it randomly after updates but either way, i want it to stop and have it set to reboot only around certain times. I have googled this and have read it may be possible to do this via registry?
To william's point,
how are the servers managed? is it a member of a domain, do you have an internal WSUS server where you can approve updates that will then be downloaded locally and scheduled for install........
or your setup check with MS and when they release updates it downloads, installs and reboots when needed (3am)
how are the servers managed? is it a member of a domain, do you have an internal WSUS server where you can approve updates that will then be downloaded locally and scheduled for install........
or your setup check with MS and when they release updates it downloads, installs and reboots when needed (3am)
ASKER
Thank you so much William!
So, I have done point 5 and enabled "No auto restart..". You mentioned to enable "Configure Automatic updates" and set policy to 2. However, you lastly mentioned to tell the server to search and install for updates during off hours. Do you mean by setting the Configure Automatic Updates policy to 4 ( 4 = Automatically download updates and install them on the schedule specified below)? As that would conflict previously setting to 2?
Arnold - Thank you. It is a member of a domain but we do not use WSUS.
So, I have done point 5 and enabled "No auto restart..". You mentioned to enable "Configure Automatic updates" and set policy to 2. However, you lastly mentioned to tell the server to search and install for updates during off hours. Do you mean by setting the Configure Automatic Updates policy to 4 ( 4 = Automatically download updates and install them on the schedule specified below)? As that would conflict previously setting to 2?
Arnold - Thank you. It is a member of a domain but we do not use WSUS.
Sorry, yes, I should have mentioned those were just various steps you could be taking to mitigate the impact the reboots will have. Setting up a scheduled restart time via a task would likely be your best bet for controlling when the update happens even with the settings you've made to stop it from rebooting while logged in. You can do so easily by following the steps listed in the first suggestion. What I would do is just set a universal time that the server will restart (every night at 3am for instance).
ASKER
Thank you William. Very helpful.
I was wondering... Would it be a problem if I were to set the "Configure Automatic Updates" policy to 4? As it appears to be similar as the scheduled task?
" 4 = Automatically download updates and install them on the schedule specified below.
Specify the schedule using the options in the Group Policy Setting. If no schedule is specified, the default schedule for all installations will be every day at 3:00 AM. If any updates require a restart to complete the installation, Windows will restart the computer automatically. (If a user is signed in to the computer when Windows is ready to restart, the user will be notified and given the option to delay the restart.)"
I would like to avoid using a schedule task for other reasons but could you see any implication if i did the above?
I was wondering... Would it be a problem if I were to set the "Configure Automatic Updates" policy to 4? As it appears to be similar as the scheduled task?
" 4 = Automatically download updates and install them on the schedule specified below.
Specify the schedule using the options in the Group Policy Setting. If no schedule is specified, the default schedule for all installations will be every day at 3:00 AM. If any updates require a restart to complete the installation, Windows will restart the computer automatically. (If a user is signed in to the computer when Windows is ready to restart, the user will be notified and given the option to delay the restart.)"
I would like to avoid using a schedule task for other reasons but could you see any implication if i did the above?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ahh, that makes complete sense. Well, i think i can fiddle around from the information you have given me and see what I can do from there. Thanks very much for your time and help.
Sure thing, no problem at all. If you run into anymore trouble, please don't hesitate to ask for help.
http://westarinfo.com/information-technology/how-to-set-up-a-scheduled-reboot-on-windows-server-2012/
You can also stop updates with a GPO by following these steps:
1.Press Windows Key+R to open the run prompt.
2.Type "gpedit.msc" and press enter.
3.In the "Local Group Policy Editor", navigate to Computer Configuration > Administrative Templates > Windows Components > Windows Update.
4.Enable the "Configure Automatic Updates" policy and set it to "2".
5.Enable the "No auto-restart with logged on users for scheduled automatic updates installations" policy.
The above will stop the reboot with users logged into the server.
The last thing you would want to do is simply tell the server to search for and install updates during off hours. Just tell it to do so around 3AM or something along those lines.
These steps should at least point you in a direction for mitigating the impact updates will have on your day to day operations.