Upgrades
Table Of Contents
- View Upgrades
- Contents
- View Upgrades
- View Upgrade Overview
- System Requirements for Upgrades
- Upgrading View Server Components
- Upgrading View Composer
- Upgrading Horizon Connection Server
- Upgrading View Security Server
- Upgrading View Servers in a Cloud Pod Architecture Environment
- Upgrading View Servers to Allow HTML Access
- Upgrade vCenter Server
- Accept the Thumbprint of a Default SSL Certificate
- Using Horizon 7 Group Policy Administrative Template Files
- Upgrade ESXi Hosts and Their Virtual Machines
- Upgrading Remote Desktops and Horizon Client
- Post-Upgrade Tasks to Enable New Features in Your View Setup
- Applying View Patches
- Upgrading vSphere Components Separately in a View Environment
- Index
Preparing Connection Server for an Upgrade
Before you upgrade Connection Server or before you upgrade any of the vSphere components that
Connection Server relies on, you must perform several tasks to ensure that these upgrades are successful.
Tasks to Perform on Only One Instance in a Replicated Group
Before you begin upgrading any Connection Server instances, perform the following tasks using only one of
the instances. Because the instances are replicated, the seings on one instance are the same as the seings
on the others:
n
If Connection Server is installed in a virtual machine, take a snapshot of the virtual machine.
For instructions on taking snapshots, see the vSphere Client online help. If you ever need to revert to
this snapshot and if you have other Connection Server instances in a replicated group, you must
uninstall those instances before you revert the master to the snapshot. After you revert, you can reinstall
the replicated instances and point to the instance you reverted.
You can label the snapshot Upgrade Preparation Phase.
n
Open Horizon Administrator and document all the global seings and seings for desktops and pools:
Pools section and Desktops section in the Inventory tree, and the Global Seings section in the View
Conguration tree.
For example, take a screen shot of the applicable seings.
n
If your deployment currently uses the Local Mode feature, ask end users to check in their Local Mode
desktops, or use Horizon Administrator to roll back the Local Mode desktops so that no desktops are
shown as checked out in Horizon Administrator.
I 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.
n
If your deployment currently uses the Local Mode feature, open Horizon Administrator, go to View
> Servers, and remove all Transfer Server instances.
n
Use the vdmexport.exe utility to back up the LDAP database.
For instructions, see the administration guide for your current version of the View Administration
document.
Tasks to Perform for Each Instance Just Before Upgrading
n
Verify that the virtual or physical machine on which the current Connection Server instance is installed
meets the system requirements for the new version.
See “Horizon Connection Server Requirements,” on page 15.
n
Document the IP address and system name of the machine on which Connection Server is installed.
n
Determine if your company has wrien any batch les or scripts that run against the View database on
the Connection Server instance, and if so, document their names and locations.
n
Open Horizon Administrator and document all the seings that are specic to this instance.
For example, go to View > Servers > Connection Servers, select the Connection Server
instance in the table and click Edit. You can take a screen shot of each tab in the Edit Connection Server
Seings dialog box.
View Upgrades
32 VMware, Inc.