P to V windows 200 server error 1,603

[Gonzouk]

Hello,

I am trying to P to V and old Windows 200 server, but I get the below error. I have manged to P to V windows 2003 and 2008 servers without any issues, this is out only Windows 2000 to do, what can I do?

Thanks

[FranckRookie]

Hi Gonzouk,

If you already converted this machine and removed the agent at the end of the process, you need to restart the server before trying another P2V. You can also have a look at this kb.

Hope it helps.

Regards

Franck

[Gonzouk]

Hi,

I got this error on my first ever attempt and have uninstall the vm converter and restarted many times, but still get the error. Can I manually install the converter from the server itself?

[FranckRookie]

You can install the Standalone converter on the server itself. You can even use the Converter boot CD if the hot P2V doesn't work.

Which version are you using? I read some articles recommending using the old 3.x version for 2000 servers.

[Gonzouk]

Hi, I'm looking on the CD, what would be the name of the file to run? I have found a folder called "VMware Tools".

[golddiggie]

You download the standalone VMware converter from the web site... Then install it onto the system you want to convert...

VMware VCP4

Consider awarding points for "helpful" and/or "correct" answers.

[FranckRookie]

What CD are you looking at? VMware vCenter Converter Standalone is a separate download.

[bshubinsky]

I had the same issue. I still haven't found a way around it and I've tried each one of the suggestions listed. I ended up doing a backup of the server and restoring it onto a newly created VM.

[monderick]

ran into the same issue a few months ago:

http://communities.vmware.com/message/1576889#1576889

you need to use the standalone converter as mentioned since converter for vCenter dropped support for windows 2000.

[a_p_]

In addition to monderick's post, don't use the latest (v4.3) Converter Standalone. It also doesn't support Windows 2000 anymore.

from the release notes:

Support of the following operating systems is discontinued:

Windows 2000

Windows NT

Download v4.0.1 from http://downloads.vmware.com/d/info/datacenter_downloads/vmware_vcenter_converter_standalone/4_0

André

[DrJohnEaton]

I fell for that too, I now RTFM.

[Gonzouk]

Thanks, I downloaded that version, but after I've captured it the server boots up and blue screens, I thin provisioned the drives, can I do this with Win 2000 servers?

[monderick]

which controller type did you select?

[Gonzouk]

Where do I find that, think I must of chosen the default (preserve source)?

[a_p_]

Thin provisioning is transparent to the guest OS, this is not the cause for the BSOD.

Which HDD controller is configured for the virtual machine?

André

[Gonzouk]

looks like "preserve source"

[a_p_]

Please tak a look at http://www.vmware.com/support/converter/doc/releasenotes_conv40.html

Destination machines converted from physical machine sources running Windows 2000 display blue screen on startup

If the source physical machine has IDE disks and is running a version of Windows 2000 earlier than service pack 4, the resulting destination virtual machine displays the following error message on a blue screen:

inaccessible_boot_device.

The issue pertains to Windows and was fixed by Microsoft in service pack 4. For more information on this issue, see

http://support.microsoft.com/kb/249694/.

.

>Workarounds:

Select destination disk controller type as SCSI on the View/Edit Options page in Converter wizard.

Upgrade the source machine to service pack 4 before conversion.

Upgrade the destination virtual machine to service pack 4 using the Windows installation CD. For more information on in-place upgrade of Windows 2000, see http://support.microsoft.com/kb/292175/.

André

[Gonzouk]

The Dell server I'm trying to P to V is already using SP4, I tried redoing it with the controller as SCSI and got this below:

I actually see the Windows 2000 server splash screen and it says starting up and then...

[a_p_]

There are some MS KBs about this error message. Please replace the scsiport.sys if they apply to your setup.

http://support.microsoft.com/kb/891861/en-us

http://support.microsoft.com/kb/904374/en-us

André

[swapnendu]

Faced the same issue.

Solution: manually install vmware converter agent on the machine which you want to convert. Choose Cusotm install and install only the agent (not client or server)

Cheers

Swap