The current release of Migration Assistant has several known limitations.
The following list contains features or actions that are currently not supported:
- vSphere Update Manager is not migrated. If you use Update Manager in your environment, there are more steps you must perform to manually move Update Manager to a new destination machine. See Moving Update Manager to a New Host Machine When Migrating vCenter Server to vCenter Server Appliance.
- Local Windows OS users and groups are not migrated to the SLES OS of the vCenter Server Appliance 6.0. If you assigned vCenter Server permissions to any Local Windows OS users and groups, remove the permissions assignments before the migration. You can re-create Local OS users and groups on the SLES OS of the vCenter Server Appliance 6.0 after the migration.
- The migration process migrates only one network adapter settings to the target vCenter Server Appliance. If the hostname of the source vCenter Server resolves to multiple IP addresses across multiple network adapters, you have the option to select which IP address and network adapter settings to migrate. After the migration, you can add the rest of the network adapters and settings to the target vCenter Server Appliance.
- Migration of deployments that use custom ports for services other than Auto Deploy, Update Manager, and vSphere ESXi Dump Collector are not supported.
- After the migration, the source vCenter Server is turned off and cannot be turned on to avoid network ID conflicts with the target vCenter Server Appliance. After the source vCenter Server is turned off, all solutions that are not migrated become unavailable.
- You cannot use the source virtual machine display name as a display name for the target appliance. You can change the display name after the migration is complete. For more information, see https://kb.vmware.com/kb/1029513.