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
Security-Related Requirements
n
View Composer requires an SSL certificate that is signed by a CA (certificate authority). If you intend to
replace an existing certificate or the default, self-signed certificate with a new certificate after you install
View Composer, you must import the new certificate and run the SviConfig ReplaceCertificate utility
to bind your new certificate to the port used by View Composer.
If you install vCenter Server and View Composer on the same Windows Server computer, they can use
the same SSL certificate, but you must configure the certificate separately for each component.
For complete information about security certificate requirements, see "Configuring SSL Certificates for
View Servers" in the View Installation guide.
n
Certificates for vCenter Server, View Composer, and View servers must include certificate revocation
lists (CRLs). For more information, see "Configuring Certificate Revocation Checking on Server
Certificates" in the View Installation guide.
n
Verify that no applications that run on the View Composer computer use Windows SSL libraries that
require SSL version 2 (SSLv2) provided through the Microsoft Secure Channel (Schannel) security
package. The View Composer installer disables SSLv2 on the Microsoft Schannel. Applications such as
Tomcat, which uses Java SSL, or Apache, which uses OpenSSL, are not affected by this constraint.
n
To enhance the security of View Composer, disable the weak cryptographic cipher suites on the
Windows Server computer on which the View Composer service is installed. See "Disable Weak
Cryptographic Cipher Suites on the View Composer Server" in the View Installation guide.
View Connection Server Requirements
View Connection Server acts as a broker for client connections by authenticating and then directing
incoming user requests to the appropriate remote desktops and applications. View Connection Server has
specific hardware, operating system, installation, and supporting software requirements.
Hardware Requirements for View Connection Server
You must install all View Connection Server installation types, including standard, replica, and security
server installations, on a dedicated physical or virtual machine that meets specific hardware requirements.
Table 2‑5. View Connection Server Hardware Requirements
Hardware Component Required Recommended
Processor Pentium IV 2.0GHz processor
or higher
4 CPUs
Network Adapter 100Mpbs NIC 1Gbps NICs
Memory
Windows Server 2008 R2 64-bit
4GB RAM or higher At least 10GB RAM for deployments of 50 or more
remote desktops
Memory
Windows Server 2012 R2 64-bit
4GB RAM or higher At least 10GB RAM for deployments of 50 or more
remote desktops
These requirements also apply to replica and security server View Connection Server instances that you
install for high availability or external access.
IMPORTANT The physical or virtual machine that hosts View Connection Server 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.
Chapter 2 System Requirements for Upgrades
VMware, Inc. 15