Specifications

See “vCenter Single Sign-On and High Availability,” on page 35 for high
availability options.
Multiple Single Sign-On
instances in different
locations
This mode is designed for vCenter Server deployments with multiple
physical locations. Multisite deployment is required when a single
administrator needs to administer vCenter Server instances that are
deployed on geographically dispersed sites in Linked Mode.
Each site is represented by one vCenter Single Sign-On instance, with one
vCenter Single Sign-On server, or a high-availability cluster. The vCenter
Single Sign-On site entry point is the machine that other sites communicate
with. This is the only machine that needs to be visible from the other sites. In
a clustered deployment, the entry point of the site is the machine where the
load balancer is installed.
NOTE This deployment mode is required if you have geographically
dispersed vCenter Servers in Linked Mode. You might also consider this
mode in the following cases:
n
If multiple vCenter Servers require the ability to communicate with each
other.
n
If you require one vCenter Single Sign-On server security domain for
your organization.
This deployment mode has the following limitations:
n
It supports the connectivity of Active Directory, OpenLDAP and
vCenter Single Sign-On embedded users and groups, but does not
support the use of local operating system user accounts.
n
Secondary vCenter Single Sign-On instances must belong to the same
Active Directory or OpenLDAP domain as the primary vCenter Single
Sign-On server and must have a local domain controller available.
You can install the vCenter Single Sign-On nodes in this deployment in any
order. Any node that is installed after the first node can point to any node
that is already installed. For example, the third node can point to either the
first or second node.
vCenter Single Sign-On and High Availability
vSphere provides several ways to ensure availability of your vSphere deployment with vCenter Single Sign-
On.
vCenter Single Sign-On is merely an authentication component for vCenter Server. Single Sign-On
protection does not provide any benefit without vCenter Server protection. Protecting one without the other
does not provide an effective availability solution. The solution you choose to protect vCenter Server will
provide the same protection for vCenter Single Sign-On without the additional complexity caused by
including third-party technologies.
Chapter 3 Preparing for the Upgrade to vCenter Server
VMware, Inc. 35