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
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 2‑3. 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 have an IP address that does
not change. In an IPv4 environment, configure a static IP address. In an IPv6 environment, machines
automatically get IP addresses that do not change.
Database Requirements for View Composer and the Events Database
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. You can optionally set up an Events database to record
information from View Connection Server about View events.
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 2-4. 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.
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 as of the publication date of this
document. For the most up-to-date information about supported databases, see the VMware Product
Interoperability Matrixes at http://www.vmware.com/resources/compatibility/sim/interop_matrix.php. For
Solution/Database Interoperability, after you select the product and version, for the Add Database step, to
see a list of all supported databases, select Any and click Add.
Table 2‑4. Supported Database Servers for View Composer and for the Events Database
Database Service Packs/Releases Editions
Microsoft SQL Server 2014
(32- and 64-bit)
No SP, SP1 Standard
Enterprise
Microsoft SQL Server 2012
(32- and 64-bit)
SP2 Express
Standard
Enterprise
Chapter 2 System Requirements for Upgrades
VMware, Inc. 13