Building off of the earlier Get-ClusterVM script, I’ve come up with a Rename-ClusterVM PowerShell script.

It sometimes comes as a surprise to people to learn that what Failover Cluster Manager shows you for a virtual machine (in the Roles node) isn’t actually the virtual machine at all. It’s an object known as a “cluster group”. Inside that are two resource objects. The first is a “virtual machine” object and the second is a “virtual machine configuration” object. None of these is the actual virtual machine.

The distinction usually isn’t all that important. But, every once in a while, you run afoul of the system. A common place this occurs is when a VM is exported and then imported as a copy (clone). Hyper-V allows you to have multiple virtual machines with the same name because it tracks them by their IDs. Failover Clustering uses IDs, but doesn’t allow duplicate names. So when a clone is made highly available, Failover Cluster Manager automatically assigns its group and resources with unique names. It ties everything together using the real virtual machine’s identifier.

There are two takeaways from this. The first is that because the virtual machine’s name isn’t connected with its resources, renaming a virtual machine has no effect on the cluster group or resources.

...MORE

Read more: http://www.altaro.com/hyper-v/free-powershell-script-hyper-v-rename-clustervm