VMWare Converter Standalone 5.0 - Windows

Just complete a standard CONVERSION, Accepting ALL THE DEFAULTS, do NOT CHANGE them!

Hi

Is it fails on 1% it can be communications problem, or problems in the physical Machine. Some services that are running that cannot.

If everything works, try to check if both server(physical machine and host destination) is on the same subnet and if both can communicate.

First disable any firewalls between source and destination. And test with telnet if you can use the ports from both side.

Check here the vConverter ports that you need to use:
http://kb.vmware.com/kb/1010056

If all works, focus on the physical server.

For a good understanding of the pre and post tasks for the P2V read my article, and try to run the tasks to bypass most of the P2V issues.

Even this is for a cold migration(server offline) you can use the same tasks for a hot migration(server online).

https://www.experts-exchange.com/Software/VMWare/A_3639-VMware-vConverter-P2V-for-Windows-Servers.html

If any questions, please ask.

Hope this can help

Jail

if it fails at 1 % it sounds like you cannot connect to the 2003 server are you using ip address or hostname

can you ping the server from the standalone convertor machine

Hello "BestWay",

Thanks for you answer.

I will try a Cold Clone as today the server is not in production.

I am following your tutorial, but I have a question. I just downloaded the VMWare BootCD from VMWare Website, but where can I find those P2V scripts that you talk about ?

Thanks.

Use the below tool to get the VHD of the running server.
http://technet.microsoft.com/en-us/sysinternals/ee656415

Now you have a VHD file. Install the virtualbox on a machine and using the vboxmanage command convert the vhd to the vmdk file of the vhd and use that to start the VM in ESX.
Command is given below :
VBoxManage.exe internalcommands converthd

See the link for more help:
http://www.virtualbox.org/manual/ch08.html

Hello "pradeeop08_81",

I will try your solution.

I already have the VHD created, could you tell me the correct syntax to convert that VHD to the VMDK file ?

Thanks.

use, http://www.starwindsoftware.com/converter

Convert VMDK to VHD and VHD to VMDK for free

Hi

The scripts files are in the end of the article.

Here is the link:

https://filedb.experts-exchange.com/incoming/ee-stuff/7978-P2V-Scripts.zip

But you can use the same tasks without using cold clone. Is better and safe, but you can use the online conversion.

But if you have already the Boot ISO, I will use cold clone.

But try to do the test that I have added in the above message. To check here is the problem with the conversion.

Jail

Are you converting to the vCenter Server?

If you are the issue is with vCenter Server [bug], convert directly to an ESX/ESXi server that is hosted by vCenter! Just change the IP address to the IP address of the ESX/ESXi server, and not vCenter, and use the root ESX/ESXi account.

Try it and see!

Hello "hanccocka",

I tried to use that software, converted to VMDK, added to the Virtual Machine but it shows the disk as "Sparse" (where it would show as Thin or Thick). It doesnt start the VM as well with the error,

Module DevicePowerOn power on failed.
Unable to create virtual SCSI device for scsi0:0, '/vmfs/volumes/4e8e053f-6793102e-f41e-842b2b17cf65/+Iw-13479 - srv01.xxx.br/xxxx.vmdk'
Failed to open disk scsi0:0: Unsupported or invalid disk type 7. Make sure that the disk has been imported.

I just used vmkfstools to convert that Sparse disk to Thin, but when Windows is starting I get blue screen and it keeps restarting :(

Use, Converter, but try to Convert to an ESX server, rather than vCenter server as destination.

Just tried. Same error at 1% :/

Coldclone with IP address? Destination ESXi server?

Are you converting to a local datastore in the server?

Hi

Have you tested the communications between the source and the destination? With that ports?

Have you follow the article? Did you perform the tasks?

Jail

Hello,
Use the below link for the cloning and conversion options.

http://www.virtualbox.org/manual/ch08.html#vboxmanage-clonevdi