You can deploy vCenter Server, the vCenter Server components, and the Platform Services Controller on one virtual machine or physical server.

After you deploy vCenter Server with an embedded Platform Services Controller, you can reconfigure your topology and switch to vCenter Server with an external Platform Services Controller. This is a one-way process after which you cannot switch back to vCenter Server with an embedded Platform Services Controller. You can repoint the vCenter Server instance only to an external Platform Services Controller that is configured to replicate the infrastructure data within the same domain.

vCenter Server with an Embedded Platform Services Controller
vCenter Server with an embedded Platform Services Controller are installed on the same virtual machine or physical server.

Important

Concurrent installations of vCenter Server instances with embedded Platform Services Controllers are not supported. You must install the vCenter Server instances with embedded Platform Services Controllers in a sequence.

Verify that your system meets the minimum software and hardware requirements.

Download the vCenter Server installer.

If you want to use the vSphere Web Client on the host machine on which you install vCenter Server, verify that Adobe Flash Player version 11.9 or later is installed on the system.

1

In the software installer directory, double-click the autorun.exe file to start the installer.

2

Select vCenter Server for Windows and click Install.

3

Follow the prompts of the installation wizard to review the welcome page and accept the license agreement.

4

Select vCenter Server and Embedded Platform Services Controller, and click Next.

5

Enter the system network name, preferably an FQDN, and click Next.

You can also enter an IP address. If you enter an IP address, provide a static IP address.

Important

Make sure the FQDN or IP address that you provide does not change. The system name cannot be changed after deployment. If the system name changes, you must uninstall vCenter Server and install it again.

6

Create a new vCenter Single Sign-On domain or join an existing domain.

Important

Although you can select to join a vCenter Single Sign-On domain, you should consider vCenter Server with an embedded Platform Services Controller as a standalone installation and do not use it for replication of infrastructure data.

Option

Description

Create a new Single Sign-On domain

Creates a new vCenter Single Sign-On server.

a

Enter the domain name, for example vsphere.local.

b

Set the password for the vCenter Single Sign-On administrator account.

This is the password for the user administrator@your_domain_name, where your_domain_name is a new domain that is created by vCenter Single Sign-On. After installation, you can log in to vCenter Single Sign-On and to vCenter Server as adminstrator@your_domain_name.

c

Enter the site name for vCenter Single Sign-On.

The site name is important if you are using vCenter Single Sign-On in multiple locations. Choose your own name for the vCenter Single Sign-On site. You cannot change the name after installation.

The supported characters are alphanumeric characters and dash (-).

Join a Single Sign-On domain in an existing Platform Services Controller

Joins a new vCenter Single Sign-On server to a vCenter Single Sign-On domain in an existing Platform Services Controller. You must provide the information about the vCenter Single Sign-On server to which you join the new vCenter Single Sign-On server.

a

Type the fully qualified domain name (FQDN) or IP address of the Platform Services Controller that contains the vCenter Single Sign-On server to join.

b

Type the HTTPS port to use for communication with the Platform Services Controller.

c

Type the password of the vCenter Single Sign-On administrator account.

d

Click Next.

e

Approve the certificate provided by the remote machine.

f

Select whether to create or join an existing vCenter Single Sign-On site.

7

Click Next.

8

Select the vCenter Server service account and click Next.

Option

Description

Use Windows Local System Account

The vCenter Server service runs in the Windows Local System account.

This option prevents you from connecting to an external database by using Windows integrated authentication.

Specify a user service account

The vCenter Server service runs in an administrative user account with a user name and password that you provide.

Important

The user credentials that you provide must be of a user who is in the local administrator group and who has the Log on as a service privilege.

9

Select the type of database that you want to use and click Next.

Option

Description

Use an embedded database (PostgreSQL)

vCenter Server uses the embedded PostgreSQL database. This database is suitable for small scale deployments.

Use an external database

vCenter Server uses an existing external database.

a

Select your database from the list of available DSNs.

b

Type the user name and the password for the DSN.

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

10

For each component, accept the default port numbers, or if another service is using the defaults, enter alternative ports, and click Next.

Make sure that ports 80 and 443 are free and dedicated, so that vCenter Single Sign-On can use these ports. Otherwise, use custom ports during installation.

11

(Optional) Change the default destination folders and click Next.

Important

Do not use folders that end with an exclamation mark (!).

12

Review the VMware Customer Experience Improvement Program (CEIP) page and choose if you want to join the program.

For information about the CEIP, see the Configuring Customer Experience Improvement Program section in vCenter Server and Host Management.

13

Review the summary of the installation settings and click Install.

14

(Optional) Click Launch vSphere Web Client to start the vSphere Web Client and log in to vCenter Server.

15

After the installation completes, click Finish.

vCenter Server, the vCenter Server components, and the Platform Services Controller are installed.