In vSphere 6.0 Update 1, one of the new features that is available for both the vCenter Server for Windows and vCenter Server Appliance (VCSA) is the ability to "repoint" the vCenter Server to a new or existing Platform Services Controller (PSC). The process is pretty straight forward and is nicely outlined in the following KB articles: KB 2113917 and KB 2131191.

One obvious question that might come up before you decide to repoint is what is the current PSC that my vCenter Server is currently pointing to? This was actually a question that I had just received this morning from one of my readers. Though I had some of the details documented in these two articles here and here on locating all deployed PSC's and vCenter Server's, I figured it was probably worth pulling this topic out into its own blog post for ease of searching.

Note: The solution below is applicable to both vSphere 6.0 and vSphere 6.0 Update 1, but the ability to repoint is only available in Update 1.

There are two methods in which you can quickly identify the PSC that your vCenter Server is currently pointing to.

Option 1: Using the vSphere Web/C# Client

Under the vCenter Server's Advanced Setting, there is a property called "config.vpxd.sso.admin.uri" which specifies the PSC it is currently configured with. This is the most simplistic approach if you want to do it using the vSphere UI. Also note this is available through the vSphere API, so you can also query this from the command-line



Option 2: Using vmafd-cli command-line

The second option is to use the handy vmafd-cli utility which is avialable on the vCenter Server itself. You will need to run the following command depending on your vCenter Server platform (Windows or VCSA):

VCSA:

/usr/lib/vmware-vmafd/bin/vmafd-cli get-ls-location --server-name localhost

Windows VC:

C:\Program Files\VMware\vCenter Server\vmafdd\vmafd-cli get-ls-location --server-name localhost

Here is a screenshot of running the command on the VCSA: