How to repoint vCenter Server 6.0 to a new External Platform Services Controller (PSC)?

By | April 1, 2015

Sometimes it would be necessary to repoint vCenter Server 6 Appliance or installed on Windows to a new external PSC. For example, some days ago I wrote a post how to configure a highly available Platform Controller Services. so it would be very useful to repoint vCenter to use Load Balancer Virtual Name. Fortunately, it is possible to repoint vCenter to a new External Platform Services (PSC) with the following steps:

vCenter  Server Appliance 6.0

You need to log into the vCenter Server appliance as root and run the following command:

/usr/lib/vmware-vmafd/bin/vmafd-cli set-dc-name --server-name localhost --dc-name <FQDN_of_PSC_or_Load_Balancer>

vCenter Server Windows 6.0

You need to log into the vCenter Server Windows Machine as Administrator and run the following command:

C:\Program Files\VMware\vCenter Server\vmafdd\vmafd-cli set-dc-name --server-name localhost --dc-name <FQDN_of_PSC_or_Load_Balancer>

After running the above command, please restart VC services:

service-control --stop --all
service-control --start --all

Note:  Repointing VC from one PSC to another is only supported within the same SSO domain. There is not supported to repoint from an embedded to an external Platform Services Controller - you can only change it with a fresh install of vCenter. For more information please follow here.

2 thoughts on “How to repoint vCenter Server 6.0 to a new External Platform Services Controller (PSC)?

  1. Luca

    I have two PCs configured with load balancing through KEMP.
    Something does not work, because vcenter successfully connects via FDQN balancing and registers but many of the services that I see still be running, are not properly contacted by vcenter same.
    Then I relinked vcenter directly to a real PSC but the service “vmware-invsvc” (inventory service) will not start …
    I guess it’s an issue of certificates, is fixable?
    Sorry for the google translation.
    greetings

    Reply
    1. Mariusz Post author

      Hello,

      The problem can be caused because of certificate. Depending on type of vCenter (Appliance or Windows) - have you check logs located on appliance: /var/log/vmware/invsvc or windows: %ALLUSERSPROFILE%\VMWare\vCenterServer\logs\invsvc folder?

      You can also install the next PSC, join to the same SSO domain and repoint vCenter to this PSC. You will not loose any SSO users, groups etc.

      btw. KEMP is not supported as a load balancer for PSCs.

      Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.