There have been many complaints about transfer rate degradation in Converter 5.0.
Converter uses NFC (a proprietary VMware protocol) for cloning to managed destination. Security has been enhanced in Converter 5.0 by encrypting the data transfer. Unfortunately this has caused a more severe performance degradation than expected.
Switching off SSL encryption is a way to work around this issue. Here is how it is done:
I.e. it should look like:
It should be under %ALLUSERSPROFILE%\Application Data\VMware\VMware vCenter Converter Standalone directory on the machine where Converter server is installed. If you paste this path in "Run" dialog box it should open at the right location.
Thank you for this tip. I was trying to convert a 500GB system, and it was predicting over 26 days to complete. After 3 days it only moved to 3%. Since I made this change and started over, the estimated time went down to just over 10 hours, and I am already at 45% since this morning.
I'm using Converter 5 and noticed the same problem. Disabling ssl didn't help me much, the problem I noticed was file vs.block transfer for the disks. If you're having slow transfer speeds, make sure you aren't doing file transfers for the disks. I had a server with C: and 😧 disks, I wanted to change the size of the disks during P2V, but when you do that Converter changes the transfer from block to file and it takes FOREVER to finish. My compromise was to change only the C: during P2V (thereby changing from block to file) and leave my larger 😧 alone (leaving it as block). This worked great - the P2V took only a few hours instead of a few days. I will be resizing the 😧 after P2V is completed.
I agree that disabling SSL does actually seem to help considerably, thank you patanassov!
I also try to guide folks to this helpful discussion over here as well:
Amazing. Thanks a ton for this information. My mysteriously slow conversion performance was estimating over 20 hours, now down to under 2 hours. Yikes... VMware, are you listening?
after this modification Converter 5 will no longer start on my 2k3 host - reverting the xml to original does not help either
Really? Is there a chance that by mistake you have created a malformed XML while editing the file? This option is ignored until the actual data transfer connection is established, so I would be very surprised if it breaks converter startup. It is even more strange that reverting back to the original file doesn't fix things.
I am as surprised as you are.
I made copies of the original file and put the originals back when I noticed the problem.
The services and the vmware-converter.exe start but no GUI appears.
Next I uninstalled and re-installed version 5 ... no luck.
Thanks god I can use Converter as well from another host so I dont need it on this one.
Do you have converter.exe process? This should be the GUI. If it is running, you can try to kill it and start it again. It has a logic for not allowing a second instance of the GUI to be started, but just activate the old one. If it is hanging for some reason, you cannot run another instance.
One more thing - do you think for some reason there is a chance that GUI is initially displayed off the screen? I mean at some weird position which makes it invisible...
in taskmanager I see converter.exe under the processes tab - but not under applications - so I doubt that it is displayed off-screen ?
could I reset that similar to settings in pereferences.ini for Workstation
Most likely it is not off-screen if it is not visible under applications. What if you just terminate converter.exe and restart it? Is it entering the same mode again? Otherwise there should be a converter-client.ini file which holds the UI settings under %USERPROFILE%\Local Settings\Application Data\VMware\VMware vCenter Converter Standalone Client - you can just delete it and it would reset the client to default values.