Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Decommission of external PSC after successful converge upgrade/migration (75177)

Last Updated: 11/17/2020Categories: How toTotal Views: 27185Language:
Chinese (Simplified)JapaneseEnglish

7 like this article

Subscribe to get an email
newsletter with new updates

7 people found this helpful Please provide article feedback:

Purpose

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.

Resolution

To decommission external PSC:

Verify all the Management nodes are upgraded to 7.0.

Power off all nodes in the SSO domain (both external PSCs and the newly embedded PSC/vCenters)

Take a snapshot on all powered off nodes

Once all snapshots have been taken, power on all nodes with the exception of the external PSC that is to be decommissioned.

With the external PSC VM powered off, log in as root to the appliance shell of a converged embedded node.

To enable the Bash shell, run the shell.set --enabled true command.

Run the shell command to start the Bash shell and log in.

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.

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

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
利用持有者令牌 - 检索用户信息：包含用户数据的已解码 base64 持有者令牌中存在不一致问题 (75137)

KB
•
Google 搜索提示和技巧 (75226)

KB
•
ベアラー トークンの利用 - ユーザー情報の取得：ユーザー データを含むデコードされた base64 ベアラー トークンに不整合がある (75137)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server

Related Versions:

VMware vCenter Server 7.0.x

Take Our Survey

Support Assistant