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
Hardware Requirements for Standalone View Composer
If you install View Composer on a different physical or virtual machine from the one used for
vCenter Server, you must use a dedicated machine that meets specific hardware requirements.
A standalone View Composer installation works with vCenter Server installed on a separate Windows
Server machine or with the Linux-based vCenter Server appliance. VMware recommends having a one-to-
one mapping between each View Composer service and vCenter Server instance.
Table 3‑2. View Composer Hardware Requirements
Hardware Component Required Recommended
Processor 1.4 GHz or faster Intel 64 or
AMD 64 processor with 2 CPUs
2GHz or faster and 4 CPUs
Networking One or more 10/100Mbps
network interface cards (NICs)
1Gbps NICs
Memory 4GB RAM or higher 8GB RAM or higher for deployments of 50 or more
remote desktops
Disk space 40GB 60GB
IMPORTANT The physical or virtual machine that hosts View Composer must use a static IP address.
Database Requirements for View Composer
View Composer requires an SQL database to store data. The View Composer database must reside on, or be
available to, the View Composer server host.
If a database server instance already exists for vCenter Server, View Composer can use that existing instance
if it is a version listed in Table 3-3. For example, View Composer can use the Microsoft SQL Server instance
provided with vCenter Server. If a database server instance does not already exist, you must install one.
View Composer supports a subset of the database servers that vCenter Server supports. If you are already
using vCenter Server with a database server that is not supported by View Composer, continue to use that
database server for vCenter Server and install a separate database server to use for View Composer and
View database events.
IMPORTANT If you create the View Composer database on the same SQL Server instance as vCenter Server,
do not overwrite the vCenter Server database.
The following table lists the supported database servers and versions. For a complete list of database
versions supported with vCenter Server, see the VMware Product Interoperability Matrixes at
http://www.vmware.com/resources/compatibility/sim/interop_matrix.php.
The versions of vCenter Server listed in the table column headings are general. For specific supported
update versions of each vCenter Server release, see the VMware Product Interoperability Matrixes at
http://www.vmware.com/resources/compatibility/sim/interop_matrix.php.
Table 3‑3. Supported Database Servers for View Composer
Database
vCenter
Server
5.5
vCenter
Server
5.1
vCenter
Server
5.0
vCenter
Server 4.1
Microsoft SQL Server 2012 Express
(32- and 64-bit)
Yes Yes Yes No
Microsoft SQL Server 2012 (SP1) Standard and Enterprise
(32- and 64-bit)
Yes Yes Yes No
View Upgrades
14 VMware, Inc.