After using VMware Converter to copy a Windows image from one vCenter to another, the customization process fails during deployment. Specifically, the DNS name doesn't change, and the image doesn't join the MS domain as expected.
- VMware vCenter Converter Standalone versions 6.4 and 6.6
- Source and destination vCenter servers
- Windows virtual machine images
Relevant Logs:
error vmware-converter-server[XXXX] [Originator@XXXX sub=vmomi.soapStub[0]] Resetting stub adapter: service state request timed out; a: <<last binding: <<pipe '\\.\pipe\vmware-converter-worker-soap'>, <pipe '\\.\pipe\vmware-converter-worker-soap'>>>, /converter/sdk>, pa: <last binding: <<pipe '\\.\pipe\vmware-converter-worker-soap'>, <pipe '\\.\pipe\vmware-converter-worker-soap'>>>, timeout: 120sec
warning vmware-converter-worker[XXXX] [Originator@XXXX sub=Default] [,0] SSL: connect failed (5)
warning vmware-converter-worker[XXXX] [Originator@XXXX sub=Default] [,0] [NFC ERROR]NfcNet_MakeHandleFromFdEx: SSL connection failed
The issue is likely caused by network connectivity problems, specifically with port 902, which is required for communication between the VMware Converter and the destination ESXi host.
Test-NetConnection -ComputerName <Destination_ESXi_Host_IP> -Port 902
nc -z -v <Converter_Machine_IP> 902
Note: Remember to disable SSH on the ESXi host after testing if it's not typically enabled in your environment.
- For more details on port requirements for VMware Converter, refer to the official documentation:
- Ensure that your VMware Converter version is up to date, as newer versions may include bug fixes for customization issues.