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
4 On the destination machine, create DSN to point to the Update Manager database.
For more information about how to create DSN, see Installing and Administering VMware vSphere Update
Manager.
5 On the source machine, in the Start Menu, either in the Run Box or the Search box, type regedit and
press Enter.
The Microsoft Registry Editor opens.
6 In the Microsoft Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\VMware,
Inc.\VMware Update Manager.
The Microsoft Registry Editor contains the conguration values for Update Manager that you need for
the move of the Update Manager server and database to a new host machine.
7 On the destination machine, start the installing of the Update Manager server of the same version as the
Update Manager server instance on the source machine.
a On the vCenter Server Information page, perform the following:
n
In the vCenter IP Address/Name text box, enter the VCServer registry value from the source
machine.
n
In the HTTP Port text box, enter the VCServerPort registry value from the source machine.
n
In the user name text box, enter the VCUserName registry value from the source machine.
n
Enter the vCenter Server password that you use as an administrator.
b On the Database Options page, from the Data Source Name drop-down menu, select the DSN you
created in step 4.
c (Optional) On the Database Information page, enter user name and password for the database.
N The database password is required only if the DSN does not use Windows authentication.
A Database re-initialization warning dialog box opens.
d On the Database re-initialization warning dialog box, select the option Do not overwrite, leave my
existing database in place.
e On the VMware vSphere Update Manager Port Seings page, perform the following:
n
From the drop-down menu, select the IP address or host name of your Update Manager
instance.
n
In the SOAP Port text box, enter the SoapPort registry value from the source machine.
n
In the Web Port text box, enter the WebPort registry value from the source machine.
n
In the SSL Port text box, enter the WebSSLPort registry value from the source machine.
n
Depending on your source proxy seings, you have one of the following options:
n
If the source machine registry value UseProxy is 1, select the check box Yes, I have
Internet connection and I want to proxy now, and enter the
ProxyPassword, ProxyPort, ProxyServer, ProxyUserName registry values from the source
machine.
n
If the source machine registry value UseProxy is 0, proceed to the next step.
f On the Destination Folder page, enter the InstallPath and PatchStore registry values from the
source machine if you want to use the same paths as on the source machine, or set dierent paths
for the destination machine.
Chapter 5 Preparing for Migration
VMware, Inc. 23