As you will notice during this deployment guide, there is not an option to create another SSO site when joining an existing SSO domain, this is due to SSO sites no longer being required for new deployments. I will be deploying a single SSO domain in a single SSO site.
#Installing vcenter 6.5 appliance upgrade#
The caveat is that this is only for greenfield deployments, there is not a currently supported method to upgrade or migrate from external PSC deployment to an embedded PSC deployment.ĭue to an issue with expiring PSC Machine SSL certificates in my homelab and challenges replacing these, I decided to deploy vCenter 6.5 U2 using embedded PSCs. The recommendation from vSphere 6.5 U2 and vSphere 6.7 onwards, is to use Embedded PSCs.
#Installing vcenter 6.5 appliance update#
Note: With vCenter Server 6.5 Update 2, you can deploy by using the GUI or CLI installer up to 15 vCenter Server Appliance instances in Embedded Linked Mode, and manage these instances with the vSphere Web Client or vSphere Client from any of the instances. The VMware KB Supported and deprecated topologies for VMware vSphere 6.5 (2147672) still needs further updates as there is only the following note at the bottom of the article: Previous versions required external PSCs to enable ELM. VCenter Server 6.5 Update 2 now supports Enhanced Linked Mode (ELM) when the vCenter appliance is deployed with an embedded Platform Services Controller (PSC). I expect there will be a supported upgrade path from vSphere 6.5 U2 to a future minor version release of vSphere 6.7. This should be carefully considered in any implementation or future upgrade plans. As vSphere 6.7 was released prior to vSphere 6.5 U2, there is not a supported upgrade path from vSphere 6.5 U2 to vSphere 6.7.
Following on from this release, vSphere 6.5 Update 2 was released in May 2018, which included some features from vSphere 6.7. VSphere 6.7 was released in April 2018 which included many new features and enhancements.