Now you have your replication agreements. As for the vdcrepadmin command, you have the following options, you can see that we now have two chords. Rinse and repeat on PSC2 PSC4 and we have the VVD topology. In this example, note that I did everything from PSC1, while I refer to different PSC files: In this post we learn how to use a PSC in the decommision/remove SSO domain. I covered the steps needed for VCSA in this contribution. The steps for a Windows-based vCenter server are very similar and are explained in VMware KB-2106736. After providing a vCenter server with an on-board service platform controller or a vCenter server with an external platform controller, you can take the appliance out of service and remove it from the vSphere and domain inventory if you no longer need appliances or if an appliance no longer reacts. Note: The process of deleting a vCenter server or service controller from the vSphere domain platform is irreversible. After removing an appliance from the domain, you can no longer connect it to the same domain. You need to re-install or have a new vCenter Server or Platform service management system to reconnect it to the domain.

My first attempt to remove vc6c.vmware.local was by running the vdcleavefed command: ./vdcrepadmin -f createagrement -2 -h psc3.local -u Administrator -H psc1.griffiths.local If we have more PSC, then plan to have the network and we can plan the same with the creategreament. Due to the replication time, it can take a few seconds to minutes for a complete network topology to be configured. Before you execute the agreement, check the current partner. vdcrepadmin -f removeagrement -2-h Source_PSC_FQDN -H PSC_FQDN_to_Remove_from_Replication -w Administrator_Password I wanted to delete all references to the old vCenter server (vc6c.vmware.local), so I reviewed the manuals of installation, configuration and troubleshooting of vSphere 6, but I found nothing. They said how to uninstall the vCenter software, but that`s it. Add an agreement with psc3.griffiths.local with the following command: In our example, we create the agreement between PSC37 and PSC35, so that in case of PSC36 error, we will always have replication with another partner in the field. Use the following command to create a new replication contract between PSCs. BEWARE – Just like Active Directory, if you don`t explicitly know what you`re doing, confusion with one of these settings can cause serious damage! In this case, I knew that my PSC installation was going south and that the existing VM could be removed without damaging the rest of my SSO environment. For more information, see Procedure to delete services for vCenter server instances. You will find the steps in using the cmsso command to cancel the registration of Single Sign-On vCenter Server (2106736) to the VMware knowledge base. Excerpt from this article: .

Currently, we have three PSCs that connect online, each PSC being installed with the previous PSC, instead of a Hub and Spoke mode, where all PSCs would end up in a PSC or central mesh topology. I started to think that it would be quite simple, that I could at least start providing an external PSC appliance and join the existing domain. I made sure that my new NAME PSC had an A entry manually registered in the DNS and installed the typical vCenter appliance. In the end, the installation was not carried out with the execution of vdcpromo: 1: Sign up as root on the shell appliance to one of the appliances of the platform controllers within the domain. Adam Fisher is a Cloud and DevOps engineer for RoundTower, based in Apex, NC. He is an IT expert who focuses on virtualization, cloud and data protection. He is vExpert and Veeam Vanguard for 2019 and a delegate to Tech Field Day. It can be followed @bonzovt on Twitter.