IP customization fails for Windows Server 2016 or Windows Server 2022 VMs after HCX Bulk Migration

Products

• VMware HCX

Issue/Introduction

• HCX guest IP customization failed while bulk migrating Windows Servers 2016, Windows Server 2022, or later
• The following error will be seen in the Cloud/Destination HCX manager using CLI:

   "/common/logs/admin/app.log":

2025-##-## 22:13:45.447 UTC [GuestCustomizationService_SvcThread-205, Ent: HybridityAdmin, , TxId: TxId: ] ERROR c.v.v.h.g.c.i.CustomizationManagerImpl- Error in  deploying deployment package for moref: vm-#####
java.lang.RuntimeException: Can't determine IMC guest type for unknown OS: windows2019srvNext_64Guest
        at com.vmware.vchs.hybridity.guest.customization.impl.CustomizationManagerImpl.determineImcOsType(CustomizationManagerImpl.java:180)
        at com.vmware.vchs.hybridity.guest.customization.impl.CustomizationManagerImpl.pushDeploymentPackage(CustomizationManagerImpl.java:213)
        at com.vmware.vchs.hybridity.guest.customization.job.GuestCustomizationJob.customizeGuestConfiguration(GuestCustomizationJob.java:257)
        at com.vmware.vchs.hybridity.guest.customization.job.GuestCustomizationJob.run(GuestCustomizationJob.java:51)
        at com.vmware.vchs.hybridity.messaging.LoggingJobWrapper.run(LoggingJobWrapper.java:41)
        at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
        at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
        at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
        at java.base/java.lang.Thread.run(Thread.java:829)

• Windows Server 2016 migration completes but no IP change happens

Environment

VMware HCX

Cause

HCX supports Guest OS customization for specific Windows and Linux operating systems.

Resolution

1. Prerequisites for IP Customization

   • Verify that the destination vCenter and ESXi hosts support the Guest OS.
   • Ensure VMware Tools is installed and running on the source VM.
   • Confirm that the Guest OS is on the officially supported list for your specific HCX version.

     2. Identify the Error: Check the Cloud HCX Manager app.log for the Can't determine IMC guest type exception.

               Guest OS Types for Guest Customization (4.10)

               Guest OS Types for Guest Customization (4.11)

               Guest OS Types for Guest Customization (9.0)

    3. Check Version Compatibility: Review the tech docs relating to supported Guest OS Types for Guest Customization based on the current version of HCX

    4. Manual Workaround: If the OS version is not yet supported for automated customization:

1. • Initiate the Bulk Migration without IP customization.
   • Manually configure the IP address via the Guest OS console once the VM is powered on at the destination.   

    5. Upgrade HCX: If a newer HCX version supports the Guest OS, plan an upgrade of the HCX Manager and Service Mesh.