When you install vCenter Server, Orchestrator is silently installed on your system as an additional component. You can use the data migration tool to launch the vCenter Server installer, install Orchestrator, and import the configuration from your previous Orchestrator installation.

For detailed information about installing vCenter Server 5.0.1 and restoring the existing vCenter Server database and configuration, see the vSphere Upgrade documentation.

Log in to the 64-bit machine as an administrator.

For the 64-bit machine, use the same IP address and host name as that which you used for the source 32-bit machine.

Ensure that the destination machine has Microsoft Windows Installer (MSI) 4.5 installed on it.

Download the vCenter Server installer.


Copy the datamigration folder from the source machine to the destination machine.


Insert the vCenter Server installation media into the DVD-ROM drive on the destination machine, or copy the installation ISO image to the destination machine.


From the Windows command prompt, navigate to the datamigration folder you copied from the source machine, type install.bat and press Enter.


If the name of the destination machine is different from the name of the source machine, type y to continue.


Type the path to the vCenter Server 5.0.1 installation media and press Enter.

The install script verifies that migration data is present, and starts the vCenter Server installer.


Follow the prompts in the installation wizard to choose the installer language, agree to the end user patent and license agreements, enter your user name, organization name, and license key.

If you omit the license key, vCenter Server will be in evaluation mode, which allows you to use the full feature set for a 60-day evaluation period. After installation, you can enter the license key to convert vCenter Server to licensed mode.


Select the type of database to use.



Install SQL Server 2008 Express instance (for small-scale deployments)

Select this option if you used the bundled SQL Express database on the source machine.

Use an existing supported database

Select this option to use an existing non-bundled database. Select the DSN that was used for the database on the source machine, type the user name and password for the DSN, and click Next. If you specify a remote SQL Server database that uses Windows NT authentication, the database user and the logged-in user on the vCenter Server machine must be the same.


Select how to upgrade vCenter Agent and click Next.




vCenter Agent is upgraded on all hosts in the vCenter Server inventory.


All hosts are disconnected from vCenter Server. To upgrade vCenter Agent, reconnect the host to vCenter Server.

Select this option if one of the following situations:

You need to control the timing of vCenter Agent upgrades on specific hosts.

The number of hosts in the vCenter Server inventory is large, and you anticipate that upgrading vCenter Agent on all hosts would negatively affect vCenter Server performance.

vCenter Agent is installed on each host in the inventory to enable vCenter Server to manage the host. vCenter Agent must be upgraded when vCenter Server is upgraded.


Type the password for the vCenter Service user account, if the user account is specified.

By default, Use SYSTEM Account is selected.


Specify the fully qualified domain name (FQDN).


Either accept the default destination folders or click Change to select another location, and click Next.

The installation path cannot have commas (,) or periods (.).


To install the vCenter Server on a drive other than C:, verify that the C:\WINDOWS\Installer folder is large enough to accommodate the Microsoft Windows Installer .msi file. If the folder is not large enough, your vCenter Server installation might fail.


Specify the port numbers for vCenter Server or accept the default port numbers.

The port numbers displayed are those that were backed up from the source installation.


Specify the port numbers for Inventory Service.


Select the amount of memory to allocate to the vCenter JVM in Tomcat, according to the number of hosts in your environment.

You can adjust this setting after installation if the number of hosts in your environment changes.


In the Ready to Install the Program page, select Select to bump up the ephemeral port value.

This option increases the number of available ephemeral ports. If your vCenter Server manages hosts on which you will power on more than 2000 virtual machines simultaneously, selecting this option prevents the pool of available ephemeral ports from being exhausted.


Click Install.

The installation process might take several minutes.


After the installation process is completed, click Finish.

The data migration tool restores the backed up configuration data and starts the vCenter Server service.


Check the \logs\restore.log file in the datamigration\logs folder, and verify that no errors occurred during the restore process.

vCenter Server and the Orchestrator client and server components are installed.

The configuration settings from your previous Orchestrator installation are imported.

Start the VMware vCenter Orchestrator Configuration service and log in to the Orchestrator configuration interface. If you migrated from vCenter Orchestrator 4.0, you must update the Orchestrator database.

If your Orchestrator database is local to the 32-bit Orchestrator server, it is inaccessible after the configuration backup. You must set up a new database and configure the database connection from the Database tab in the Orchestrator configuration interface.

For the detailed procedures, see

Start the Orchestrator Configuration Service

Log In to the Orchestrator Configuration Interface

Configure the Database Connection