With Windows Server 2008 R2, Microsoft lessened the feature gap between Hyper-V’s Live Migration and competitors’, but it still has some limitations. Thankfully, you can work around the shortcomings in Hyper-V Live Migration using Windows PowerShell cmdlets.
Hyper-V Live Migration allows admins to move a virtual machine (VM) from one Hyper-V cluster node to another with no noticeable downtime, but some shortcomings still remain, include the inability to live migrate multiple VMs at one time, the lack of scheduling capabilities for live migration, and the inability to migrate VMs based on specific criteria. Hyper-V 3.0, slated for some time in 2012, promises to improve on Hyper-V Live Migration’s limitations, but for now, there are viable workarounds with the help of PowerShell cmdlets.
Using the PowerShell Failover Cluster cmdlet
Most large Hyper-V clustered installations implement System Center Virtual Machine Manager (SCVMM), but for organizations with only one or a few Hyper-V clusters, PowerShell cmdlets can automate and orchestrate the live migration process, while avoiding the additional cost of SCVMM. Most Windows cluster administrators are familiar with Cluster.exe for managing cluster resources, but the PowerShell Failover Cluster cmdlet can accomplish even more live migration functions.
To read the rest of the article see the scripts go HERE.