2V0-622D · Question #98
When upgrading a standalone vCenter Single Sign-On Server version 5.5 to version 6.5, which will be the final deployment type?
The correct answer is B. It will be an external Platform Services Controller.. When upgrading a standalone vCenter SSO 5.5 instance to vSphere 6.5, the SSO component is migrated into an external Platform Services Controller (PSC) deployment.
Question
When upgrading a standalone vCenter Single Sign-On Server version 5.5 to version 6.5, which will be the final deployment type?
Options
- AThere is no option to do this type of upgrade.
- BIt will be an external Platform Services Controller.
- CIt will be an embedded Platform Services Controller with vCenter Server
- DIt will be a Standalone vCenter Server.
How the community answered
(44 responses)- A7% (3)
- B89% (39)
- C2% (1)
- D2% (1)
Why each option
When upgrading a standalone vCenter SSO 5.5 instance to vSphere 6.5, the SSO component is migrated into an external Platform Services Controller (PSC) deployment.
VMware does support this upgrade path - the standalone SSO server is a recognized source topology for migration to vSphere 6.5.
In vSphere 6.x, the vCenter Single Sign-On service was consolidated into the Platform Services Controller (PSC). A standalone SSO 5.5 node has no embedded vCenter Server, so after upgrade it maps to the external PSC deployment model, continuing to provide SSO, licensing, and lookup services separately from vCenter Server.
An embedded PSC only results when vCenter Server and SSO are co-located on the same node in 5.5; a standalone SSO server has no bundled vCenter component.
A standalone vCenter Server deployment refers to a vCenter instance with no external SSO/PSC, which is not the result of upgrading an SSO-only appliance.
Concept tested: vSphere SSO to PSC upgrade path topology
Source: https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vcenter.upgrade.doc/GUID-7AFB6672-0B79-4897-8E4E-C4F6F99A2B28.html
Topics
Community Discussion
No community discussion yet for this question.