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

Upgrading to vCenter Single Sign-On 5.5 on a Microsoft Windows platform (2058249)

  • 2 Ratings

Purpose

This article provides step-by-step guidance for upgrading to VMware vCenter Single Sign-On (SSO) 5.5 using the Custom Install method.

This article assumes that:
  • You have backed up your existing SSO service. For more information, see Backing up and restoring the vCenter Single Sign-On (SSO) configuration (2034928).
  • You have reviewed all of the upgrade documentation. For more information, see the vSphere Upgrade Guide. 
  • You have met all minimum software and hardware requirements for vSphere 5.5. For more information, see the System Requirements  in the vSphere Installation and Setup Guide.

    Notes:

  • You have upgraded all other VMware products in the correct order.

    Note: vCloud Director, vCloud Networking and Security, and Horizon View products must be upgraded before upgrading vCenter Server. For more information, see Update sequence for vSphere 5.5 and its compatible VMware products (2057795).

  • You have configured both a forward and reverse lookup zone for this Microsoft Windows Server. For more information on configuring reverse lookup zones in a Microsoft Active Directory domain, see the Microsoft TechNet article Adding a Reverse Lookup Zone.
  • If you plan to authenticate against Active Directory, you have joined your Microsoft Windows server to the domain. For more information, see the Microsoft TechNet article How to Join Your Computer to a Domain.

    Note: The preceding link was correct as of September 19, 2013. If you find the link is broken, provide feedback and a VMware employee will update the link.

  • You are upgrading an existing vSphere environment that has services located in various Microsoft Windows servers. This may have be done if this SSO instance must act as a single node in a highly available configuration using a third party load balancer.

Important: Having the services located on multiple Microsoft Windows servers increases the complexity of maintaining the environment. Additional complexity comes in the form of administration overhead and licensing costs. In addition, this configuration introduces points of failure, such as network connectivity and name resolution related issues which may involve engaging additional vendors during outages and maintenance windows. Please make sure that your infrastructure is configured in a redundant manner and you allocate appropriate resources considering these factors.

Resolution

Upgrade steps for Single Sign-On 5.5

  1. Mount the vSphere 5.5 installation media. The installation wizard appears.
  2. In the left pane, under Custom Install, click Single Sign-On Install and then click Install.

    Note: If any of the prerequisites are not met, they are listed in the right pane under Prerequisites.

  3. In the welcome screen, click Next.
     
    In the welcome screen, Click Next. If a previous version of vCenter Single Sign-On (SSO) is installed, you see this message in the welcome screen:

    An earlier version of vCenter Single Sign-On is already installed on this computer and will be upgraded to vCenter Single Sign-On 5.5.0.

  4. Review the End User License Agreement. If you agree, select the I accept the terms in the license agreement option and then click Next.
  5. Review the Prerequisites check screen and then click Next. The installer notifies that a previous version is detected and that Users, Groups, Solution Users, and Lookup Service artifacts will be migrated.
  6. Click Next.

    Note: Steps 7 and 8 are done if upgrading from vCenter Server 5.0 and earlier. 

  7. Select a deployment mode and click Next.



    The various deployment mode options include:

    • vCenter Single Sign-On for your first vCenter Server – Select this option to deploy your first SSO server. This server becomes the first SSO server in a new vSphere authentication domain.

      After you select this option:

      1. Provide a password for the SSO administrator user and click Next.

        Note: This dialog shows information related to a domain by the name vsphere.local. This is not a domain that is auto-detected within the existing environment, but a net new domain used internally by vSphere. The administrator@vsphere.local account performs the same function as the admin@System-Domain account in previous versions of vSphere.

        For more information about the administrator@vsphere.local account, see the vSphere Software Components section of the vCenter Server and Host Management Guide.

      2. Provide a site name and click Next.

        Note: The site name is used in environments where there are SSO servers in multiple sites. Ensure to select this name carefully because it cannot be changed in the vSphere Web Client after the installation completes.


    • vCenter Single Sign-On for an additional vCenter Server in an existing site – Select this option to add this SSO server to an existing vSphere authentication domain site. This server replicates information from an existing SSO server in the vSphere authentication domain.

      After selecting this option:

      1. Under vCenter Sign-On Information, specify the Partner host name. This is the host name of the alternative SSO instance.
      2. Specify the password for the administrator@vsphere.local user for the alternate instance and click Next.

        Certificate information for the partner service you provided is displayed and you are asked if you trust the certificate. If you trust the certificate, click Continue.

      3. Select the original site name defined during the installation for the primary node name from the dropdown and click Next.

        Note: Both SSO instances share a common site name. Using this deployment mode is essential for configuring a load balanced HA Single Sign-On implementation.

    • vCenter Single Sign-On for an additional vCenter Server with a new site – Select this option to add the SSO server to an existing vSphere authentication domain and create a new site. This server replicates information from an existing SSO server in the vSphere authentication domain.

      After selecting this option:

      1. Under vCenter Sign-On Information, specify the Partner host name. This is the host name of the alternative SSO instance.
      2. Specify the password for the administrator@vsphere.local user and click Next.

        Certificate information for the partner service you provided is displayed and you are asked if you trust the certificate. If you trust the certificate, click Continue.

      3. Enter a name for the new site.

        Note: The site name is used in environments where there are SSO servers in multiple sites. Ensure to choose this name carefully because this name cannot be changed in the vSphere Web Client after the installation completes.

  8. Optionally, provide an alternative installation location and then click Next.

    Notes:
    • The installation requires 2 GB of disk space to be available. For more information, see the Hardware Requirement for vCenter Server, the vSphere Web Client, vCenter Inventory Service, and vCenter Single Sign-On section in the vSphere Installation and Setup Guide.
       
    • The path must conform to NTFS naming restrictions. For more information, see the Microsoft article Naming Files, Paths, and Namespaces.

      The preceding link was correct as of September 19, 2013. If you find the link is broken, provide feedback and a VMware employee will update the link.

  9. In the confirmation screen, click Install.
  10. When the installation completes, click Finish.

Post upgrade of Single Sign-On 5.5

After installing SSO 5.5:

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

  • 2 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.
  • 2 Ratings
Actions
KB: