baleman2
asked on
Windows Server 2008 R2 Windows Updates / Automatic Restart / effect on VM's
On our Domain Controller (Windows Server 2008), we have a Domain Group Policy setting for scheduling of Windows Updates.
Screenshot is attached showing:
1) Option 4 - Auto Download and schedule the installation
2) Scheduled Install Day - Every Sunday
3) Scheduled Install Time - 02:00
We're using these settings primarily to have our servers install updates and reboot during off-peak hours. In our environment, we have physical boxes running Windows Server 2012 (Host OS) and VM's on these physical boxes running (Guest OS) Windows Server 2012. All servers (physical boxes and VM's) are members of our domain.
Our primary problem resides with the physical boxes. It seems that the download of Windows updates (if available) is occurring nightly on these servers. Given the settings above, we'd expect those updates to be installed "Every Sunday" at "2:00 a.m.". This schedule seems to be working. We'd also expect those servers to reboot after those updates are installed; again, during off-peak hours. However, this is not happening.
We're seeing an automatic reboot of these physical boxes occur at random during the following days after the updates are installed. Our end users are accessing software installed on the VM's which are, of course, running on the physical boxes. When the random reboot of the physical box occurs (more often than not during the work day), our end users are left with no connectivity for as long as it takes the server to reboot. The VM's, as expected, seem to go in to a "Paused" state while the reboot of the physical box occurs.
Once the physical box reboots, the end users are able to connect to software running on the VM's. It sometimes takes 20-30 minutes for this process to finish.
There seems to be an update that resolves this issue for Windows Server 2012. A screenshot, "Hotfix", is also attached.
C--Users-dan-Desktop-GP_Updates_Rest.JPG
C--Users-dan-Desktop-HotFix.JPG
Screenshot is attached showing:
1) Option 4 - Auto Download and schedule the installation
2) Scheduled Install Day - Every Sunday
3) Scheduled Install Time - 02:00
We're using these settings primarily to have our servers install updates and reboot during off-peak hours. In our environment, we have physical boxes running Windows Server 2012 (Host OS) and VM's on these physical boxes running (Guest OS) Windows Server 2012. All servers (physical boxes and VM's) are members of our domain.
Our primary problem resides with the physical boxes. It seems that the download of Windows updates (if available) is occurring nightly on these servers. Given the settings above, we'd expect those updates to be installed "Every Sunday" at "2:00 a.m.". This schedule seems to be working. We'd also expect those servers to reboot after those updates are installed; again, during off-peak hours. However, this is not happening.
We're seeing an automatic reboot of these physical boxes occur at random during the following days after the updates are installed. Our end users are accessing software installed on the VM's which are, of course, running on the physical boxes. When the random reboot of the physical box occurs (more often than not during the work day), our end users are left with no connectivity for as long as it takes the server to reboot. The VM's, as expected, seem to go in to a "Paused" state while the reboot of the physical box occurs.
Once the physical box reboots, the end users are able to connect to software running on the VM's. It sometimes takes 20-30 minutes for this process to finish.
There seems to be an update that resolves this issue for Windows Server 2012. A screenshot, "Hotfix", is also attached.
C--Users-dan-Desktop-GP_Updates_Rest.JPG
C--Users-dan-Desktop-HotFix.JPG
rindi
On servers you should never do the updates automatically. Things can go wrong etc. You should rather have someone do this manually at weekends or similar. That way he can oversee whether everything works as expected, and he can troubleshoot and fix things, or even go onsite if something goes wrong. If you do it automatically chances are that in Monday when all want to resume work, they can't because servers are down.
ASKER
To Rindi:
Come on. We're not even a very large company, but we've got a datacenter with over 40 servers. It's not feasible to manually login, update, and reboot that many machines.
Come on. We're not even a very large company, but we've got a datacenter with over 40 servers. It's not feasible to manually login, update, and reboot that many machines.
Did you try the hotfix in the article you linked to?
Is something running at 2:00am preventing the restart? Have you tried an earlier or later time?
Is something running at 2:00am preventing the restart? Have you tried an earlier or later time?
ASKER
The hotfix was found under an article based on the Windows Server 2012 OS, so I haven't attempted to install on the 2008 Server.
Have tried different times with no success.
Have tried different times with no success.
Your initial problem claims "In our environment, we have physical boxes running Windows Server 2012 (Host OS) and VM's on these physical boxes running (Guest OS) Windows Server 2012"
Why wouldn't you apply this hotfix to your 2012 servers since they have the issue?
Why wouldn't you apply this hotfix to your 2012 servers since they have the issue?
ASKER
Am (incorrectly?) assuming that Domain Group Policy would take precedence over the settings applied by the hotfix?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.