This procedure describes upgrading Connection Server instances that are not paired with security servers. For example, this procedure applies to Connection Servers that are configured for connections to clients that are inside the corporate firewall.

Before you begin

  • Determine when to perform this procedure. Choose an available desktop maintenance window. The amount of time the upgrade takes depends on the number of Connection Server instances in the group. Budget 15 minutes to half an hour for each instance.

  • If you use View Composer, verify that View Composer has been upgraded. See Upgrade View Composer. After you upgrade Connection Server, you must add View Composer using Horizon Administrator.

  • Familiarize yourself with the security-related requirements of Horizon 7, and verify that these requirements are met. See Upgrade Requirements for View Connection Server. You might need to obtain and install a CA-signed SSL server certificate that includes certificate revocation information, verify that Windows Firewall with Advanced Security is set to on, and configure any back-end firewalls to support IPsec.

  • Verify that the server on which vCenter Server is installed has a CA (certificate authority)-signed SSL server certificate installed and configured. After you upgrade Connection Server, if vCenter Server does not use a CA-signed certificate, the default self-signed certificate is shown as invalid in Horizon Administrator, and a message indicates that vCenter Server is unavailable.

  • Complete the tasks listed in Preparing Connection Server for an Upgrade.

    Important:

    If any Local Mode desktops are checked out at the time you run the Connection Server installer to install the upgrade, the upgrade will fail.

  • Verify that you have a license that is valid for the new version.

    Note:

    When you upgrade from 6.0.x or 6.1.x to 6.2, your previous license will continue to work and the usage model will be set to Concurrent User. A new licensing model called Named User was added beginning with Horizon 6 version 6.2. You have the option of changing the licensing model to Named User. For more information, see http://www.vmware.com/files/pdf/products/horizon-view/VMware-Horizon-View-Pricing-Licensing-FAQ.pdf.

  • Verify that you have a domain user account with administrative privileges on the hosts that you will use to run the installer and perform the upgrade.

  • If you are unfamiliar with the vdmexport.exe utility, print the instructions for using it from the View Administration document. You will use this utility to back up the View LDAP database as part of the upgrade procedure.

You do not need to make any changes to the configuration of existing load balancers.

About this task

For Connection Server instances that are paired with security servers, use the procedure described in Upgrade View Security Servers and Their Paired View Connection Servers.

Note:

This procedure describes an in-place upgrade. To migrate to a different machine, see Upgrade to the Latest Version of Connection Server on a Different Machine.

Procedure

  1. If you are using a load balancer to manage a group of Connection Server instances, disable the server that hosts the Connection Server instance that you are about to upgrade.
  2. Log in to Horizon Administrator and disable the Connection Server instance that you are about to upgrade.
    1. Go to View Configuration > Servers and click the Connection Servers tab.
    2. Select the Connection Server instance in the list and click the Disable button above the table.
    3. Click OK to confirm disabling the server.
  3. On the host of the Connection Server instance, download and run the installer for the new version of Connection Server.

    The installer filename is VMware-viewconnectionserver-x86_64-y.y.y-xxxxxx.exe, where xxxxxx is the build number and y.y.y is the version number. You do not need to stop any services before performing the upgrade. The installer stops and restarts services as necessary. In fact, the VMwareVDMDS service must be running in order to upgrade the View LDAP database.

    The installer determines that an older version is already installed and performs an upgrade. The installer displays fewer installation options than during a fresh installation.

    The View LDAP is also upgraded.

    Note:

    Before performing the upgrade, the installer does a replication status check to determine whether the server can communicate with the other servers in the replicated group and whether the server can fetch LDAP updates from the other servers in the group. If the status check fails, the upgrade does not proceed.

  4. Verify that the VMware Horizon Connection Server service restarts after the installer wizard closes.
  5. Log in to Horizon Administrator and enable the Connection Server instance that you just upgraded.
    1. Go to View Configuration > Servers and click the Connection Servers tab.
    2. Select the Connection Server instance in the list and click the Enable button above the table.
    3. In the Version column, verify that the new version is displayed.
  6. Go to View Configuration > Product Licensing and Usage, click Edit License, enter the license key, and click OK.
  7. If you are using a load balancer for managing this Connection Server instance, enable the server that you just upgraded.
  8. Verify that you can log in to a remote desktop.
  9. Repeat the previous steps to upgrade each Connection Server instance in the group.
    Important:

    If you do not upgrade all Connection Server instances in a replicated group, the health indicators in the Horizon Administrator dashboard might show that one or more instances are in an error state. This situation arises because different versions supply different kinds of data. The solution is to upgrade all instances in the replicated group.

  10. Use the vdmexport.exe utility to back up the newly upgraded View LDAP database.

    If you have multiple instances of Connection Server in a replicated group, you need only export the data from one instance.

  11. Log in to Horizon Administrator and examine the dashboard to verify that the vCenter Server and View Composer icons are green.

    If either of these icons is red and an Invalid Certificate Detected dialog box appears, you must click Verify and either accept the thumbprint of the untrusted certificate, as described in "What to Do Next," or install a valid CA-signed SSL certificate.

    For information about replacing the default certificate for vCenter Server, see the VMware vSphere Examples and Scenarios document.

  12. Verify that the dashboard icons for the connection server instances are also are green.

    If any instances have red icons, click the instance to determine the replication status. Replication might be impaired for any of the following reasons:

    • A firewall might be blocking communication

    • The VMware VDMDS service might be stopped on a Connection Server instance

    • The VMware VDMS DSA options might be blocking the replications

    • A network problem has occurred

What to do next

To use a default or self-signed certificate from vCenter Server or View Composer, see Accept the Thumbprint of a Default SSL Certificate.

If you have an older version of vCenter Server, see Enable TLSv1.0 on vCenter Connections from Connection Server.

If the upgrade fails on one or more of the Connection Server instances, see Create a Replicated Group After Reverting Connection Server to a Snapshot.

Important:

If you plan to use enhanced message security mode for JMS messages, make sure that firewalls allow Connection Server instances to receive incoming JMS traffic on port 4002 from desktops and security servers. Also open port 4101 to accept connections from other Connection Server instances.

If you ever reinstall Connection Server on a server that has a data collector set configured to monitor performance data, stop the data collector set and start it again.