Update and Reboot of Hyper-V servers


We would like to get info or Microsoft recommendation about hyper-v update. How often is best practice to update because we need to manually turn off VM's (for security reasons and to avoid problems) and reboot hyper-v and that costs our clients a lot. We are updating our servers through Kaseya and we cannot reboot Hyper-V servers every week because of one update (sometimes). 

Hope that someone can share with me best practice or what we can do?

Best regards/Jimmy

May 22nd, 2015 2:49pm

You update your Hyper-V Servers when you decide there is a patch worthy to install.

If you run Hyper-V Server you should have only needed to patch about 4 times in the past year (I know it is not many).

If you run Windows Server Core with Hyper-V the number of patches would have been a bit higher.

And if you run Windows Server Full with Hyper-V you would have had to install most every patch that was issued.

There was a talk on this once that I can't seem to find...

Free Windows Admin Tool Kit Click here and download it now
May 22nd, 2015 3:35pm

+1 to everything that Brian said.

If host-imposed downtime for VMs is unacceptable, the "best practice" is to implement clustering.

May 22nd, 2015 5:08pm

Hi Jimmy,

as Eric said, the best option for you would be to run all the VMs on a Cluster. Like that you can avoid any downtime during a installation of Windows Updates and even automate the installation using Cluster Aware Updating.

Best Regards,

Free Windows Admin Tool Kit Click here and download it now
May 22nd, 2015 5:48pm

Hello Guys,

Thank you for the answers. Our customers are running Windows Server 2012 R2 with Hyper-V and they don't have plan to run cluster any more. They use it before with 2008 R2. So recommendation is to run and install every update and not to wait and install them once a month.

May 25th, 2015 3:42am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics