6.0.2

Table 1‑3. Login Privileges After Upgrade of Custom Install Environment
Source version Login access for Notes
vSphere 5.0 vCenter Single Sign-On recognizes local
operating system users for the machine where
the Platform Services Controller is installed, but
not for the machine where vCenter Server is
installed.
N Using local operating users for
administration is not recommended, especially in
federated environments.
[e-mail] can log in to
vCenter Single Sign-On and each vCenter Server
instance as an administrator user.
If your 5.0 installation supported
Active Directory users, those
users no longer have access after
the upgrade. You can add the
Active Directory domain as an
identity source.
vSphere 5.1 or vSphere 5.5 vCenter Single Sign-On recognizes local
operating system users for the machine where
the Platform Services Controller is installed, but
not for the machine where vCenter Server is
installed.
N Using local operating users for
administration is not recommended, especially in
federated environments.
[e-mail] log in to vCenter
Single Sign-On and each vCenter Server instance
as an administrator user.
For upgrades from vSphere 5.1
Admin@SystemDomain has the same privileges
as [e-mail].
Starting with vSphere 5.5,
vCenter Single Sign-On supports
only one default identity source.
You can set the default identity
source.
See the vSphere Security
documentation.
Users in a non-default domain
can specify the domain when
they log in (DOMAIN\user or
user@DOMAIN).
vSphere Security Certificates Overview
ESXi hosts and vCenter Server communicate securely over SSL to ensure condentiality, data integrity and
authentication.
In vSphere 6.0, the VMware Certicate Authority (VMCA) provisions each ESXi host with a signed
certicate that has VMCA as the root certicate authority, by default. Provisioning happens when the ESXi
host is added to vCenter Server explicitly or as part of the ESXi host installation. All ESXi certicates are
stored locally on the host.
You can also use custom certicates with a dierent root Certicate Authority (CA). For information about
managing certicates for ESXi hosts, see the vSphere Security documentation.
All certicates for vCenter Server and the vCenter Server services are stored in the VMware Endpoint
Certicate Store (VECS).
You can replace the VMCA certicate for vCenter Server with a dierent certicate signed by a CA. If you
want to use a third party certicate, install the Platform Services Controller, add the new CA-signed root
certicate to VMCA, and then install vCenter Server. For information about managing vCenter Server
certicates, see the vSphere Security documentation.
Enhanced Linked Mode Overview
Enhanced Linked Mode connects multiple vCenter Server systems together by using one or more
Platform Services Controllers.
Enhanced Linked Mode lets you view and search across all linked vCenter Server systems and replicate
roles, permissions, licenses, policies, and tags.
Chapter 1 Introduction to vSphere Upgrade
VMware, Inc. 27