7.0
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
- Preparing View Connection Server for an Upgrade
- Upgrade View Connection Servers in a Replicated Group
- Enable TLSv1.0 on vCenter Connections from Connection Server
- Upgrade to the Latest Version of View Connection Server on a Different Machine
- Create a Replicated Group After Reverting View Connection Server to a Snapshot
- 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 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
5 Restart the VMware Horizon View Composer service.
TLSv1.0 connections from View Composer to vCenter are now enabled.
6 In the Windows Registry on the View Composer machine, navigate to HKLM\SOFTWARE\VMware,
Inc.\VMware View Composer.
7 Create or edit the String value EnableTLS1.0 and set it to 1.
8 If the View Composer host is a 64-bit machine, navigate to HKLM\SOFTWARE\WOW6432Node\VMware,
Inc\VMware View Composer.
9 Create or edit the String value EnableTLS1.0 and set it to 1.
10 Restart the VMware Horizon View Composer service.
TLSv1.0 connections from View Composer to ESXi hosts are now enabled.
Manually Upgrading the View Composer Database
Rather than letting the View Composer installer upgrade the database when a schema update is required,
you can manually upgrade the database. You can use the SviConfig utility when you must observe the
upgrade process more closely or when upgrade tasks must be distributed to IT administrators with different
responsibilities.
When you upgrade View Composer to a version with an updated database schema, an installer prompt asks
if you want the wizard to upgrade the database. If you choose not to use the installer wizard, you must use
the SviConfig utility to upgrade the database and migrate the existing data.
Using the SviConfig command-line utility has the following advantages:
n
This utility returns result codes and creates a log of the database upgrade to simplify troubleshooting if
the upgrade fails.
n
You can separate the upgrade tasks. A vSphere or View administrator can run the View Composer
installer to upgrade the software. A database administrator (DBA) can use SviConfig to upgrade the
View Composer database.
n
The software upgrade and the database upgrade can occur during different maintenance windows. For
example, your site might run database-maintenance operations on weekends only, whereas software-
maintenance tasks can occur during the week.
Run SviConfig to Manually Upgrade the Database
With the SviConfig command-line utility, you can upgrade the View Composer database separately from
the View Composer software. This utility also creates a log file to simplify troubleshooting if the upgrade
fails.
IMPORTANT Only experienced View Composer administrators should use the SviConfig utility. This utility
is intended to resolve issues relating to the View Composer service.
Prerequisites
n
Back up the View Composer database. For instructions, see the documentation for your database server.
n
Verify that you know the database source name (DSN) for the View Composer database.
n
Verify that you know the user name and password for the database administrator account for this
database.
Chapter 3 Upgrading View Server Components
VMware, Inc. 23