Tech Encounters

Steps to migrate virtual machines from Server 2012 non-clustered to Server 2012 R2 clustered. Prepare the migration At the source server, check the VM settings and the current network Virtual Switch name. A matching Virtual Switch name must exist on the destination server or you will get a nonsensical error message about not being able to connect to the destination server. As a temporary fix where the names do not match...  If both systems are production systems and you don't want to interfere with operations. Go to the destination server and create a new Virtual Switch and assign this to the internal network. This will be sufficient to get the migration working but you will need to swap the adaptor on completion. At the destination server, create the virtual machine folder in the final location on the clustered CSV volume that the machine will finish up in (only the root folder is needed). Do the move At the source server commence a 'Move'. For the destination ...

Moving VMs from Server 2008 R2 to Server 2012 R2 Error message The virtual machine cannot be moved to the destination computer.  The hardware on the destination computer is not compatible with the hardware requirements of this virtual machine.  Virtual machine migration failed at migration source. Apparent cause The destination server does not have a matching named Virtual Network Switch. The error message is a little vague. How to fix Rename one of the virtual switches to have a matching set between the source and destination servers. If the source and destination servers are part of production systems so they can't simply have the Virtual Switch renamed. And if a short pause is acceptable at the end of the migration try this: On the destination server,  Create a new network switch using the internal network and name this to match the source server network.  Start the server move, as the move completes, change the network from Internal to the co...