Converting a Windows 2000 machine has a bunch of caveats and problems when going from physical to virtual (p2v), using VMware vCenter Converter Standalone.
•VMware Standalone Converter version 4.0.1 (See Additional Info at the end)
•Update Rollup 1 for Windows 2000 SP4 (KB891861)
•Windows 2000 Sysprep tools (Q257813)
•A Windows or Linux LiveCD. I recommend Knoppix (6.4+ - Linux) or Hiren (Windows).
If you need to modify registry keys, use Hiren.
1.Install VMware Standalone Converter version 4.0.1
2.Extract sysprep tools and place them in C:\Documents and Settings\All Users\Application Data\VMware\VMware vCenter Converter Standalone\sysprep\2k
That should be on the same machine that has VMware Converter, not the Windows 2000 server.
* On Windows 2008, the location is C:\Users\All Users\VMware\VMware vCenter Converter Standalone\sysprep\2k (Thanks Anonymous for the tip!)
or C:\ProgramData\VMware\VMware vCenter Converter Standalone\sysprep\2k (thanks Ben!)
3.Either apply the update rollup to the server or extract the update rollup and replace it with the file SCSIPORT.SYS in C:\WINNT\system32\drivers. Applying the update is recommended if the system is stable.
4.If you’re using a static IP on the Windows 2000 server, see this Knowledge Base article.
5.Run the Converter and deploy the agent. If you’re asked to restart, restart then start the VMware Converter service manually before running the Converter again, otherwise it’ll ask you to deploy the agent again.
6.In Step 3: View / Edit Options, Click on the Devices pane and change the disk controller to BusLogic SCSI.
7.Keep the number of processors as is, because if you change it, Windows 2000 won’t auto-detect new CPUs and you’ll need to update the Hardware Abstraction Layer (HAL) on it manually. See KB234558 and KB249694 for more details.
8.In the Networks pane, deselect the option to connect at power on.
9.In the Advanced Options pane, do not select the options to power off the source and select the option to power on the target (VM). Do install VMware tools.
Do NOT select "configure guest preferences for the virtual machine"
With that, you should be set to convert that machine. After the conversion is complete, the VM will start, install VMware tools, then restart. After it comes up you should apply the proper network settings then shutdown and enable the NIC to connect at power on.
Problems and Solutions:
•"disk read error" when starting the virtual machine.
This happens because you have selected the Disk Controller as “Preserve Source” or “IDE” -- you must select “SCSI” -- after doing so, you’ll need to reconvert the machine.
•“KMODE_EXCEPTION_NOT_HANDLED” Blue Screen of Death (BSOD) during boot up.
This happens because Windows 2000 is using the old SCSI driver (SCSIPORT.SYS).
You must boot into a LiveCD and replace the file in the location mentioned above.
This happened to me even after I copied the SCSIPORT.SYS to the target machine before converting.
•After installing the Converter agent, you face problems & restart the Windows 2000 server, then when running converter again, it asks you to re-deploy the agent.
This happens because when the Windows 2000 system comes up again, the Converter agent service isn’t started again.
Open the services console (services.msc in run) and right-click VMware Converter then choose Start. After the service is started, run VMware Converter and it should connect.
•Unable to communicate to the agent.
The network traffic is probably blocked by firewalls that are on the Converter machine, the Windows 2000 target machine or in between. Make sure the firewalls are disabled or port 9089 is allowed to pass through.
•"Inaccessible boot device" Blue Screen of Death (BSOD) during boot up.
This happens due to some misconfiguration of drivers in the registry.
To fix this, run the Converter program again and do a machine reconfiguration only (don't reconvert). Let it install VMware Tools, select "Reconfigure destination virtual machine" and do NOT select "Configure guest preferences for the virtual machine"
If that does not solve your problem, read this thread.