Specifications

Table Of Contents
n
If your current environment is not distributed over several machines or several locations, you can
distribute the upgrade over multiple machines with a custom install (step 4) or continue placing all
vCenter components on the same machine (step 2).
2 If all vCenter Server components are on the same host machine, you can upgrade with Simple Install.
See “Use Simple Install to Upgrade vCenter Server and Required Components,” on page 65. After you
upgrade with the Simple Install process, local operating system users and the user
administrator@vsphere.local can authenticate.
n
If your environment was using only local operating system users, the localos identity source is
sufficient. You can log in to vCenter Server as administrator@vsphere.local or any local operating
system user who previously had permissions.
n
If your environment was using Active Directory to manage users and permissions, go to Step 3.
3 If your pre-upgrade environment used Active Directory to manage users and permissions, the Active
Directory domain is added to vCenter Single Sign-On as an identity source. Users who previously had
permissions to access vCenter Server objects continue to have those permissions.
Only one default identity source is supported with vSphere 5.5, and the Active Directory identity
source is initially not the default identity source. Users can log in only if they include the domain as
part of the login (DOMAIN\user).
You can log in to the vCenter Single Sign-On server as administrator@vsphere.local and make the
Active Directory domain the default identity source.
a Log in to the vCenter Single Sign-On server as administrator@vsphere.local and add the Active
Directory domain as an identity source. See “Add a vCenter Single Sign-On Identity Source,” on
page 104.
b Make the Active Directory domain the default identity source. Only one default identity source is
supported. Users from other domains can include the domain as part of the login (DOMAIN\user).
c Users who previously had permissions to access vCenter Server objects continue to have those
permissions.
4 If you decide to install vCenter Server services on different machines, you can use a Custom Install
upgrade process. See “Use Custom Install to Upgrade Version 5.0.x and Earlier vCenter Server and
Required Components,” on page 69.
a If your current environment supports only local operating system users, you must either make sure
those users are available as localos users on the machine where vCenter Single Sign-On is installed,
or you can add an Active Directory or OpenLDAP domain that includes those users.
b If your current environment supports an Active Directory domain, you can log in to the vCenter
Single Sign-On server as administrator@vsphere.local and add the Active Directory domain to
vCenter Single Sign-On. See “Add a vCenter Single Sign-On Identity Source,” on page 104.
c You can either set the default identity source or users who log in to vCenter Server can include the
domain name when they log in.
Chapter 4 Upgrading vCenter Server
VMware, Inc. 63