VMM - Migrate VMs from 2008R2 to 2012R2 (Error 2901)
When I try to use Virtual Machine Manager 2012 SP1 to migrate my VMs from our 2008 R2 Hyper V Cluster to my 2012 R2 Hyper V Cluster, I get the following error:
Error (2901)
The operation did not complete successfully because of a parameter or call sequence that is not valid.
The parameter is incorrect (0x80070057)
Recommended Action
Ensure that the parameters are valid, and then try the operation again.
I was able to successfully migrate VMs from a 2012 R2 Hyper V instance to my 2012 R2 Hyper V Cluster without a problem. Any ideas why I am getting a hiccup here?
Thanks!
-IT_Crowd
P.s. I found this question, but didn't think it was related because we don't have VMware in our environment.
http://www.experts-exchang
Error (2901)
The operation did not complete successfully because of a parameter or call sequence that is not valid.
The parameter is incorrect (0x80070057)
Recommended Action
Ensure that the parameters are valid, and then try the operation again.
I was able to successfully migrate VMs from a 2012 R2 Hyper V instance to my 2012 R2 Hyper V Cluster without a problem. Any ideas why I am getting a hiccup here?
Thanks!
-IT_Crowd
P.s. I found this question, but didn't think it was related because we don't have VMware in our environment.
http://www.experts-exchang
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
My scenario was slightly more complicated because I was going from 2008 R2 to 2012 R2. Andrew, I couldn't get your method to work because we were migrating to 2012 "R2", not just normal 2012. When I tried your method, I ended up getting "Hyper-V did not find virtual machines to import from location..."
I found the following website:
http://blogs.technet.com/b/rmilne/archive/2013/10/22/windows-hyper-v-2012-amp-8-1-hyper-v-did-not-find-virtual-machine-to-import.aspx
"VM's that are exported from Windows Server 2008 or 2008 R2 utilized the version 1 WMI namespace which resulted in an .exp file to represent the exported virtual machine. In Windows Server 2012 we introduced a new WMI namespace (version 2 or root\virtualization\v2) which implemented a much better import/export model – allowing you to effectively just copy the virtual machine folder (with the VM’s XML configuration file inside it) as well as the VM’s VHDs and then import that directly. For Windows Server 2012 we maintained the version 1 WMI namespace which allowed for importing of Windows Server 2008/R2 VM’s on 2012.
In Windows Server 2012 R2 we have removed the old version 1 namespace which means we can’t import virtual machines that where exported from Windows Server 2008/R2."
I found the following website:
http://blogs.technet.com/b/rmilne/archive/2013/10/22/windows-hyper-v-2012-amp-8-1-hyper-v-did-not-find-virtual-machine-to-import.aspx
"VM's that are exported from Windows Server 2008 or 2008 R2 utilized the version 1 WMI namespace which resulted in an .exp file to represent the exported virtual machine. In Windows Server 2012 we introduced a new WMI namespace (version 2 or root\virtualization\v2) which implemented a much better import/export model – allowing you to effectively just copy the virtual machine folder (with the VM’s XML configuration file inside it) as well as the VM’s VHDs and then import that directly. For Windows Server 2012 we maintained the version 1 WMI namespace which allowed for importing of Windows Server 2008/R2 VM’s on 2012.
In Windows Server 2012 R2 we have removed the old version 1 namespace which means we can’t import virtual machines that where exported from Windows Server 2008/R2."
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
As a further note, when I tried to stop the service mentioned above, it would "restart" itself within 10 seconds. I needed to disable the service each time I wanted to perform a move. Each time, I moved around 10-20 of our VMs.
Also there were quite a few VMs that needed to have their snapshots/checkpoints removed, so thank you for that comment as well.
Also there were quite a few VMs that needed to have their snapshots/checkpoints removed, so thank you for that comment as well.
ASKER
My solution was slightly different than the proposed solutions by the experts. I have given them partial credit as both of their comments aided in my migration.
ASKER