If your deployment uses load balancers to manage multiple View Connection Server instance, an upgrade of the Connection Server infrastructure can be performed with zero downtime.
About this task
This procedure describes upgrading View Connection Server instances that are not paired with security servers. For example, this procedure applies to View Connection Servers that are configured for connections to clients that are inside the corporate firewall. For View Connection Server instances that are paired with security servers, use the procedure described in Upgrade View Security Servers and Their Paired View Connection Servers.
This procedure describes an in-place upgrade. To migrate to a different machine, see Upgrade to the Latest Version of View Connection Server on a Different Machine.
Determine when to perform this procedure. Choose an available desktop maintenance window. The amount of time the upgrade takes depends on the number of View 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 View Connection Server, you must add View Composer using View Administrator.
Familiarize yourself with the security-related requirements of View, 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 View Connection Server, if vCenter Server does not use a CA-signed certificate, the default self-signed certificate is shown as invalid in View Administrator, and a message indicates that vCenter Server is unavailable.
Complete the tasks listed in Preparing View Connection Server for an Upgrade.Important:
If any Local Mode desktops are checked out at the time you run the View Connection Server installer to install the upgrade, the upgrade will fail.
Verify that you have a license for the new version.
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.
- If you are using a load balancer to manage a group of View Connection Server instances, disable the server that hosts the View Connection Server instance that you are about to upgrade.
- Log in to View Administrator and disable the View Connection Server instance that you are about to upgrade.
- Go to Connection Servers tab. and click the
- Select the View Connection Server instance in the list and click the Disable button above the table.
- Click OK to confirm disabling the server.
- On the host of the View Connection Server instance, download and run the installer for the new version of View 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.
- Verify that the VMware Horizon View Connection Server service restarts after the installer wizard closes.
- Log in to View Administrator and enable the View Connection Server instance that you just upgraded.
- Go to Connection Servers tab. and click the
- Select the View Connection Server instance in the list and click the Enable button above the table.
- In the Version column, verify that the new version is displayed.
- Go to Edit License, enter the license key, and click OK. , click
- If you are using a load balancer for managing this View Connection Server instance, enable the server that you just upgraded.
- Verify that you can log in to a remote desktop.
- Repeat the previous steps to upgrade each View Connection Server instance in the group.
If you do not upgrade all View Connection Server instances in a replicated group, the health indicators in the View 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.
- Use the vdmexport.exe utility to back up the newly upgraded View LDAP database.
If you have multiple instances of View Connection Server in a replicated group, you need only export the data from one instance.
- Log in to View 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.
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 the upgrade fails on one or more of the View Connection Server instances, see Create a Replicated Group After Reverting View Connection Server to a Snapshot.
If you plan to use enhanced message security mode for JMS messages, make sure that firewalls allow View 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 View Connection Server instances.
If you ever reinstall View 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.