Jon Snyderman

<div>
Thank you for your (ridiculously) prompt response :). &nbsp; I did see that as an option. &nbsp; But I think that means that I have to do all 8 VMs, and then undo it when I am done. &nbsp; I know that is not so many, but might there be a better way?
</div>


Thank you for your (ridiculously) prompt response :).   I did see that as an option.   But I think that means that I have to do all 8 VMs, and then undo it when I am done.   I know that is not so many, but might there be a better way?

<div>
Yup, all valid points. &nbsp; During a maintenance window, we dont care if they are up or down. &nbsp; We dont really want to have to wait for an unnecessary transition to happen. &nbsp; But your points are valid. &nbsp; &nbsp; <br />
<br />
Never the less, my question is answered. &nbsp; &nbsp;Thank you.<br />
<br />
~Jon
</div>


Yup, all valid points.   During a maintenance window, we dont care if they are up or down.   We dont really want to have to wait for an unnecessary transition to happen.   But your points are valid.    

Never the less, my question is answered.    Thank you.

~Jon

<div>
<div class="content wysiwyg-content">
I have a small 2 host HyperV cluster with about 4 VMs on each host. &nbsp; &nbsp;When we go in to do our monthly updates, we dont want the machines to move. &nbsp; We do them very hands-on. &nbsp; We patch all 8 VMs. &nbsp; Then we shut down or suspend the VMs and do the hosts. &nbsp; &nbsp; No matter what we try including shutting all VMs down, HyperV moves the VMs to the host that is up. &nbsp; How can we temporarily suspend the automated movement of these VMs? &nbsp; <br />
<br />
~Jon
</div>
</div>


I have a small 2 host HyperV cluster with about 4 VMs on each host.    When we go in to do our monthly updates, we dont want the machines to move.   We do them very hands-on.   We patch all 8 VMs.   Then we shut down or suspend the VMs and do the hosts.     No matter what we try including shutting all VMs down, HyperV moves the VMs to the host that is up.   How can we temporarily suspend the automated movement of these VMs?   

~Jon

How do I suspend automated movement of VMs in a HyperV Cluster

Virtualization is the act of creating a virtual (rather than actual) version of something, including (but not limited to) a virtual computer hardware platform, operating system (OS), storage device, or computer network resources. Virtualization is usually the creation of a system that executes separate from the underlying hardware resources, or the creation of an entire desktop for systems located elsewhere, similar to thin clients.

Virtualization

This topic area includes legacy versions of Windows prior to Windows 2000: Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions including Windows Mobile.

Windows OS

Hyper-V is a native hypervisor; it can create virtual machines on x86-64 systems and supersedes Windows Virtual PC as the hardware virtualization component of the client editions of Windows NT. A server computer running Hyper-V can be configured to expose individual virtual machines to one or more networks. Hyper-V Server supports remote access via Remote Desktop Connection. Administration and configuration of the host OS and the guest virtual machines is generally done over the network.

Hyper-V

Servers are computing devices that are similar to desktop computers in that they have the same basic components, but are significantly different in size, configuration and purpose. Servers are usually accessed over a network, and many run unattended, without a computer monitor, input device, audio hardware or USB interfaces. Many servers do not have a graphical user interface (GUI), and are configured and managed remotely. Servers typically include hardware redundancy such as dual power supplies, RAID disk systems, and ECC memory, along with extensive pre-boot memory testing and verification. Critical components might be hot swappable, and to guard against overheating, servers might have more powerful fans or use water cooling.