6.0
Table Of Contents
- View Upgrades
- Contents
- View Upgrades
- View Component Compatibility Matrix
- View Upgrade Overview
- System Requirements for Upgrades
- Preparing for a View Upgrade
- Upgrading View Server Components
- Upgrade ESXi Hosts and Their Virtual Machines
- Upgrading Remote Desktops and Horizon Client
- Upgrade RDS Hosts That Provide Session-Based Desktops
- Upgrade View Agent
- Upgrade View Composer Desktop Pools
- Tasks for Upgrading Desktop Pools to Use Space Reclamation
- Tasks for Upgrading Desktop Pools to Use a Virtual SAN Datastore
- Upgrade the Client Application
- Configure the VMware Horizon Web Portal Page for End Users
- Applying View Patches
- Upgrading vSphere Components Separately in a View Environment
- Index
Solution
1 See the View Composer SviConfig log file for more information.
The default location of this file is C:\Users\All Users\VMware\View Composer\vmware-sviconfig.log.
The upgrade script logs a message for each failure.
2 Examine the log records to identify the desktops that failed to upgrade.
Option Action
The desktop exists but is
unavailable.
Make the desktop available again.
Depending on the cause of the failure, you might have to restart the ESXi
host or vCenter Server, or take another action.
The desktop does not exist.
Ignore the log message.
NOTE A deleted desktop might appear to exist in View Administrator if
an administrator deletes the desktop virtual machine directly in vSphere.
3 Run the SviConfig databaseupgrade command again.
Migrate View Composer to Another Machine
In some situations, you might need to migrate a VMware Horizon View Composer service to a new
Windows Server virtual or physical machine. For example, you might migrate View Composer and
vCenter Server to a new ESXi host or cluster to expand your View deployment. In addition, View Composer
and vCenter Server do not have to be installed on the same Windows Server machine.
You can migrate View Composer from the vCenter Server machine to a standalone machine or from a
standalone machine to the vCenter Server machine.
IMPORTANT These topics pertain to migrating the latest version of View Composer to another machine. You
must upgrade from the earlier version of View Composer before you perform these tasks.
If your current version of View Composer is installed on a machine that does not meet the system
requirements for the new version of View Composer, you cannot use these procedures. For example, if you
have View Composer 2.6, which is included with View 4.6, installed on a Windows Server 2003 operating
system, see the procedure called "Manually Migrate View Composer to the New Machine" in the VMware
View 4.6 Upgrades document. After you migrate View Composer 2.6 to a system with a Windows Server
operating system that is supported for this release, you can perform an in-place upgrade to the latest version
of View Composer.
n
Guidelines for Migrating View Composer on page 32
The steps you take to migrate the VMware Horizon View Composer service depend on whether you
intend to preserve existing linked-clone virtual machines.
n
Migrate View Composer with an Existing Database on page 32
When you migrate View Composer to another physical or virtual machine, if you intend to preserve
your current linked-clone virtual machines, the new VMware Horizon View Composer service must
continue to use the existing View Composer database.
n
Migrate View Composer Without Linked-Clone Virtual Machines on page 34
If the current VMware Horizon View Composer service does not manage any linked-clone virtual
machines, you can migrate View Composer to a new physical or virtual machine without migrating
the RSA keys to the new machine. The migrated VMware Horizon View Composer service can
connect to the original View Composer database, or you can prepare a new database for View
Composer.
Chapter 5 Upgrading View Server Components
VMware, Inc. 31