Patch Management on Hyper-V Hosts


we developing our patch management policies our server environment.  1 question came regarding strategy patching hyper-v hosts , how ensure vm shutdowns or pausing should addressed.  example, if vm set paused during "automatic stop action", hyper-v host ensure vm in paused state prior rebooting? or shutdown vm if configured?  in instances, such domain controller, think might smarter shutdown dc , restart after hyper-v host has been rebooted.  i'd appreciate thoughts or links patching strategies hyper-v hosts.

thanks!

the 'turn off' option same pull cable on physical machine. 'shut down' option same send shutdown command within vm (start-->shutdown-->shutdown/restart). if define setting 'shut down', hyper-v host should take care of vms, , shut them down properly.

i prefer shutdown vms when host stops/restarts, , configure automatic start 'always start if running when service stopped' 

regards,  



kristian (virtualization , coffee: http://kristiannese.blogspot.com )


Windows Server  >  Hyper-V



Comments

Popular posts from this blog

WIMMount (HSM) causing cluster storage to go redirected (2012r2 DC)

Failed to delete the test record dcdiag-test-record in zone test.com

Azure MFA with Azure AD and RDS