VMware Converter Fails to Customize Windows VM After Image Copy

Products

VMware vCenter Server

Issue/Introduction

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.

Environment

- VMware vCenter Converter Standalone versions 6.4 and 6.6
- Source and destination vCenter servers
- Windows virtual machine images

Relevant Logs:

VMware Converter Server Logs:
Location: [Converter installation directory]\vmware-converter-server-[number].log
Relevant entry:

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

VMware Converter Worker Logs:
Location: [Converter installation directory]\vmware-converter-worker-[number].log
Relevant entry:

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

Cause

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.

Resolution

Verify network connectivity between the VMware Converter and the destination ESXi host:
1. Open a PowerShell window on the machine running VMware Converter.
2. Run the following command, replacing <Destination_ESXi_Host_IP> with the IP address of your destination ESXi host:
  - ```
  Test-NetConnection -ComputerName <Destination_ESXi_Host_IP> -Port 902
```
Test connectivity from the ESXi host to the VMware Converter machine:
1. Enable SSH on the ESXi host temporarily (if not already enabled).
2. Connect to the ESXi host via SSH.
3. Run the following command, replacing <Converter_Machine_IP> with the IP address of your VMware Converter machine:
  - ```
  nc -z -v <Converter_Machine_IP> 902
```
If either test fails, work with your network team to ensure port 902 is open bidirectionally:
1. Provide your network team with the IP addresses of the VMware Converter machine and the destination ESXi host.
2. Request that they open port 902 for both TCP and UDP traffic in both directions between these two endpoints.
3. After the network changes are made, repeat steps 1 and 2 to verify connectivity.
If port 902 is open in both directions and the issue persists:
1. Check the VMware Converter logs for any additional error messages.
2. Verify that the customization specification is correctly configured in the destination vCenter.
3. Ensure that the source VM is compatible with the destination environment (e.g., hardware version, OS version).
If the issue continues after verifying all the above steps, contact VMware support for further assistance.

Note: Remember to disable SSH on the ESXi host after testing if it's not typically enabled in your environment.

Additional Information

- 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.