I am wondering if anyone knows if a certain aspect of migrating VMs in VMM is improved in VMM 2016?
We have 6 Hyper-V hosts which use shared storage on an SMB3 file share. It is not a failover cluster and we do not want it to become a failover cluster.
We can happily do Live Migration in VMM 2012 R2 for those VMs that are actually running.
In HyperV Manager (in Windows Server 2012 R2) we can also do Live Migration using the Move Wizard ("move only the virtual machine"). And the Move Wizard also works brilliantly if the VMs are Off. It finishes in no time and leaves all the VM's files where they are on the file share.
But if we try to Migrate a VM, which is off, using VMM, it mostly does something totally idiotic. It actually copies all of the files from the file share to the origin host and from there to the destination host and from there back to the file share. But since the files are already there, it creates a new folder with "_1" appended to the name. Of course this takes forever for large VMs and leaves weird duplicate folders on the file share.
Does anyone know if this is improved in VMM 2016? VMM should just move the VM and leave all files where they are - just like HyperV manager does.