Connect Converter to a managed host.

[xmerlyn]

I have a server in Tampa I want to convert to a ESXi 5.5 host in Tampa.  The vCenter server is in Orlando.  Can I directly connect the Standalone Converter all in Tampa?  I get an error when I try and directly connect to the host in Tampa

[bayupw]

Hi xmerlyn

What is the error message?

Do you have the error message or screenshots?

The procedures on how to obtain diagnostic information/logs for VMware Converter is explained in the KB here:

VMware KB: Collecting diagnostic information for VMware Converter

Make sure you have open the required firewall ports as listed in the KB here:

VMware KB: Required VMware vCenter Converter 4.x/5.x ports

Thanks,

Bayu

[wkwicker]

I was wondering if this was an issue in previous versions and since this post is 5 years years old I guess it is.  I am in the same situation where I have VM hosts and the server I want to P2V at a remote site.  Since my host is managed, if I try to P2V keeping all traffic local at that site, I get an error on stating I can't P2V because my host is managed.  I am using the latest converter, 6.2.0.1. In order to P2V I have to bring the image across my slow WAN into vCenter and vCenter then will add it to the host which is back across the slow WAN.  I have to com across the slow WAN twice to do a local P2V since the host is managed.

VMWARE, Please change this!

[patanassov]

Hi

The error you get most probably means you directly target a host that is managed by a vCenter Server. Set the vCenter Server as destimation instead. This is design limitation introduced in vSphere, Converter has nothing to do with that. Similarly, whether the host is local or remote has nothing to do with that.

If however, you experience difficulties because of the remoteness, I would suggest you install Converter server on a machine on the remote site and connect to it via terminal.

HTH,

Plamen

[wkwicker]

You are correct, the error is related to the converter connecting to a host managed by vCenter.  My goal is to P2V a server quickly since the the server and VM host are at the same site.  I do not want it to take 9+ hours for this small machine by pulling it across my WAN for vCenter to add it to a host back across my WAN.  If I can use the host's UI to create a VM on the host outside of vCenter, then this seems to be a converter limitation and not a vCenter limitation.

At this point I have two choices, let it take 9 hours to P2V or unmanage a host, P2V in less than 1 hour, re-manage the host.  I am hoping VMware is reading this and will fix that limitation in the future.  If my server and host are local, I shouldn't have to cross a WAN to P2V.