HCX OSAM migration failure to perform fix-up operation on migrated VM.

Products

• VMware HCX

Issue/Introduction

If you are performing an OSAM migration and get the error below.

Environment

HCX

Cause

This is an error in the migration process after the VM has been migrated to the VMWare environment. The HCX manager will not have visibility into what failed on the migration at this point. 

Resolution

In order to determine the cause of the failure, you will need to power on the VM created in vCenter for your migration, and navigate to C:/temp/fixup and open the fixup log file that was created. (Do note that the fixup process is still on going when you power on this VM, so the sentinel agent will try to complete the task that was failing which may result in the VM constantly powering off or restarting while you are trying to collect this error log.)

The typical failure point here is either VMWare tools is failing to install on the VM during this process, or the fixup local user is unable to get created due to group policies in the environment. 

If the failure was due to the fixup user not getting created contact Broadcom support and reference this kb.

The fixup process will automatically delete the user once it completes. It is not possible to avoid having the local account created for OSAM migrations, and if local accounts are not permitted in your environment you will not be able to use HCX to facilitate these migrations.

If you cannot create a local account you can attempt to use the vCenter converter tool in order to migrate your VM. 

There are certain limitations to performing a migration via the vCenter converter which are listed below. 

1. You must power off source virtual machines before you convert them. You can convert running virtual machines if you follow the procedure for converting powered on machines.
2. For volume-based conversions of virtual machine sources that run Windows 8 or Windows Server 2012, Converter Standalone does not preserve storage pools on the destination.
3. For volume-based conversions of UEFI sources, Converter Standalone does not preserve the UEFI settings. The UEFI settings are preserved during disk-based conversions.
4. When you convert a virtual machine with snapshots, the snapshots are not transferred to the destination virtual machine.
5. For volume-based conversions of powered-off virtual machine sources at file level, the Converter Standalone server host operating system must support the file system of the source volume. For example, when the Converter Standalone is running on Windows Server 2008, you cannot convert source volumes with ReFS.
6. Certain limitations are applicable when you convert Linux virtual machine sources.
   1. Only disk-based cloning is supported for Linux guest operating systems.
   2. Configuration or customization is not supported for Linux guest operating systems.
   3. Installing VMware Tools is not supported on Linux guest operating systems.

Additional Information

If you have any questions about this make a ticket with HCX support.

Uploading files to cases on the Broadcom Support Portal

Creating and managing Broadcom support cases