Mobility Group created via PowerShell script shows "Bulk Migration (not licensed)"

Products

• VMware HCX

Issue/Introduction

• VMware HCX bulk migration of workloads via PowerShell script fails.

• Mobility Group created via PowerShell script shows Bulk Migration (not licensed):

• The HCX Manager UI Migrations dialog and the PowerShell console output display the following error: Unable to find a Service Mesh for the selected scope with cluster pair (<REDACTED_CLUSTERNAME> to <REDACTED_CLUSTERNAME>)

• The script execution log contains the following entries: 

  2026-03-05 16:13:42,123 [ERROR] MigrationCreateFailed: Unable to find a Service Mesh for the selected scope with cluster pair (<REDACTED_HOSTNAMES> to <REDACTED_HOSTNAMES>)
  2026-03-05 16:13:42,124 Script line 57: New-HCXMigration -Name $MigName -Source $srcCluster -Target $tgtCluster …

Environment

VMware HCX 4.11.3

Cause

The PowerShell automation script does not supply a Service Mesh object to the New‑HCXMigration cmdlet. Because the Get‑HCXServiceMesh call is commented out, HCX attempts auto‑discovery, which fails when multiple meshes exist or when the source‑target pair is ambiguous.

Resolution

 

• Edit the PowerShell migration script.

• Adjust the Service Mesh retrieval line as such (This configuration is required):

  $TargetServiceMesh = Get-HCXServiceMesh -Name $VM_Details.SERVICE_MESH_NAME
  

• Ensure $VM_Details.SERVICE_MESH_NAME matches the exact name of the Service Mesh shown in the HCX Manager UI under Service Meshes.

• Pass the retrieved object to the migration cmdlet by adding the -ServiceMesh parameter:

  New-HCXMigration `
      -Name $MigName `
      -Source $srcCluster `
      -Target $tgtCluster `
      -ServiceMesh $TargetServiceMesh `
      ...
  

• Run a test migration for a single virtual machine to confirm the Service Mesh resolves correctly.

• Re-run the bulk migration script.