Upgrade VMware vCenter 5.5 to 6.5 in Enhanced Linked Mode

In this post we will discuss how to upgrade vCenter 5.5 with Embedded PSC to 6.5 in Enhanced Linked Mode (ELM). You can reference the details at below:

Lab Environment:
vCenter Server A – VMware vCenter 5.5 Windows with Embedded PSC1
vCenter Server B – VMware vCenter 5.5 Windows with Embedded PSC2

Final Configuration:
vCenter Server A – VMware vCenter 6.5
vCenter PSC1 – vCenter 6.5 Platform Service Controller
vCenter Server B – VMware vCenter 6.5
vCenter PSC2 – vCenter 6.5 Platform Service Controller

Supported and deprecated topologies for VMware vSphere 6.5 (2147672)
https://kb.vmware.com/s/article/2147672

vCenter Single Sign-On and Platform Services Controller Compatibility Matrix with vCenter Server (2120504)

https://kb.vmware.com/s/article/2120504

Prerequisites:

  • Deploy a new 1st VMware vCenter 5.5 SSO machine for VMware vCenter ServerA.
  • Deploy a 2nd VMware vCenter 5.5 SSO machine for VMware vCenter ServerB.

Migration & Upgrade Flow:

  • Re-point the VMware vSphere Web Client on vCenterA and B.
  • Re-point the VMware vCenter Inventory Service on vCenterA and B.
  • Re-point the VMware vCenter Server on vCenterA and B.
  • Uninstall VMware vCenter Single Sign-On installed on vCenterA and B.
  • Upgrade VMware vCenter SSO to an External Platform Services Controller PSC1 and PSC2.
  • Upgrade VMware vCenter Server 5.5 on vCenterA and B to version 6.0.
  • Upgrade VMware vCenter PSC 6.0 to 6.5 on PSC1 and PSC2.
  • Upgrade VMware vCenter Server 6.0 on vCenterA and B to version 6.5.

Deploy a new 1st VMware vCenter 5.5 SSO machine for VMware vCenter ServerA

  • Deploy a new Microsoft Windows virtual machine that meets the requirements for your version of VMware vCenter Single Sign-On.
  • Install Single Sign-On by vCenter Server Windows installation (same the build-in number of running vCenter).
  • Once you confirm the configuration, then install Single Sign-On on PSC1.

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

Deploy a 2nd VMware vCenter 5.5 SSO machine for VMware vCenter ServerB

  • Deploy a new Microsoft Windows virtual machine that meets the requirements for your version of VMware vCenter Single Sign-On.
  • Install Single Sign-On by vCenter Server Windows installation (same the buildin number of running vCenter).
  • Select the deployment mode Multisite.

  • Enter the information to point to the partner VMware vCenter SSO node installed in the previous SSO installation for vCenterA.

  • Review the installation options and click Install Single Sign-On on PSC2.

Repoint the VMware vSphere Web Client on vCenterA and B

  • Change Directory to %Vmware vCenter installation path%\Infrastructure\vSphereWebClient\scripts.
  • Use the following command to repoint vSphere Web Client to corresponding VMware vCenter Single Sign-On.

client-repoint.bat https://machinename.corp.com:7444/lookupservice/sdk “administrator@vSphere.local” “SSO Password”

Repoint the VMware vCenter Inventory Service on vCenterA and B

  • Change Directory to %Vmware vCenter installation path%\Infrastructure\Inventory Service\scripts

is-change-sso.bat https://machinename.corp.com:7444/lookupservice/sdk “administrator@vSphere.local” “SSO Password”

NOTE: Once re-pointing of Inventory Service is successful, please restart the VMware Inventory Server Service to take effect.

Repoint the VMware vCenter Server on vCenterA and B

  • Change directory to %Vmware vCenter installation path%\Infrastructure\VirtualCenter Server\ssoregtool
  • Run this command to register vCenter Server to a different Single Sign-On instance.

repoint.cmd configure-vc –lookup-server https://machinename.corp.com:7444/lookupservice/sdk –user “administrator@vSphere.local” –password “SSO password” –openssl-path “C:\Program Files\VMware\Infrastructure\Inventory Service\bin/”

NOTE: Once re-pointing of vCenter Service is successful, please restart vCenter Server Service manually

Uninstall VMware vCenter Single Sign-On installed on vCenter 1 and 2

  • Click Start > Control Panel.
  • Under Programs, select Uninstall a program.
  • Highlight VMware Single Sign-On and click Uninstall.
  • Repeat this process for PSC2.

Upgrade VMware vCenter SSO to an External Platform Services Controller PSC1 and PSC2

  • Mount vCenter 6.0 installation ISO and start Installation.

  • Select vCenter Server for Windows > Install
  • Then vCenter Single Sign-On 5.5 is detected and will be ugprade to Service Platform Controller 6.0.
  • Provide Single Sign-On Credentials.
  • Configure Network Ports.
  • Verify the configuration and Start Upgrade Process.
  • Once PSC upgrade process is completed.
  • Follow the above same procedures to upgrade from SSO 5.5 to PSC 6.0 on vCenterB.

Upgrade VMware vCenter Server 5.5 on vCenterA and B to version 6.0

  • Start vCenter Installation and continue process, vCenter 6.0 Installation detects vCenter 5.5 only at this time and will be upgrade to vCenter 6.0.
  • Provide vCenter 5.5 credentials.
  • If your vCenter DB is embedded SQL expres it will be automatically migrated to vPostgres.
  • Provide PSC administrator password.
  • Configure Network Ports.
  • Proceed vCenter upgrade.
  • Follow the same above steps to upgrade from vCenter 5.5 to 6.0 on vCenterB.

Upgrade VMware vCenter PSC 6.0 to 6.5 on PSC1 and PSC2

  • Mount vCenter 6.5 installation ISO and start Installation.
  • Select vCenter Server for Windows > Install

  • Then vCenter PSC 6.0 is detected and will be ugprade to PSC 6.5.
  • Provide Single Sign-On Credentials.
  • Configure Network Ports.
  • Verify the configuration and Start Upgrade Process.
  • Once PSC upgrade process is completed.
  • Follow the same above steps to upgrade from PSC 6.0 to 6.5 on vCenterB.

Upgrade VMware vCenter Server 6.0 on vCenterA and B to version 6.5

  • Start vCenter Installation and continue process, vCenter 6.5 Installation detects vCenter 6.0 only at this time and will be upgrade to vCenter 6.5.
  • Provide vCenter 6.0 credentials.
  • Provide PSC administrator password.
  • Configure Network Ports.
  • Proceed vCenter upgrade.
  • Follow the same above steps to upgrade from vCenter 6.0 to 6.5 on vCenterB.

Finally the vCenter Server 6.5 is completed successfully and both vCenter servers are running in ELM.

Optional Information:

Now there are no any tool that can be supported to migrate External PSC into Embedded PSC. For vCenter 6.7 Enhanced Linked Mode, it is only supported on Embedded PSC (up to 15). Currently the only option you spin up a new environment with the embedded PSC and migrate your configuration, hosts and virtual machines across to the new deployment.

4 comments

  1. Great article. Well done! Curious, why do you need to upgrade to from 5.5 to 6.0 then 6.5? Upgrade path from 5.5 to 6.5 is supported. I am sure there is a reason I am missing.

    Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s