Yes, I added that to the host file of the VCenter and as an entry on their internal DNS server. The name resolves when the converter attempts to connect when selecting the destination. However, I did change that name after the new ESX 5.5 server was created to VMHost.wvins.local. I can resolve with both names. However, the certificate still does show localhost.localdomain. I haven't been able to get a clear instruction on how to recreate a self-signed cert for that host that would reflect the new name. If you think that might be the issue, I'd appreciate a point in the right direction to do so.
However, the thing that I don't get is why if I have UseSSL set to false in the converter-worker.xml file that it would go ahead and try to verify SSL?