When you install vCenter Server 5.0.1, Orchestrator 4.2.1 is silently installed on your system as an additional component.

Verify that the machine on which you are installing vCenter Server 5.0.1 is a 64-bit operating system platform.

Verify that you have the Microsoft .NET 3.5 SP1 Framework installed. If your system does not have it installed, the vCenter Server installer installs it. The .NET 3.5 SP1 installation might require Internet connectivity to download additional files.

For a list of required ports, see the vSphere Installation and Setup documentation.

Make sure that your system meets the vCenter Server installation requirements. For more information about the vCenter Server installation prerequisites, see the vSphere Installation and Setup documentation.

Download the vCenter Server 5.0.1 installer from the VMware Web site.

1

Start the vCenter Server installer.

In the software installer directory, for example, C:\install_directory\, double-click the autorun.exe file.

2

Select vCenter Server™ and click Install.

3

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.

4

Choose the type of database that you want to use.

Option

Action

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

Select Install SQL Server 2008 Express instance (for small-scale deployments) to use the bundled database.

The SQL Server Express database is suitable for deployments of up to 5 hosts and 50 virtual machines.

Use an existing supported database

Select Use an existing supported database option to use an existing database. Select your database from the list of available DSNs. Type the user name and password for the DSN.

If your database uses Windows NT authentication, the user name and password fields are disabled.

Note

A dialog box might appear, warning you that the DSN points to an older version of a repository that must be upgraded. If you click Yes, the installer upgrades the database schema, making the database irreversibly incompatible with previous vCenter Server versions. For more information, see the vSphere Upgrade documentation.

5

Set the login information for vCenter Server.

If you are using a nonbundled database, specify the administrator name and password that you use when you log in to the system on which you are installing vCenter Server.

If you are using the bundled SQL Server database, select Use SYSTEM Account.

You will need the user name and password entered here to log in to vCenter Server after install it.

The Fully Qualified Domain Name field displays the FQDN of the system on which you are installing vCenter Server. The vCenter Server installer checks that the FQDN is resolvable. If not, a warning message is displayed when you click Next. Change the entry to a resolvable FQDN. You must enter the FQDN, not the IP address.

6

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

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

Note

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.

7

Select Create a standalone VMware vCenter Server instance or Join Group.

Join a Linked Mode group to enable the vSphere Client to view, search, and manage data across multiple vCenter Server systems. For more information, see the vSphere Installation and Setup documentation. .

Note

You cannot join a Linked Mode group during the installation if you are upgrading the VirtualCenter or vCenter Server database schema. You can join a Linked Mode group after the installation is complete.

8

If you join a group, enter the fully qualified domain name and LDAP port number of any remote vCenter Server system and click Next.

In some cases, you can enter the IP address instead of the fully qualified domain name. To help ensure connectivity, the best practice is to use the fully qualified domain name. For IPv6, unless both the local and the remote machine are in IPv6 mode, you must enter the fully qualified domain name of the remote machine instead of the IPv6 address. If the local machine has an IPv4 address and the remote machine has an IPv6 address, the local machine must support IPv4 and IPv6 mixed mode. The domain name server must be able to resolve both IPv4 and IPv6 addresses if your environment has both addressing types in a single Linked Mode group.

9

Specify the port numbers to use or accept the default port numbers and click Next.

10

Select the amount of JVM memory to allocate for vCenter Server Web services, according to the size of your inventory.

This setting determines the JVM heap settings for Tomcat, Inventory Service, and Storage Based Policy Management (SPS) services. You can adjust this setting after installation if the number of hosts in your environment changes.

11

In the Ready to Install the Program window, 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, this option prevents the pool of available ephemeral ports from being exhausted.

12

Click Install.

Installation might take several minutes. Multiple progress bars appear during the installation of the selected components.

13

Click Finish.

You completed the installation of vCenter Server. The Orchestrator client and server components are installed on your system.

Start the VMware vCenter Orchestrator Configuration service and log in to the Orchestrator configuration interface at: http://localhost:8282.

Configure Orchestrator using an IPv4 operating system. Orchestrator does not support IPv6 operating systems.