1 person found this helpful
Is it the same build of Server 2.0 on both hosts?
Typical causes are:
1) Encoding/locale differences - check the .vmx and .vmdk files
2) Path differences in .vmx and .vmdk files between the hosts
3) Case sensitivity of file names in .vmx andf .vmdk files - usually only an issue when moving from Windows hosts to Linux
4) Not copying all files - particularly when there is a snapshot
Check the logs for detailed errors and try SysInternals/Microsoft Process Monitor to see if it can help you pinpoint what it thinks is missing.
Another option it to create a new VM and configure it to use the disk copied from the other host. If this still doesn't work then points at path or encoding issues in the .vmdk.
If none of this helps, please post (attach) the .vmx and .vmdk (the small ascii file) files.
If you found this or any other answer useful please consider the use of the Helpful or Correct buttons to award points.
Probably in my case the reason could be, that I have different partition letters in host1 and host2. I'll have to check that one out when I'll be next to that host.
Additional question - can I clone VMs somehow? In inventory menu I have nothing about cloning.
Cloning is a manual job - just copy all of the files for one VM to another folder and add its .vmx to the inventory via the web ui. When you start it, it will ask if you moved or copied it - select "copied" to ensure unique ids are generated for things like MAC addresses. You will also need to ensure that IP addresses and OS specific things like SIDs (Windows) are unique.
I found solution for this fault . The
problem was in encoding differences within the .vmx and .vmdk files. On
the origin host, the VM machines configured with windows-1256, while on
the destination host the VM machines configured with windows-1252. I
have edited this manually.. and it works
fix-en.JPG 63.8 K
Hah, yesterday I moved one virtual Windows server from one host to another in offline suspend mode. It didn't start, because there was second disc mapped from another VM which was deleted at the same time. And because server was in suspended mode, extra disk could not be removed. After some panic, I opened that main configuration file and choosed second disk value TRUE to FALSE, and the system is now up and running. Damn I was happy to solve it