Decommission of external PSC after successful converge upgrade/migration

Products

• VMware vCenter Server

Issue/Introduction

This article provides information about decommissioning external PSC after successful converge upgrade/migration.

Important: The process for removing a vCenter Server or a Platform Services Controller from the vSphere domain is irreversible. After you remove an appliance from the domain, you cannot rejoin it to the same domain. You must perform a re-install or a re-deploy of vCenter Server or Platform Services Controller system in order to re-join it to the domain.

Environment

VMware vCenter Server 7.0.x

Resolution

To decommission external PSC:

1. Verify all the Management nodes are upgraded to 7.0.
2. Power off all nodes in the SSO domain (both external PSCs and the newly embedded PSC/vCenters)
3. Take a snapshot on all powered off nodes
4. Once all snapshots have been taken, power on all nodes with the exception of the external PSC that is to be decommissioned. 
5. With the external PSC VM powered off, log in as root to the appliance shell of a converged embedded node.
6. To enable the Bash shell, run the shell.set --enabled true command.
7. Run the shell command to start the Bash shell and log in.
8. Run the cmsso-util unregister command to unregister the stopped Platform Services Controller:

cmsso-util unregister --node-pnid Platform_Services_Controller_System_Name --username administrator@your_domain_name --passwd vCenter_Single_Sign_On_password

Note: You must run this command only on one of the Platform Services Controller replication partners, as the synchronization removes the entries from all other VCSA replication partners.

Note: There is downtime involved in executing cmsso-util unregister command, it will restart the services on the PSC / vCenter Server where you are executing the command.

7. Delete the Platform Services Controller appliance that you no longer need from the vSphere inventory.