6.0.2

Table Of Contents
Upgrade vCenter Single Sign-On 5.5 for External Deployment
You can upgrade your externally deployed vCenter Single Sign-On 5.5 to an externally deployed
Platform Services Controller instance by using the vCenter Server for Windows installer.
Figure 45. vCenter Single Sign-On 5.5 Upgrade Workflow for Windows
Begin vCenter Single Sign-On
5.5 Upgrade
Is vCenter
Single Sign-On
external?
Upgrade
vCenter Server
No
Yes
More
than one
Single Sign-On
instance?
No
Yes
Upgrade vCenter Server
instances. Join vCenter
Server instances to the
Standalone Platform Services
instance.
Upgrade vCenter
Single Sign-On instances
to Platform Service Controller
instances. Configuration settings
such as replication are preserved.
Upgrade to Standalone
Platform Services
Controller
Load
balancer?
No
Yes
vCenter Single Sign-On
upgrade is complete.
Verify the load balancer
is supported and
correctly configured.
If you are upgrading an externally deployed vCenter Single Sign-On 5.5 to an externally deployed
Platform Services Controller in a mixed version environment, any vCenter Server 5.5 instances continue to
operate with the upgraded Platform Services Controller exactly as they did with the vCenter Single Sign-On
without any problems or required actions.
N A vCenter Single Sign-On 5.5 deployed on the same VM or physical server as vCenter Server 5.5 is
automatically upgraded to an embedded Platform Services Controller when you upgrade to vCenter Server
6.0.
n
For more information about how vCenter Single Sign-On aects your upgrade, see “How vCenter
Single Sign-On Aects Upgrades,” on page 25.
n
For information on vCenter Server behavior in mixed version environments, see “Mixed-Version
Transitional Environments During vCenter Server Upgrades,” on page 20.
n
For information on deployment options, see “vCenter Server Deployment Models,” on page 16.
Chapter 4 Upgrading and Updating vCenter Server for Windows
VMware, Inc. 81