You can upgrade vCenter Server and other vCenter components separately to customize the location and configuration of each component.

This procedure upgrades vCenter Server versions 5.0.x and earlier, which do not include vCenter Single Sign-On. If you are upgrading vCenter Server 5.1.x, see one of the following procedures:

Use Custom Install to Upgrade a Standalone vCenter Single Sign-On Deployment of Version 5.1.x vCenter Server and Required Components.

Use Custom Install to Upgrade vCenter Server from a Version 5.1.x High Availability vCenter Single Sign-On Deployment.

Use Custom Install to Upgrade vCenter Server from a Version 5.1.x Multisite vCenter Single Sign-On Deployment.

For most standalone vCenter Single Sign-On deployments, if all components are on the same host machine, you can upgrade vCenter Single Sign-On, the vSphere Web Client, Inventory Service, and vCenter Server together on a single host machine using the vCenter Server Simple Install option.

See Use Simple Install to Upgrade vCenter Server and Required Components.

Note

vCenter Server 5.5 supports connection between vCenter Server and vCenter Server components by IP address only if the IP address is IPv4-compliant. To connect to a vCenter Server system in an IPv6 environment, you must use the fully qualified domain name (FQDN) or host name of the vCenter Server. The best practice is to use the FQDN, which works in all cases, instead of the IP address, which can change if assigned by DHCP.

1

Create the only vCenter Single Sign-On instance in a standalone vCenter Single Sign-On installation or the first vCenter Single Sign-On instance in a deployment with multiple vCenter Single Sign-On instances.

2

Create an additional vCenter Single Sign-On node as a partner to an existing vCenter Single Sign-On installation in the same location so that you can configure a third-party load balancer to provide vCenter Single Sign-On high availability.

3

Create an additional vCenter Single Sign-On node as a partner to an existing vCenter Single Sign-On installation in a different location so that the authentication information is replicated between the vCenter Single Sign-On instances. The vCenter Server instances registered with the replicating vCenter Single Sign-On instances are in Linked Mode and belong to the same vCenter Single Sign-On domain.

4

The vSphere Web Client lets you connect to a vCenter Server system to manage your vSphere deployment through a browser.

5

You can use Custom Install to upgrade vCenter Single Sign-On, vCenter Inventory Service, and vCenter Server separately to customize the location and configuration of the components.

6

You can upgrade vCenter Server separately after installing vCenter Single Sign-On, and upgrading Inventory Service.