Ran into an issue trying to convert a Windows 2000 Pro system to virtual. Long story short VMWare Converter stopped supporting Win2K after version 4.1. One noted point: You will not be told this if you try to use a later version. All you get for an error is the classic Microsoft Install error "1603" All that tells you is the install of the client on the Source machine has failed.
There is a work around. You can use VMWare Converter 4.0. Location to download is here. Also here are the Release Notes.
I was able to install Converter 4.o onto my workstation. They ran the Converter Server as a service locally (the install will take care of this). I didnt want challenge the idea of installing two versions of Converter on the vCenter. Once the install was done, I was able to connect to the Source Machine, install the client agent and proceed with the conversion. The remote reboot command from Converter will fail. Just reboot the Source Machine and rerun the job. To do this RIGHT CLICK on the TASK and choose RUN AS COPY. It will ask for the login credentials on all the processes again.
The next part gets tricky. See this VM has been created for VMWare 3.5. Therfore it will need to be upgraded once you have it on the newer host. Installing the VMWare tools to version 7 worked very well. I was able to get the VM on the new version host without worrying about getting the Guest VMWare Hardware upgraded.
-Boston Tech Guy
No comments:
Post a Comment