HCX-Migration> Start-HCXMigration -Migration $hcxMigration
Start-HCXMigration : 11-10-2024 11:54:06 Start-HCXMigration com.vmware.vapi.std.errors.invalid_request {'messages': [], 'data': struct {'errors': [struct {'code': E_INVALID_SCHEMA, 'message': JSONObject["name"] not found.}]}, 'error
_type': INVALID_REQUEST}.
At line:1 char:1
+ Start-HCXMigration -Migration $hcxMigration
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Start-HCXMigration], CisException
+ FullyQualifiedErrorId : VMware.VimAutomation.Hcx.Impl.V1.Service.HCXMigrationService,VMware.VimAutomation.Hcx.Commands.Cmdlets.StartHCXMigration
"E_INVALID_SCHEMA, 'message': JSONObject["name"] not found".
HCX documentation will be updated in the future to reflect the mandatory fields.
Workaround
When creating the New-HCXGuestOSCustomization, use the same parameters that are mandatory in the UI, such as the HostName.
As a workaround, add an empty mobility group level GuestOSCustomization object.
Example:
$GOS = New-HCXGuestOSCustomization -GroupConfiguration
$mobilityGroupConfigiuration = New-HCXMobilityGroupConfiguration -SourceSite $sourceSite -DestinationSite $targetSite -GuestOSCustomization $GOS