Upgrading Embedded vCenter 5.1/5.5 to vCenter 6.0 in linked mode

Objective: vCenter 6.0 in linked mode is not possible with embedded PSC. To configure vCenter 6.0 in linked mode, the vCenter should be pointing to external PSC.

Find the recommended topologies here

In this article I explained step by step process to upgrade your existing VMware vCenter 5.1/5.5 to 6.0 in linked mode.
  • Deploy a new VMware vCenter Single Sign-On machine for VMware vCenter Server on PSC1
  • Deploy a second VMware vCenter Single Sign-On machine for VMware vCenter Server on PSC2
  • Repoint the VMware vSphere Web Client on vCenter 1 and 2 to their corresponding VMware vCenter Single Sign-On deployments
  • Repoint the VMware vCenter Inventory Service on vCenter 1 and 2 to their corresponding VMware vCenter Single Sign-On deployments
  • Repoint the VMware vCenter Server on vCenter 1 and 2 to their corresponding VMware vCenter Single Sign-On deployments
  • Remove VMware vCenter Single Sign-On installed on vCenter 1 and 2
  • Upgrade VMware vCenter Single Sign-On to an External Platform Services Controller PSC1 and PSC2
  • Upgrade VMware vCenter Server 5.1/5.5 on vCenter 1 and 2 to VMware vCenter Server 6.0

psc

Precautions:

  • Take backup of SQL database for all the vCenter. proper backup /snapshot of vCenter server.
  • Check upgrade path. To check upgrade path use the VMware Interop Matrix

Lets start our process

Note: I have deployed two vCenters named vCenter1 and vCenter2, New Windows machines for external SSO/PSC named PSC1 and PSC2 respectively. This article uses same names for upgrading vCenter 5.5 to vCenter 6.0

Deploy a new VMware vCenter Single Sign-On machine for VMware vCenter Server on PSC1

  • 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.
  • Check Build number of vCenter and use same build number ISO to install Single Sign-On.
  • To verify your build number check VMware KB article here
  • Once you are sure with build number 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 second VMware vCenter Single Sign-On machine for VMware vCenter Server on PSC2

  • Install 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.
  • Follow the same instructions as mentioned above before installing Single Sign-On.
  • Install Single Sign on PSC2.

When prompted:

  • Select the deployment mode Multisite.

17

  • Enter the information to point to the partner VMware vCenter Single Sign-On node installed in the previous step, Deploy a new VMware vCenter Single Sign-On machine for VMware vCenter Server on PSC1.
    • Enter the partner host name.The partner host name is the IP address or DNS name of the existing VMware vCenter Single Sign-On server to replicate from.
    • Enter the password for the VMware vCenter Single Sign-On administrator account of the existing VMware vCenter Single Sign-On server.

18

  • Review and accept the partner certificate.
  • Enter the new site name.
  • Accept or change the HTTPS port for VMware vCenter Single Sign-On.
  • Accept or change the default VMware vCenter Single Sign-On installation folder.
  • Review the installation options and click Install.

Repoint the VMware vSphere Web Client on vCenter 1 and 2 to their corresponding VMware vCenter Single Sign-On deployments

To repoint the VMware vSphere Web Client to the new VMware vCenter Single Sign-On deployment:

  • Log on as an administrative user to each VMware vCenter Server machine with the VMware vSphere Web Client installed.
  • Repoint the VMware vSphere Web Client to its corresponding VMware vCenter Single Sign-On deployment.
  • To repoint vSphere web client to its corresponding VMware vCenter Single Sign-On. Open command prompt with “Run as administrator”
  • Change Directory to %Vmware vCenter installation path%\Infrastructure\vSphereWebClient\scriptswc1
  • Use the following command to repoint vSphere Web Client to corresponding VMware vCenter Single Sign-On
  • Run the client-repoint.bat command to register the vSphere Web Client with a different vCenter Single Sign-On:

client-repoint.bat lookup_service_url "single_sign_on_admin_user" "single_sign_on_admin_password"

For vCenter Server 5.1:

client-repoint.bat https://machinename.corp.com:7444/lookupservice/sdk "admin@System-Domain" "SSO_pw1@"

For vCenter Server 5.5:

client-repoint.bat https://machinename.corp.com:7444/lookupservice/sdk "administrator@vSphere.local" "SSO_pw1@"wc2

Repoint the VMware vCenter Inventory Service on vCenter 1 and 2 to their corresponding VMware vCenter Single Sign-On deployments

To repoint VMware vCenter Inventory Service to the new VMware vCenter Single Sign-On deployment:

  • Log on as an administrative user to each VMware vCenter Server machine with the VMware vCenter Inventory Service is installed.
  • To register Inventory service with corresponding VMware Single Sign-On.
  • Open Command Prompt with “Run as administrator”
  • Change Directory to %Vmware vCenter installation path%\Infrastructure\Inventory Service\scriptsis1
  • Run the is-change-sso.bat command to update the stored configuration information of the Inventory Service:

is-change-sso.bat ssoServerUrl "ssoAdminuser" "ssoAdminPassword"

In vCenter Server 5.1:

is-change-sso.bat https://machinename.corp.com:7444/lookupservice/sdk "admin@System-Domain" "SSO_pw1@"

In vCenter Server 5.5:

is-change-sso.bat https://machinename.corp.com:7444/lookupservice/sdk "administrator@vSphere.local" "SSO_pw1@"

is2

  • Once re-pointing of Inventory Service is successful. Restart VMware Inventory Server Service to take effect.

Repoint the VMware vCenter Server on vCenter 1 and 2 to their corresponding VMware vCenter Single Sign-On deployments

To repoint VMware vCenter Server to the new VMware vCenter Single Sign-On deployments:

  • Log on as an administrative user to each VMware vCenter Server machine.
  • To register vCenter service with corresponding VMware Single Sign-On.
  • Open Command Prompt with “Run as administrator”
  • Change directory to %Vmware vCenter installation path%\Infrastructure\VirtualCenter Server\ssoregtoolvc2
  • Unzip the sso_svccfg.zip file.vc1
  • Run this command to register vCenter Server to a different Single Sign-On instance:

repoint.cmd configure-vc --lookup-server lookup_service_url --usersingle_sign_on_admin_user --password single_sign_on_admin_password --openssl-path "path_to_OpenSSL_bin_directory/"

In vCenter Server 5.1:

repoint.cmd configure-vc --lookup-server https://machinename.corp.com:7444/lookupservice/sdk --user "admin@System-Domain" --password "SSO_pw1@" --openssl-path "C:\Program Files\VMware\Infrastructure\Inventory Service\bin/"

In vCenter Server 5.5:

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

  • Once re-pointing of vCenter Service is successful. Manually restart vCenter Server Service

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

To uninstall VMware vCenter Single Sign-On on PSC1 and PSC2:
  1. Log on as an administrative user to PSC1.
  2. Click Start > Control Panel.
  3. Under Programs, select Uninstall a program.
  4. Highlight VMware Single Sign-On and click Uninstall.
  5. Repeat this process for PSC2.

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

To Upgrade Single Sign-On to Platform Service Controller.

  • Mount 6.0 ISO
  • Start Insatallation
  • Select vCenter Server for Windows > Installpsc1
  • Before proceeding with Installation make sure vCenter Single Sign-On is detected.psc2
  • Accept License Agreementpsc3
  • Provide Single Sign-On Credentialspsc4
  • Configure Network Ports If requiredpsc5
  • Configure vCenter Directory (If Required)psc6
  • Verify the configuration and Start Upgrade Process.psc7
  • Once PSC upgrade process is completed proceed with vCenter Upgradationpsc8
  • Follow the same steps on PSC 1 and PSC 2 to upgrade from SSO 5.1/5.5 to PSC 6.0

Upgrade VMware vCenter Server 5.1/5.5 on vCenter 1 and 2 to VMware vCenter Server 6.0

Hurrey!! Finally We reached on our Final Step of Migrating vCenters 5.1/5.5 in linked mode to vCenter 6.0 in linked mode.

To upgrade VMware vCenter Server 5.1/5.5 to Vmware vCenter Server 6.0

  • Start Installation and continue process. Make sure vCenter 6.0 Installation detects vCenter 5.1/5.5 onlyc1
  • Accept License agreement, In next step provide vCenter 5.5 credentialsc2
  • If your vCenter had embedded SQL express database it will be automatically migrated to vPostgresc3
  • re-check and provide PSC admin passwordc4
  • Configure Network Portsc5
  • Configure Destination Folder path.c6
  • Proceed in completing Installationc7
  • We are successfully completed in upgrading one vCenter 5.1/5.5 to 6.0.c8
  • Follow the same steps on both vCenter. Migration of vCenter 5.1/5.5 in linked mode to vCenter 6.0 linked mode is successfully done once you complete this process.

I hope the post is useful. If there are any feedback,feel free to post it. I would be happy to hear.

Written By chintagowtham

3 Comments on “Upgrading Embedded vCenter 5.1/5.5 to vCenter 6.0 in linked mode

  1. Ravi Prasad Reply

    July 4, 2016 at 12:12

    Hello ,
    Good Post , have few questions.
    1. You are moving Embedded SSO to External SSO on First go
    2.uninstall SSO on second go
    3. upgrade SSO as PSC finally
    correct me if understanding is wrong.
    just curious to know below
    1. repoint to external sso does this Migrate embedded SSO DB to external SSO ?
    2. why uninstall? why not direc upgrade?
    3. even after uninstall why PSC able to see previous sso deployment?
    4.what are steps needed if we use Vcenter appliance and windows vcenter in combination from original setup?

    Thanks,
    Ravi Prasad

    • chintagowtham Reply

      July 4, 2016 at 8:34

      Hi Ravi,

      The questions are great thank you for posting.

      1. repoint to external sso does this Migrate embedded SSO DB to external SSO ?
      — Repointing vCenter components to external SSO will not migrate SSO DB.

      2. why uninstall? why not direc upgrade?
      — We can do direct upgrade but if we have SSO component also available on same embedded vCenter it will also upgrade SSO. So it would be better if we uninstall SSO to make sure no one confuse.

      3. even after uninstall why PSC able to see previous sso deployment?
      — PSC only detects if SSO is installed but while upgrading vCenter it requires PSC details. If SSO is uninstalled only vCenter components will be upgraded.

      4.what are steps needed if we use Vcenter appliance and windows vcenter in combination from original setup?
      — I think vCenter appliance in linked mode is not possible for 5.1/5.5 vSphere.

  2. chintagowtham Reply

    July 4, 2016 at 8:38

    Hi All, from vCenter 6.0 U2 we have another method to update vCenter 5.1/5.5 to vCenter 6.0 in linked mode. I will provide step by step article in my next post.

Leave a Reply

Your email address will not be published. Required fields are marked *