Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Upgrading Single Sign-On 5.1 to 5.5 when vCenter Server Heartbeat is installed (2059820)

Purpose

This article provides the steps to upgrade vSphere Single Sign-On (SSO) 5.1 to 5.5.

If Single Sign-On 5.5 cannot be installed on a separate machine (not the Primary or Secondary node), you must perform the procedure in this article to upgrade from SSO 5.1 to SSO 5.5.

Note: This article only applies to SSO 5.1 protected by vCenter Server Heartbeat being upgraded to 5.5.

Resolution

Note: Before starting this procedure, download and extract the attached file (SSOUpgradeUtil.zip) and save it in a location for use on both the Primary and Secondary nodes.

To upgrade Single Sign-On on the Secondary node:

  1. If the Primary node is active, use the vCenter Server Heartbeat Console on the Secondary node to perform a manual failover to make the Secondary node active. If the Secondary node is currently active, go to Step 2.

    Note: Only proceed to step 2 when the Secondary node is currently active.

  2. Shut down vCenter Server Heartbeat on both the Primary and Secondary nodes, leaving protected applications running on the Secondary (active) node.
  3. Open an elevated command prompt and run this command:

    SSOupgradeUtil.exe pre

  4. Start VMware vCenter Installer for the version you want to upgrade to and select vCenter Single Sign-On from the list.
  5. On the vCenter Single Sign-On Prerequisites page, ensure the IP address listed is the Public IP. If the channel or management IP is listed, temporarily remove the IP from the NIC and click Back and Next to refresh the Prerequisites page.
  6. Proceed with the SSO upgrade.
  7. If errors are encountered during the upgrade process, research the cause of the upgrade failure. If the issue can be resolved, it is safe to proceed with the upgrade procedure.
  8. After the upgrade completes, open an elevated command prompt and run this command:

    SSOupgradeUtil.exe post

  9. Back up the vCenter Server and vSphere Update Manager (VUM) (if present) databases and SSL certificates.
  10. Upgrade the other vCenter Server components installed on the node.
  11. Start VMware vCenter Server Heartbeat on the Secondary node only:

    1. Using the vCenter Server Heartbeat Console, verify on the Applications: Summary page that the Application state is Started.
    2. Click Stop Applications.

  12. Stop VMware vCenter Server Heartbeat on the Secondary node from the system tray, and choose to shut down the protected applications.
  13. Change the node's role to Secondary/passive:

    1. Launch the vCenter Server Heartbeat Configure Server wizard and click the Machine tab.
    2. Change the Active Server to Primary and click Finish.

  14. Start VMware vCenter Server Heartbeat on the Secondary node only.
  15. Stop VMware vCenter Server Heartbeat on the Secondary node.

To upgrade Single Sign-On on the Primary node:

Note: Only perform these steps after successfully completing the upgrade of the Secondary node.

  1. Before beginning the upgrade on the Primary node, restore the vCenter Server and vSphere Update Manager (if present) databases that were backed up in the Secondary node upgrade procedure.
  2. Change the node's role to Primary/active:

    1. Launch the vCenter Server Heartbeat Configure Server wizard and click the Machine tab. Change the node's role for the current (Primary) node to active and click Finish.
    2. Start VMware vCenter Server Heartbeat on the Primary node only.
    3. Using the vCenter Server Heartbeat Console, verify on the Server: Summary page that the Applications are Started.
    4. Shut down vCenter Server Heartbeat on the Primary node, leaving protected applications running.

  3. Open an elevated command prompt and run this command:

    SSOupgradeUtil.exe pre

  4. Start the VMware vCenter Installer for the version you want to upgrade to and select vCenter Single Sign-On from the list.
  5. On the vCenter Single Sign-On Prerequisites page, ensure the IP address listed is the Public IP. If the channel or management IP is listed, temporarily remove the IP from the NIC and click Back and Next to refresh the Prerequisites page.
  6. Proceed with the SSO upgrade.
  7. If errors are encountered during the upgrade process, research the cause of the upgrade failure. If the issue can be resolved, it is safe to proceed with the upgrade procedure.
  8. After the upgrade completes, open an elevated command prompt and run this command:

    SSOupgradeUtil.exe post

  9. Upgrade the other vCenter Server components installed on the node.
  10. Start VMware vCenter Server Heartbeat on both the Primary and Secondary nodes.
  11. Allow the nodes to connect and synchronize, and wait for the Full System Check to complete.
  12. Using the vCenter Server Heartbeat Console, navigate to the Data: Replication page and click Full Registry Check.
  13. Uninstall and re-install the Virtual Center plug-in:

    1. Using the vCenter Server Heartbeat Console, verify that all status icons on the Server: Summary page are green, which indicates that the Start process has completed and all protected services are started.
    2. Navigate to the Applications: Plug-ins page, select the VirtualCenterNFPlugin and click Uninstall.
    3. After the plug-in has been removed from the plug-ins list, click Install.
    4. Navigate to the location of the vCenter Server plug-in (the default location is C:\Program Files\VMware\VMware vCenter Server Heartbeat\R2\plugins\VMwareVirtualCenter\201.5.4.13406) and select the VirtualCenterNFPlugin.dll file.
    5. After the plug-in has been added, select it, click Edit, then enter the credentials used to connect to vCenter Server.

Additional Information

vCSHB-Ref-2631

Update History

10/29/2013 - Add note to Purpose to clarify article applicability.

Attachments

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

  • 1 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)
  • 1 Ratings
Actions
KB: