Repointing the vCenter Embedded PSC to External PSC

Hi All,

I’ve recently migrated the embedded PSC to external PSC with and without DSN names.When I migrated the PSC with DSN name.I’ve ran out an permission related issues while migrating(still figuring it)

Why PSC required in separate server?Platform Services Controller services that must be running are VMware License Service, VMware Identity Management Service, VMware Security Token Service, VMware Certificate Service, and VMware Directory Service.

  1. Firstly We need to install/upgrade vCenter 6.0 with embedded PSC and then install the PSC alone joining the existing domain.
  2. Accept the certificate prompt and then proceed with installation

Capture

3. Go to embedded PSC server and ran the following commands

C:\Program Files\VMware\vCenter Server\vmafdd>vmafd-cli get-dc-name –server-nam
e localhost
192.168.55.230

 

C:\Program Files\VMware\vCenter Server\vmafdd>vmafd-cli get-domain-name –server
-name localhost
vsphere.local

 

C:\Program Files\VMware\vCenter Server\bin>cmsso-util reconfigure –repoint-psc
192.168.55.231 –username Administrator –domain-name vsphere.local –passwd VMware@1

C:\Program Files\VMware\vCenter Server\python-modules\identity\vmkeystore.py:4:
RuntimeWarning: to-Python converter for struct client already registered; second
conversion method ignored.
import identity.vmafd as vmafd
C:\Program Files\VMware\vCenter Server\python-modules\identity\vmkeystore.py:4:
RuntimeWarning: to-Python converter for class vmafd_exception already registered
; second conversion method ignored.
import identity.vmafd as vmafd
Validating Provided Configuration …
Validation Completed Successfully.
Executing reconfiguring steps. This will take few minutes to complete.
Please wait …
Stopping all the services …
All services stopped.
Starting vmafd service.
Successfully joined the external PSC 192.168.55.231
Cleaning up…
Cleanup completed
Starting all the services …
Started all the services.
The vCenter Server has been successfully reconfigured and re pointed to the external Platform Services Controller 192.168.55.231.

 

Reference Document:

1.http://pubs.vmware.com/vsphere-60/index.jsp?topic=%2Fcom.vmware.vsphere.upgrade.doc%2FGUID-E7DFB362-1875-4BCF-AB84-4F21408F87A6.html

2.Antivirus might block to access the TMP file.So disable it before migrating.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s