P2V: cannot sysprep windows 2000 pro

[konenas]

I'm trying to p2v with 3.0.3 VM Converter.

On my machine I have 3 partitions, Windows NT SP6, Windows 2000 PRO SP4 and 2000 server SP4.

My disk partitioning is:

part1 = C: has Windows NT and it is the bootable disk

part2 = D: or K: has Windows 20000 Server

part3 = has a not bootable partition

part4 = G: has Windows 20000 Pro

Recently, I managed to convert W2000 Server and I'm trying to convert W2K Pro but Converter hugs when trying to sysprep it, with the following error:

12:25:49 PM Step 1 : Connecting to VMware Converter Agent on localhost

12:25:50 PM Step 2 : Creating target virtual machine and converting data

12:25:50 PM Configuring parameters for the target virtual machine...

12:25:53 PM Creating target virtual machine...

12:25:55 PM Taking a snapshot of the volume...

12:25:55 PM Cloning source volume c: into target virtual machine...

12:28:45 PM Taking a snapshot of the volume...

12:28:45 PM Cloning source volume g: into target virtual machine...

12:52:20 PM Updating boot sectors...

12:52:21 PM Updating boot.ini...

12:52:21 PM Adjusting drive letter mappings...

12:52:23 PM Failed to adjust drive letter mappings...

12:52:24 PM Step 3 : Preparing target virtual machine

12:52:30 AM ERROR: Unknown error returned by VMware Converter Agent

VMware Converter Agent logs can be found on localhost at G:\WINNT\Temp\vmware-temp\vmware-converter*

VMware Converter Client logs on this computer can be exported, or found at "G:\Documents and Settings\filippos\Local Settings\Temp\vmware-temp\vmware-client*"

VMware Converter logs are stored on a temporary basis, and should be retrieved as soon as possible.

Message was edited by: konenas - more info

[IamTHEvilONE]

konenas,

So what I am gathering here is that you did a conversion against 2 operating systems NT (C:\) + 2000 Pro (G:).

Have you attempted to boot the virtual machine that was created? If you get a 0x0000007b, then you just have to fiddle with a couple things. For example, editing the boot.ini so that there is only 1 OS entry to the correct operating system and partition. The try the configure machine option or check this kbs:

http://kb.vmware.com/kb/1001620

http://kb.vmware.com/kb/1005291

http://kb.vmware.com/kb/1006294

http://kb.vmware.com/kb/1006858

After the conversion is done, sysimage.fault.OsVersionNotFound is the actual error message when trying to reconfigure the virtual machine. It attempted to get extended os info from the partition normal boot partition .... which may confuse it ....

If the above kbs don't help ... I would probably suggest converting only the Windows 2000 pro guest to see if converter can give you a working guest, that's just to see if it will do it normally. Then you can convert the C:\ drive to a vmdk file and attach it to the other virtual machine.

Regards,

EvilOne

1 - Check the documents

2 - Search the forums

3 - Post Question

And remember to award points to those who assist you.

[konenas]

The problem is that my primary partition is named G: and convert when makes new virtual drive doesn't take this into account.

Nothing changed.

[konenas]

My source machine's disk controller is : VT8237 Integrated Serial ATA RAID controller, so HAL expects to find this controller and eventually fails.

Sysprep should change this situation removing VT8237, but it doesn't, when converter stops with that error.

Please help!

[konenas]

These days I bought a new PC and tried once again to prepare a virtual machine. Same problem.

Now Standard disk controller is used.

[continuum]

I would ghost the disk into a new VM.

Once that is done you must beautify the environment for Converter because a triple boot-setup is way to complicated for the over-simplified Converter

___________________________________

description of vmx-parameters:

VMware-liveCD:

[konenas]

I've done it already, but the problem isn't solved, yet.

Today is Dec28. I lost any hope.

[konenas]

and when I try to boot from it, it comes with BSOD 0x7b

Happy new year to all.