It seems like the failures are random when I try to import a Hyper-V VM after exporting from another server. I copy from one lab server to another, use the same path to the VM files (drive letter and folder structure), but I still get import failures.
It the "Failed to import virtual machine" error that so many other people seem to get, as mentioned in http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/thread/24c92ef7-541a-43e7-8e55-549117eb6a82
I searched the net on this quite a bit a few weeks ago, and just can't seem to find the ultimate fix.
Any ideas for me here?
This was a very common issue, but there is a fix now. The problem is related to an GUID set for ScopeOfResidence in the .exp file of the exported VM. There is a manual way to fix this, and an automatic way, In short, when you get this error message:
Error (12700) VMM cannot complete the Hyper-V operation on the <server FQDN> server because of the error: Failed to import the virtual machine from import directory <Directory Path>. Error: One or more arguments are invalid (0x80070057) (Unknown error (0x8005))
You either remove the guid from the VMs .exp file, or you simply run this script on the target Hyper-V host, which fixes the problem auatomically.
http://support.microsoft.com/kb/968968