Move-VM to a Cluster with a Different named Switch not possible through powershell?

Hi guys,

So, we are to move a customers VM’s from one Cluster to another, however the Virtual Switch are named differently on the two Clusters.

I’ve read these articles : 

https://pcortis.wordpress.com/2014/07/18/share-nothing-live-migration-error-could-not-find-ethernet-switch/

https://blogs.technet.microsoft.com/keithmayer/2012/10/04/live-migrate-your-vms-in-one-line-of-powershell-31-days-of-favorite-features-in-winserv-2012-part-4-of-31/

If I chose to move a unclustered VM from Hyper-V Manager - the gui will eventually prompt me to choose the Switch on the destination host/cluster, but if I try to do it from Powershell - the command : Move-VM does not give me the possibility to attach vNIC
to a HA switch on the destination host/cluster with a different name?

Is this by design? Because I cant sit and move hundreds of VM’s from Hyper-V Manager.

Hope you guys have a usefull trick to help me out here 🙂

Read full post . . . .

Go Que Newsroom Categories

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 46 bytes) in /home/content/36/8658336/html/goquecom/wp-includes/wp-db.php on line 1995