6.2
Table Of Contents
- View Upgrades
- Contents
- View Upgrades
- View Upgrade Overview
- System Requirements for Upgrades
- Upgrading View Server Components
- Upgrading View Composer
- Upgrading View Connection Server
- Upgrading View Security Server
- Upgrading View Servers in a Cloud Pod Architecture
- Upgrade vCenter Server
- Accept the Thumbprint of a Default SSL Certificate
- Using View 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
The -exp option creates an exportable key pair. If a future migration is required, the keys can be
exported from this machine and imported to another machine. If you previously migrated the keys to
this machine without using the -exp option, you can import the keys again using the -exp option so that
you can export the keys in the future.
The registration tool imports the key pair data into the local key container.
What to do next
Install the new VMware Horizon View Composer service on the destination machine. Provide the DSN and
ODBC data source information that allows View Composer to connect to the same database information that
was used by the original VMware Horizon View Composer service. For installation instructions, see
"Installing View Composer" in the View Installation document.
Complete the steps to migrate View Composer to a new machine and use the same database. See “Migrate
View Composer with an Existing Database,” on page 26.
Upgrading View Connection Server
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 down time.
NOTE Before you can use the Horizon 6 version 6.2 feature for cloning a desktop pool, you must upgrade all
View Connection Server instances in a pod to Horizon 6 version 6.2 or later.
Preparing View Connection Server for an Upgrade
Before you upgrade View Connection Server or before you upgrade any of the vSphere components that
View 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 View Connection Server instances, perform the following tasks using only
one of the instances. Because the instances are replicated, the settings on one instance are the same as the
settings on the others:
n
If View 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 View 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 View Administrator and document all the global settings and settings for desktops and pools:
Pools section and Desktops section in the Inventory tree, and the Global Settings section in the View
Configuration tree.
For example, take a screen shot of the applicable settings.
n
If your deployment currently uses the Local Mode feature, ask end users to check in their Local Mode
desktops, or use View Administrator to roll back the Local Mode desktops so that no desktops are
shown as checked out in View Administrator.
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.
n
If your deployment currently uses the Local Mode feature, open View Administrator, go to View
Configuration > Servers, and remove all Transfer Server instances.
View Upgrades
30 VMware, Inc.