Search the VMware Knowledge Base (KB)
View by Article ID

Migrating a single VMware vCenter Single Sign-On embedded VMware vCenter Server deployment to an external VMware vCenter Single Sign-On deployment (2127992)

  • 3 Ratings

Purpose

When all VMware vCenter Server 5.1/5.5 components are installed on the same machine, the VMware vCenter Single Sign-on 5.1/5.5 deployment type is embedded.

When you upgrade to VMware vSphere 6.0, several configurations of VMware vSphere 5.1/5.5 are upgraded to topologies that are deprecated.

In this example, a single embedded VMware vCenter Single Sign-On VMware vCenter Server deployment is upgraded to an Embedded Platform Services Controller in VMware vSphere 6.0:
 
 

This topology is recommended only when one VMware vCenter Server exists within the deployment. If you plan to add an additional VMware vCenter Server or Platform Services Controller after the upgrade, this results in the following deprecated topologies that are not recommended by VMware:
 
 
 
For more information on deprecated topologies for VMware vSphere 6.0, see the Deprecated topologies section in List of recommended topologies for VMware vSphere 6.0.x (2108548).

For information on migrating to an external Platform Service Controller when on vSphere 6.0 Update 1, see the Reconfigure vCenter Server with Embedded Platform Services Controller to vCenter Server with External Platform Services Controller section of the vSphere Upgrade guide.

Reconfiguration Caveats:
  • Verify that you have only one external Platform Services Controller installed.
  • Verify that the external Platform Services Controller is in the same vCenter Single Sign-On domain as the embedded Platform Services Controller.
  • Verify that you do not have any additional Embedded vCenter Servers replicating with the vCenter Server you are attempting to convert.
 
This article provides the necessary steps to migrate your existing VMware vCenter Server deployment to use an external deployment of VMware vCenter Single Sign-On.

Resolution

Note: This article is a part of a resolution path. For more information, see Migrating embedded VMware vCenter Single Sign-On to an external VMware vCenter Single Sign-On deployment (2125119).

This article consists of these steps to migrate your existing VMware vSphere 5.1/5.5 deployment to a recommended topology for VMware vSphere 6.0:
  1. Document the existing VMware vCenter Single Sign-On permissions used within your VMware vCenter Signle Sign-On domain
  2. Deploy a new VMware vCenter Single Sign-On machine
  3. Repoint the VMware vSphere Web Client to the new VMware vCenter Single Sign-On deployment
  4. Repoint VMware vCenter Inventory Service to the new VMware vCenter Single Sign-On deployment
  5. Repoint VMware vCenter Server to the new VMware vCenter Single Sign-On deployment
  6. Remove VMware vCenter Single Sign-On installed on the VMware vCenter Server machine
  7. Upgrade VMware vCenter Single Sign-On to an External Platform Services Controller
  8. Upgrade VMware vCenter Server 5.1/5.5 to VMware vCenter Server 6.0

Document the existing VMware vCenter Single Sign-On permissions used within your VMware vCenter Single Sign-On domain

Before migrating, document any custom settings configured for VMware vCenter Single Sign-On using the VMware vSphere Web Client.

Custom settings include, but are not limited to:
  • Identity Sources
  • Password Policies
  • Lockout Policies
  • Token Policies
  • Single Sign-On Users and Groups added after install
For more information, see the Configuring vCenter Single Sign-On section in the vSphere Security guide.

 

Deploy a new VMware vCenter Single Sign-On machine

To deploy a new VMware vCenter Single Sign-On machine:
  1. Deploy a new Microsoft Windows Server on a physical or virtual machine that meets the software and hardware requirements for your version of VMware vCenter Single Sign-On.

    For more information, see Installing vCenter Server 5.1 best practices (2021202) and Installing vCenter Server 5.5 best practices (2052334).

  2. Download and mount the installation media for the current version and build of VMware vCenter Server that is currently deployed in your environment.
  3. Install VMware vCenter Single Sign-On.

    Note: When prompted, create a new VMware vCenter Single Sign-On domain. Do not join another VMware vCenter Single Sign-On domain or instance.

Repoint the VMware vSphere Web Client to the new VMware vCenter Single Sign-On deployment

To repoint the VMware vSphere Web Client to the new VMware vCenter Single Sign-On deployment:
  1. Log on as an administrative user to the VMware vCenter Server machine.
  2. Repoint the VMware vSphere Web Client to the new VMware vCenter Single Sign-On deployment.

    For more information, see the Register the vSphere Web Client with a different vCenter Single Sign-On instance in Re-pointing and re-registering VMware vCenter Server 5.1 / 5.5 and components (2033620).

  3. Configure and replicate the information obtained from the Document the existing VMware vCenter Single Sign-On permissions used within your VMware vCenter Signle Sign-On domain section to the new VMware vCenter Single Sign-On deployment.

Repoint VMware vCenter Inventory Service to the new VMware vCenter Single Sign-On deployment

To repoint VMware vCenter Inventory Service to the new VMware vCenter Single Sign-On deployment:
  1. Log on as an administrative user to the VMware vCenter Server machine.
  2. Repoint the VMware vCenter Inventory Service to the new VMware vCenter Single Sign-On deployment.

    For more information, see the Re-register vCenter Inventory Service with vCenter Single Sign-On section in Re-pointing and re-registering VMware vCenter Server 5.1 / 5.5 and components (2033620).

Repoint VMware vCenter Sever to the new VMware vCenter Single Sign-On deployment

To repoint VMware vCenter Inventory Service to the new VMware vCenter Single Sign-On deployment:
  1. Log on as an administrative user to the VMware vCenter Server machine.
  2. Repoint the VMware vCenter Server to the new VMware vCenter Single Sign-On deployment.

    For more information, see the Register vCenter Server with a different vCenter Single Sign-On instance section in Re-pointing and re-registering VMware vCenter Server 5.1 / 5.5 and components (2033620).

Uninstall VMware vCenter Single Sign-On installed on the VMware vCenter Server machine

To uninstall VMware vCenter Single Sign-On installed on the VMware vCenter Server machine: 
  1. Log on as an administrative user to the VMware vCenter Server machine.
  2. Click Start > Control Panel.
  3. Under Programs, select Uninstall a program.
  4. Highlight VMware Single Sign-On and click Uninstall.

Upgrade VMware vCenter Single Sign-On to an External Platform Services Controller 

To upgrade the new VMware vCenter Single Sign-On deployment to an External Platform Services Controller, see Upgrading VMware vCenter Single Sign-On 5.5 to a VMware vCenter Server 6.0 Platform Services Controller 6.0 (2109560).

Upgrade VMware vCenter Server 5.1/5.5 to VMware vCenter Server 6.0 

To upgrade VMware vCenter Server 5.1/5.5 to VMware vCenter Server 6.0, see Upgrading VMware vCenter Server 5.5 to vCenter Server 6.0 with an external Platform Services Controller (2109562).

See Also

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 3 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 3 Ratings
Actions
KB: