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
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.
IMPORTANT If your company uses proxy settings for Internet access, you might have to configure your
View Connection Server hosts to use the proxy. This step ensures that servers can access certificate
revocation checking sites on the Internet. You can use Microsoft Netshell commands to import the
proxy settings to View Connection Server. For more information, see "Troubleshooting View Server
Certificate Revocation Checking" in the View Administration guide.
n
If you plan to pair a security server with this View Connection Server instance, verify that Windows
Firewall with Advanced Security is set to on in the active profiles. It is recommended that you turn this
setting to on for all profiles. By default, IPsec rules govern connections between security server and
View Connection Server and require Windows Firewall with Advanced Security to be enabled.
n
If your network topology includes a firewall between a security server and a View Connection Server
instance, you must configure the firewall to support IPsec. See the View Installation document.
If you plan to perform fresh installations of View Connection Server instances on additional physical or
virtual machines, see the complete list of installation requirements in the View Installation document.
Supported Operating Systems for View Agent
The View Agent component assists with session management, single sign-on, device redirection, and other
features. You must install View Agent on all virtual machines, physical systems, and RDS hosts.
The following table lists the Windows operating system versions that are supported on single-session
virtual machines in a desktop pool. The virtual machine version must support the guest operating system.
For example, to install Windows 8.1, you must use a vSphere 5.1 or later virtual machine.
Table 2‑7. Operating Systems for Linked-Clone and Full-Clone Remote Desktops
Guest Operating System Version Edition Service Pack
Windows 10 64-bit and 32-bit Enterprise None
Windows 8.1 64-bit and 32-bit Enterprise and
Professional
Latest update
Windows 8 64-bit and 32-bit Enterprise and
Professional
None
Windows 7 64-bit and 32-bit Enterprise and
Professional
SP1
Windows Server 2012 R2 64-bit Datacenter None
Windows Server 2008 R2 64-bit Datacenter SP1
IMPORTANT View Agent 6.1 and later releases do not support Windows XP and Windows Vista desktops.
View Agent 6.0.2 is the last View release that supports these guest operating systems. Customers who have
an extended support agreement with Microsoft for Windows XP and Vista, and an extended support
agreement with VMware for these guest operating systems, can deploy the View Agent 6.0.2 version of their
Windows XP and Vista desktops with the latest version of View Connection Server.
The following table lists the Windows operating systems versions that are supported for creating desktop
pools and application pools on an RDS host.
Chapter 2 System Requirements for Upgrades
VMware, Inc. 17