So this isn’t EXACTLY a throwback post.. More of a recent time machine gig I had. I was working with a customer to migrate VMs from their legacy vSphere 4.1 environment over to a new 6.7 environment. These older environments can be pretty fragile so rather than adopting the legacy ESX servers into the new vCenter, I opted to use VMware converter to migrate the few machines over.

Since this was an extremely legacy environment, we immediately hit an SSL error when trying to connect Converter to the source vCenter.

“A general system error occurred: SSL Exception: error:14077102:SSL routines:SSL23_GET_SERVER_HELLO:unsupported protocol”

After a bunch of Google-Fu, came across a nice easy fix in a forum to allow Converter to talk TLS 1.0 again with the legacy vCenter.

The workaround was to enable TLS1.0 in converter-server.xml, converter-worker.xml and converter-agent.xml by changing tag <sslOptions> from 123422720 to 56313856. These files were located in C:\ProgramDataVMwareVMware vCenter Converter Standalone. There was one more file in %ProgramFiles(x86)%VMwareVMware vCenter Converter Standaloneconverter-client.xml that also needed modifying.

Then restart the Worker and Server services.

Once the changes were made and the services restarted, it was smooth sailing bringing those 2007 machines into the 2018 environment.

– Carlo