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

Changing external Platform Services Controller deployment to embedded during process of migration or upgrade (68137)

Last Updated: 7/6/2020Categories: InformationalTotal Views: 8041Language:
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:

Details

This article describes how to change external Platform Services Controller deployment topology to embedded during process of migration or upgrade to vSphere 7.0.

VMware is deprecating the external Platform Services Controller(PSC) deployment model. Since vSphere 7.0 release, there will no longer be an option to deploy the external PSC. This means that customers with an existing external deployment needs to change their topology to embedded before or during migration or upgrade to vSphere 7.0.

A converge utility introduced in vSphere 6.7U1, allows customers with an external PSC deployment to migrate to an embedded PSC deployment prior upgrading/migrating to vSphere 7.0. It is a two way step process: first do a converge and second perform upgrade/migrate. Also note, that this utility is only available in vCenter Server Appliance(vCSA) and it's not available in vCenter Server for Windows.

As part of vCenter Server 7.0 upgrade/migrate, MxN deployment topology will be converged and upgrade/migrate to embedded PSC in a single step following existing upgrade/migrate process.

Solution

The solution below describes steps to converge external PSC deployment topology during migration or upgrade process.

Convergence Steps

Before starting migration or upgrade to vSphere 7.0 take a backup of your vCenter Server(s) and the PSCs in vSphere SSO domain. This must be done before each vCenter Server management node upgrade or migration. VMware recommends having Powered-Off snapshots taken if you are planning to use snapshots as backup solution. The correct practice is to have powered-off snapshots of all PSCs and VCs within the SSO domain. This ensures consistency for the entries in VMDIR (VMware Directory Service) Database and that they do not go out of sync in the event they roll back to the previous state. Additionally, it is recommended that when rolling back to a previous state that all PSCs and VCs are rolled back to the same point in time

Note: The process for migration or upgrade to vCenter Server with an embedded Platform Services Controller is irreversible. The legacy vCenter Server management node will be removed from the vSphere SSO domain and it cannot rejoin to the same domain. You must perform restore from backup of vCenter Servers and Platform Services Controller systems in order to restore legacy system configuration.

Skip external Platform Services Controller upgrade or migration. The external Platform Services Controller upgrade will be part of migration process of the vCenter Server management node.

Proceed to vCenter Server management node upgrade or migration. Follow steps of vCenter Server upgrade UI wizard or use upgrade CLI to perform the upgrade. Note that if there are more than once vCenter Server management nodes in the deployment, an already converged embedded node needs to be specified as "SSO replication partner" or "first instance" for the first converged vCenter Server.

After the upgrade or migration process has completed, verify the vCSA is now running with an embedded PSC. You can use VMware Appliance Management on port 5480 or vSphere Client (HTML5). For VMware Appliance Management, go to the Summary tab and verify the type is “vCenter Server with an embedded Platform Services Controller” or look under the Administration menu in vSphere Client for System Configuration and verify the type as above.

If there are any products or solutions that use the PSC for authentication, they will need to be re-registered. Re-register them with the embedded vCSA deployment before decommissioning the external PSC.

Do not decommission an external PSC until all vCenter Server management nodes registered to that PSC have gone through the convergence process.

Decommission external Platform Services Controller

Note: Verify the steps above have been completed prior to starting the decommissioning process.

Decommission external Platform Services Controllers using the cmsso-util command. For detailed instructions on decommissioning an external Platform Services Controller see Decommission of external PSC after successful converge upgrade/migration

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
VMware Learning Platform の FAQ (70735)

KB
•
Download and Install VMware Fusion (2014097)

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 vSphere ESXi

Related Versions:

VMware vSphere ESXi 7.0.0

Take Our Survey

Support Assistant