We would like to migrate 40+ VM's from our 2008R2 Hyper-V cluster to our new 2012 Hyper-V cluster.
For this we use the Cluster Migration Wizard found in the Hyper-V2012 cluster manager.
We started a test scenario before actually migrating, to ensure that we can resolve any issues before doing this on our production environment.
Unfortunately we have run into a problem: we believe this may have to do with SCVMM. Let me explain:
When we create a VM on our old cluster and migrate it using the wizard, everything works fine (tested a number of times); we can start the VM. However, when we do the same with a VM that was created using SCVMM on the old cluster, and then migrate it; the VM
won't start.
In the Hyper-V section of the Server manager we see the following events:
19610: 'name' could not be realized due to errors in its configuration file which could not be resolved.
17030: Virtual machine 'TEST-VM02' is assigned to an authorization scope that is not defined in the policy store: 'fb6d85ff-e910-446d-a954-eb844130e239'. The virtual machine will be reassigned to the default authorization scope. (Virtual machine ID A3AE6456-7C29-4DD4-963F-E1C5D2A8436A)
This last error leads us to believe that this may be linked to the fact that SCVMM uses a different folder for the Authorisation Manager store, more details:http://kb.prismmicrosys.com/evtpass/evtpages/EventId_17030_Microsoft-Windows-Hyper-V-VMMS_62946.asp
Unfortunately all our VM's on the old cluster have been created using SCVMM, and as such are affected. It would appear that the Hyper-V Cluster Migration Wizard is not 'SCVMM aware'.
What can we do to continue our migration?
Regards, Paul www.servercare.nl