6.0.2
Table Of Contents
- vSphere Migration
- Contents
- About vSphere Migration
- System Requirements for Migrating vCenter Server Deployments to vCenter Server Appliance Deployments
- vCenter Server Appliance Requirements
- vCenter Server Appliance Hardware Requirements
- vCenter Server Appliance Storage Requirements
- Software Included in the vCenter Server Appliance
- vCenter Server Appliance Software Requirements
- vCenter Server Appliance Database Requirements
- vSphere Web Client Software Requirements
- Required Ports for vCenter Server and Platform Services Controller
- Pre-migration Checks
- Known Limitations
- Preparing for Migration
- Moving Update Manager to a New Host Machine When Migrating vCenter Server to vCenter Server Appliance
- Synchronizing Clocks on the vSphere Network
- Preparing vCenter Server Certificates for Migration
- Preparing vCenter Server Databases for Migration
- Prepare Managed ESXi Hosts for Migration
- Install the Client Integration Plug-In
- Required Information for Migrating vCenter Server and vCenter Single Sign-On from Windows to an Appliance
- Migration of vCenter Server with an Embedded vCenter Single Sign-On to an Appliance
- Migration of vCenter Server with an External vCenter Single Sign-On to an Appliance
- After Migrating vCenter Server
- Troubleshooting
- Index
Known Limitations 4
The current release of Migration Assistant has several known limitations.
The following list contains features or actions that are currently not supported:
n
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,” on page 21.
n
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.
n
The migration process migrates only one network adapter seings 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 seings to migrate. After the migration, you can add the rest of the network adapters
and seings to the target vCenter Server Appliance.
n
After the migration, the source vCenter Server is turned o and cannot be turned on to avoid network
ID conicts with the target vCenter Server Appliance. After the source vCenter Server is turned o, all
solutions that are not migrated become unavailable.
VMware, Inc.
19