VMware Cloud Community
wb0808
Contributor
Contributor

Problem Converting Windows 2000 system

I have been trying for the last couple of days to convert some of my Win2K machines. I have done the following.

1. reboot

2. Uninstall and re-install client

3. Run Chkdsk to look at the volume.

4. Reapplied service pack 4

This is the error I keep getting has anyone seen this and know how to fix it

\[#1] \[2007-03-30 23:27:11.309 'App' 892 info] \[extendedOsInfo,178] Returning OS as win2000AdvServGuest

\[#1] \[2007-03-30 23:27:11.309 'App' 2108 warning] \[importSource,319] Unable to determine the guest OS from metadata: no metadata for sources of this type

\[#1] \[2007-03-30 23:27:11.356 'App' 2108 verbose] \[vmiTask,109] VmiCheckDestParamsTask::task\{3}: returning results:

\[#1] (sysimage.CompatibilityWarning) []

0 Kudos
1 Reply
esiebert7625
Immortal
Immortal

Are you a local admin on the server? Any software raid? Dynamic disks? Anything unusual in your boot.ini file? How many partitions do you have?

I've used some file and registry monitoring utilities to see what Converter is doing when it tries and determines the Source OS. What I see is that it looks at the boot.ini. So make sure your boot.ini is in the root of C:\ and the user you are using to login to that server has access to it. It also makes registry calls to determine the OS. It reads the below values from the registry, check to see if you have all these and they are set correctly.

HKLM\SYSTEM\ControlSet001\Control\ProductOptions\ProductType "WinNT'

HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\CSDVersion "Service Pack 2"

HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\CurrentType "Uniprocessor Free"

HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\CurrentVersion "5.1"

HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProductName "Microsoft Windows XP"

HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SystemRoot "C:\Windows"

Also to help you solve this you can use some utilities to see exactly what Converter is doing when it tries to read your source OS and why it is failing. I used these on a working copy of Converter and was able to see exactly what files and registry settings it was accessing. The process that does the actual conversion is called vmware-ufad.exe. The other process Converter.exe is the main program. So if you monitor the vmware-ufad.exe process when you press the import button you will see what it is doing. The tool to use for this is called Process Monitor. You can set a filter to only monitor the vmware-ufad.exe process. Hopefully you will see exactly what it is trying to read on the file system and registry and see if there are any failures. You can also use Filemon and Regmon or Process Explorer, but I've found Process Monitor to be adequate.

Process Monitor:

http://www.microsoft.com/technet/sysinternals/ProcessesAndThreads/processmonitor.mspx

Process Explorer:

http://www.microsoft.com/technet/sysinternals/ProcessesAndThreads/ProcessExplorer.mspx

FileMon:

http://www.microsoft.com/technet/sysinternals/FileAndDisk/Filemon.mspx

RegMon:

http://www.microsoft.com/technet/sysinternals/SystemInformation/Regmon.mspx

0 Kudos