1 person found this helpful
Usually, the first thing to do is uninstall any VMware Converter products on that Windows 2000 Server, and then install a fresh copy of 3.0.3. You may be required to reboot after the uninstall, and definitely after the reinstall.
Make sure you are up to day on service packs, if applicable, and ensure that nothing is occupying the server. This is a little harder because MSCONFIG is not in Windows 2000 by default, but we just want to make sure an application is not locking files on the system. i.e. Anti-virus, Database software, etc. Disable as much as you can.
Try the clone again using the Version of 3.0.3 installed directly on the server that you want to convert. If it fails again, export the logs via the option in the file menu and attach it to this thread.
If you get the same error again, and you have access to the Cold Clone CD (licensed version of converter) ... that may be a good way to go.
PS: FYI about the Converter Logs:
vmware-client.log (capture a record on the source)
- Contains actions taken on the Converter application are written here.
- Does NOT contain import/reconfiguration information
- Is stored under the user’s (the user who ran the Converter Application) temp directory.
vmware-converter.log (capture a record on the system where Converter is installed)
- Contains information regarding the import/reconfiguration steps taken by the agent when converting the physical/virtual machine.
- Is available in the Source Physical Machine OS’s temp directory (C:\Windows\Temp\vmware-temp)
thanks for the info - I figured out that I had to perform a Custom install of the Converter and select to only install the Converter agent portion of it. (while logged on with the local admin account of course!)
Then after a reboot, the P2V worked fine!