vCenter 6.5 PSC Repoint Limitations
This is just a quick note to let you all know of a limitation with vSphere 6.5. Repointing of a vCenter Server to a Platform Services Controller (PSC) in another vSphere SSO domain SITE is not supported. Please see the caution at the top of this VMware KB article.
Note: As of 21/11/2016, the KB article for repointing a VC to a PSC WITHIN the same SSO domain site (see here) also has a caution to say it is not supported with 6.
Repoint vCenter Server to PSC
Introduction This article will walk through the steps required to repoint a vCenter Server 6U1 or later node to a different Platform Services Controller (PSC) node. Scenario one will walk through the steps if the destination PSC is located within the same vSphere SSO site, where as scenario two will walk through the steps if the destination PSC is located in a different vSphere SSO site. This is almost the same process, but repointing a VC to a PSC in a different SSO Site than the original PSC requires an additional step.
Reconfiguring and Repointing vCenter Server to PSC
Introduction Starting with vSphere 6, there are two main roles to a core vCenter infrastructure. The vCenter Server (VC) and the Platform Services Controller (PSC). During deployment, administrators are presented with two deployment options:
Embedded. With an embedded deployment, the VC and PSC roles are installed on the same node External. With an external deployment, the PSC and VC roles are installed onto separate nodes. External deployment also enables the enhanced linked mode feature for vCenter Server Prior to 6.