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
System Requirements for Migrating
vCenter Server Deployments to
vCenter Server Appliance
Deployments 1
Your source and target systems must meet specic software and hardware requirements before you can
migrate a vCenter Server or a vCenter Single Sign-On deployment to a vCenter Server Appliance or
Platform Services Controller appliance.
Source System
n
Synchronize the clocks on all machines running the source vCenter Server services. See “Synchronizing
Clocks on the vSphere Network,” on page 24.
n
Verify that the system network name of the machines running the target vCenter Server services are
valid, and are reachable from other machines in the network.
n
Verify that the host name of the virtual machine or physical server from which you are migrating
vCenter Server complies with RFC 1123 guidelines.
n
If your vCenter Server service is running using a user account other than the Local System account,
verify that the user account in which the vCenter Server service is running has the following
permissions:
n
Member of the Administrators group
n
Log on as a service
n
Act as part of the operating system (if the user is a domain user)
n
If your vCenter Server service is running using a service user account for access to the vCenter Server
database and you run Migration Assistant under a dierent account, the Migration Assistant account
must have the Replace a process level token permission.
n
Verify that the LOCAL SERVICE account has read permission on the folder in which vCenter Server is
installed and on the HKLM registry.
n
Verify that the connection between the virtual machine or physical server and the domain controller is
working.
n
Verify that the source vCenter Server instance or vCenter Single Sign-On instance on Windows have a
default gateway. If there is no default gateway, the migration will fail.
n
Verify that the source vCenter Server instance or vCenter Single Sign-On instance on Windows does not
use a DHCP IP address as its system network name.
I Migration from a source Windows machine using a DHCP IP Address as its system
network name to an appliance is not supported.
VMware, Inc.
7