VMware Horizon View - 6.1 User Manual
View Upgrades
VMware Horizon 6
Version 6.1
This document supports the version of each product listed and
supports all subsequent versions until the document is
replaced by a new edition. To check for more recent editions
of this document, see http://www.vmware.com/support/pubs.
EN-001740-00
View Upgrades
You can find the most up-to-date technical documentation on the VMware Web site at:
http://www.vmware.com/support/
The VMware Web site also provides the latest product updates.
If you have comments about this documentation, submit your feedback to:
docfeedback@vmware.com
Copyright © 2009–2015 VMware, Inc. All rights reserved. Copyright and trademark information.
VMware, Inc.
3401 Hillview Ave.
Palo Alto, CA 94304
www.vmware.com
2 VMware, Inc.
Contents
View Upgrades 5
Component Compatibility Matrix 7
1
View Upgrade Overview 11
2
System Requirements for Upgrades 13
3
View Composer Requirements 13
View Connection Server Requirements 16
View Administrator Requirements 18
Horizon Client Requirements 18
Supported Operating Systems for View Agent 19
Preparing for a View Upgrade 21
4
Preparing vCenter Server and View Composer for an Upgrade 21
Preparing View Connection Server for an Upgrade 23
Prepare to Upgrade or Reinstall a Security Server 24
Upgrading View Server Components 25
5
Upgrade View Composer 25
Upgrade View Connection Servers in a Replicated Group 34
Upgrade View Security Server 39
Upgrade vCenter Server 40
Using View Group Policy Administrative Template Files 41
VMware, Inc.
Upgrade ESXi Hosts and Their Virtual Machines 43
6
Upgrading Remote Desktops and Horizon Client 45
7
Upgrade RDS Hosts That Provide Session-Based Desktops 45
Upgrade View Agent 46
Upgrade View Composer Desktop Pools 48
Upgrade the Client Application 49
Post-Upgrade Tasks to Enable New Features in Your View Setup 51
8
Change the JMS Message Security Mode to Enhanced 51
Tasks for Upgrading Desktop Pools to Use Space Reclamation 52
Upgrade Tasks If You Use VMware Virtual SAN Datastores 53
Configure the VMware Horizon Web Portal Page for End Users 57
3
View Upgrades
Applying View Patches 61
9
Apply a Patch for View Composer 61
Apply a Patch for View Connection Server 62
Apply a Patch for View Agent 63
Apply a Patch for Horizon Client 64
Upgrading vSphere Components Separately in a View Environment 65
10
Index 67
4 VMware, Inc.
View Upgrades
View Upgrades provides instructions for upgrading from Horizon View 5.x (which includes 5.1.3, 5.2, and
5.3.3) or VMware Horizon™ 6.0.x (with View) to VMware Horizon 6 verison 6.1. You can also use this guide
when you upgrade to View maintenance and patch releases.
If you are also upgrading your version of VMware vSphere®, this guide tells you which steps of that
upgrade to do at various stages of the View upgrade.
For View patch releases, see Chapter 9, “Applying View Patches,” on page 61.
Intended Audience
This guide is intended for anyone who needs to upgrade to this latest version of this product. The
information in this guide is written for experienced Microsoft Windows or Linux system administrators
who are familiar with virtual machine technology and datacenter operations.
VMware, Inc.
5
View Upgrades
6 VMware, Inc.
Component Compatibility Matrix 1
Because large enterprises must often perform phased upgrades, components are designed to be somewhat
forward and backward compatible, at least during upgrades.
View Connection Server compatibility with View Agents is limited to interoperability during a View
Connection Server upgrade. You must upgrade View Agents as soon as possible to match the version of the
View Connection Server that manages them.
The following tables list the components and show whether they are compatible with other components
whose version is different. For information about compatibility with vSphere, see the VMware Product
Interoperability Matrix at http://www.vmware.com/resources/compatibility/sim/interop_matrix.php.
Table 1‑1. Compatibility Matrix for VMware Horizon 6 version 6.1 and Horizon 6.0 (with View) Components
Connection
Server 6.0.x
Connection
Server 6.1
Security Server
6.1 (PCoIP and
RDP)
View Composer
6.1
View Agent 6.1 Only during
Horizon Client
3.3
Only during
upgrade
No N/A No Only during upgrade Yes
Only during
upgrade
upgrade (see the
exception in the
note following
this table)
Yes Yes Yes Yes N/A
Security Server
6.0.x (PCoIP and
RDP)
Only if paired
before upgrade
Only during
upgrade
No No N/A Only during
View Composer
6.0.x View Agent 6.0.x
No Only during upgrade Yes
N/A Only during upgrade N/A
Horizon Client
(Windows) 3.2,
3.1, 3.0
upgrade
VMware, Inc.
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 View Connection Server 6.1.
7
View Upgrades
Table 1‑2. Compatibility Matrix for VMware Horizon 6 version 6.1 and Horizon View 5.3.x Components
Security Server
Connection
Server 5.3.x
Connection
Server 6.1
Security Server
6.1 (PCoIP and
RDP)
View Composer
6.1
View Agent 6.1 Only during
Horizon Client
3.3
Only during
upgrade
No N/A No Only during upgrade Yes
Only during
upgrade
upgrade
Yes Yes Yes Yes N/A
5.3.x (PCoIP and
RDP) View Composer 5.3 View Agent 5.3.x
Only if paired
before upgrade
Only during
upgrade
No No N/A Only during
No Only during upgrade Yes
N/A Only during upgrade N/A
Table 1‑3. Compatibility Matrix for VMware Horizon 6 version 6.1 and Horizon View 5.2.x Components
Security Server
Connection
Server 5.2.x
Connection
Server 6.1
Security Server
6.1 (PCoIP and
RDP)
View Composer
6.1
View Agent 6.1 Only during
Horizon Client
3.3
Only during
upgrade
No N/A No Only during upgrade Yes
Only during
upgrade
upgrade
Yes Yes Yes Yes N/A
5.2.x (PCoIP and
RDP) View Composer 5.2 View Agent 5.2.x
Only if paired
before upgrade
Only during
upgrade
No No N/A Only during
No Only during upgrade Yes
N/A Only during upgrade N/A
View Client
(Windows) 5.x
upgrade
View Client
(Windows) 5.x
upgrade
Table 1‑4. Compatibility Matrix for VMware Horizon 6 version 6.1 and Horizon View 5.1.x Components
Security Server
Connection
Server 5.1.3
Connection
Server 6.1
Security Server
6.1 (PCoIP and
RDP)
View Composer
6.1
8 VMware, Inc.
Only during
upgrade
No N/A No Only during upgrade Yes
Only during
upgrade
5.1.3 (PCoIP and
RDP) View Composer 3.0 View Agent 5.1.3
Only if paired
before upgrade
Only during
upgrade
No Only during upgrade Yes
N/A Only during upgrade N/A
View Client
(Windows) 5.1.x
Chapter 1 Component Compatibility Matrix
Table 1‑4. Compatibility Matrix for VMware Horizon 6 version 6.1 and Horizon View 5.1.x Components (Continued)
Security Server
Connection
Server 5.1.3
View Agent 6.1 Only during
upgrade
Horizon Client
3.3
Yes Yes Yes Yes N/A
5.1.3 (PCoIP and
RDP) View Composer 3.0 View Agent 5.1.3
No No N/A Only during
View Client
(Windows) 5.1.x
upgrade
CAUTION During an upgrade, View Composer provisioning and maintenance operations are not supported.
Operations such as provisioning and recomposing linked-clone desktops are not supported during the
transitional period when any View servers are still running the earlier version. You can successfully perform
these operations only when all instances of View Connection Server and View Composer have been
upgraded to the latest version.
For details about which versions of View are compatible with which versions of vCenter Server and ESXi,
see the VMware Product Interoperability Matrix at
http://www.vmware.com/resources/compatibility/sim/interop_matrix.php.
VMware, Inc. 9
View Upgrades
10 VMware, Inc.
View Upgrade Overview 2
Upgrading an enterprise View deployment involves several high-level tasks. Upgrading is a multistage
process in which procedures must be performed in a particular order. You upgrade View Composer before
upgrading View Connection Server and the other View servers.
During an upgrade, View does not support View Composer provisioning and maintenance operations.
Operations such as provisioning and recomposing linked-clone desktops are not supported during the
transitional period when any View servers are still running the earlier version. You can successfully perform
these operations only when all instances of View Connection Server and View Composer have been
upgraded.
You must complete the upgrade process in a specific order. Order is also important within each upgrade
stage.
NOTE This overview relates to upgrades for major, minor, and maintenance releases. For information about
patches, see Chapter 9, “Applying View Patches,” on page 61.
How many of the following tasks you need to complete depends on which components of View you use in
your deployment.
1 On the physical or virtual machines that host View Composer and VMware® vCenter Server™, make
backups and temporarily halt certain scheduled tasks. See “Preparing vCenter Server and View
Composer for an Upgrade,” on page 21.
VMware, Inc.
For details about which versions of View are compatible with which versions of vCenter Server and
ESXi, see the VMware Product Interoperability Matrix at
http://www.vmware.com/resources/compatibility/sim/interop_matrix.php.
2 On the physical or virtual machines that host View Connection Server instances, make backups and
record various configuration and system settings. See “Preparing View Connection Server for an
Upgrade,” on page 23.
3 If you use security servers, perform the tasks in “Prepare to Upgrade or Reinstall a Security Server,” on
page 24.
4 Upgrade View Composer on the existing host or migrate to a new machine. See “Upgrade View
Composer,” on page 25.
5 Upgrade View Connection Server on the existing host or migrate to a new machine. See “Upgrade View
Connection Servers in a Replicated Group,” on page 34.
IMPORTANT After you upgrade a View Connection Server instance to the latest version, you cannot
downgrade that instance to an earlier version. After you upgrade all View Connection Server instances
in a replicated group, you cannot add another instance that runs an earlier version.
6 If you use security servers, upgrade them. See “Upgrade View Security Server,” on page 39.
11
View Upgrades
7 Upgrade the group policies used in Active Directory. See “Using View Group Policy Administrative
8 If you are also upgrading VMware vSphere components, upgrade vCenter Server. See “Upgrade
9 If you are also upgrading vSphere, upgrade the VMware® ESXi™ hosts and virtual machines. See
10 If you currently use Windows Terminal Services servers as desktop sources, upgrade to Windows
11 Upgrade the Horizon™ View Agent™ software that runs on the physical or virtual machines that are
12 Use the newly upgraded virtual machine desktop sources to create upgraded pools of desktops. See
13 Upgrade the Horizon Client software that runs on end users' client devices. See “Upgrade the Client
Because certain commands can simultaneously upgrade more than one stage, VMware recommends that
you thoroughly understand the irreversible changes at each stage before you upgrade your production
environments.
Template Files,” on page 41.
vCenter Server,” on page 40.
Chapter 6, “Upgrade ESXi Hosts and Their Virtual Machines,” on page 43.
Server 2008 R2 or later and verify that the RDS Host role is installed. See “Upgrade RDS Hosts That
Provide Session-Based Desktops,” on page 45
used as desktop sources, as full-clone desktops in a pool, and as individual desktops in a manual pool.
See “Upgrade View Agent,” on page 46.
“Upgrade View Composer Desktop Pools,” on page 48.
Application,” on page 49.
IMPORTANT The VMware View® Client with Local Mode feature, for using offline desktops, has been
removed, and therefore this overview does not include steps for upgrading View Transfer Server instances
and View Client with Local Mode. In place of the Local Mode feature, VMware recommends using
VMware® Mirage™, which is included with VMware Horizon 6.0 and later releases. For more information,
see the View Release Notes, available at https://www.vmware.com/support/pubs/view_pubs.html.
12 VMware, Inc.
System Requirements for Upgrades 3
Hosts and virtual machines in a View deployment must meet specific hardware and operating system
requirements.
This chapter includes the following topics:
“View Composer Requirements,” on page 13
n
“View Connection Server Requirements,” on page 16
n
“View Administrator Requirements,” on page 18
n
“Horizon Client Requirements,” on page 18
n
“Supported Operating Systems for View Agent,” on page 19
n
View Composer Requirements
With View Composer, you can deploy multiple linked-clone desktops from a single centralized base image.
View Composer has specific installation and storage requirements.
Supported Operating Systems for View Composer
VMware, Inc.
View Composer supports 64-bit operating systems with specific requirements and limitations. You can
install View Composer on the same physical or virtual machine as vCenter Server or on a separate server.
Table 3‑1. Operating System Support for View Composer
Operating System Version Edition
Windows Server 2008 R2 SP1 64-bit Standard
Enterprise
Datacenter
Windows Server 2012 R2 64-bit Standard
Datacenter
NOTE Windows Server 2008 R2 with no service pack is no longer supported.
If you plan to install View Composer on a different physical or virtual machine than vCenter Server, see
“Hardware Requirements for Standalone View Composer,” on page 14.
13
View Upgrades
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-toone 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
Networking One or more 10/100Mbps
network interface cards (NICs)
Memory 4GB RAM or higher 8GB RAM or higher for deployments of 50 or more
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.
2GHz or faster and 4 CPUs
1Gbps NICs
remote desktops
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.
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 3‑3. Supported Database Servers for View Composer
Database Service Packs/Releases Editions
Microsoft SQL Server 2014
(32- and 64-bit)
Microsoft SQL Server 2012
(32- and 64-bit)
No SP Standard
Enterprise
No SP, SP1, SP2 Express
Standard
Enterprise
14 VMware, Inc.
Table 3‑3. Supported Database Servers for View Composer (Continued)
Database Service Packs/Releases Editions
Microsoft SQL Server 2008 R2
(32- and 64-bit)
Microsoft SQL Server 2008
(32- and 64-bit)
Oracle 12c Release 1 (any release up to 12.1.0.2) Standard One
Oracle 11g
(32- and 64-bit)
SP1, SP2, SP3 Express
SP4 Express
Release 2 (11.2.0.4) Standard One
NOTE Oracle 10g Release 2 is no longer supported.
Upgrade Requirements for View Composer
Chapter 3 System Requirements for Upgrades
Standard
Enterprise
Datacenter
Standard
Enterprise
Standard
Enterprise
Standard
Enterprise
The View Composer upgrade process has specific requirements and limitations.
To run the View Composer installer, you must be a domain user with Administrator privileges on the
system.
Security-Related Requirements
View Composer requires an SSL certificate that is signed by a CA (certificate authority). If you intend to
n
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.
Certificates for vCenter Server, View Composer, and View servers must include certificate revocation
n
lists (CRLs). For more information, see "Configuring Certificate Revocation Checking on Server
Certificates" in the View Installation guide.
Verify that no applications that run on the View Composer computer use Windows SSL libraries that
n
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.
To enhance the security of View Composer, disable the weak cryptographic cipher suites on the
n
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.
VMware, Inc. 15
View Upgrades
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 3‑4. View Connection Server Hardware Requirements
Hardware Component Required Recommended
Processor Pentium IV 2.0GHz processor
or higher
Network Adapter 100Mpbs NIC 1Gbps NICs
Memory
Windows Server 2008 R2 64-bit
Memory
Windows Server 2012 R2 64-bit
4GB RAM or higher At least 10GB RAM for deployments of 50 or more
4GB RAM or higher At least 10GB RAM for deployments of 50 or more
4 CPUs
remote desktops
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.
Supported Operating Systems for View Connection Server
You must install View Connection Server on a supported Windows Server operating system.
The following operating systems support all View Connection Server installation types, including standard,
replica, and security server installations.
Table 3‑5. Operating System Support for View Connection Server
Operating System Version Edition
Windows Server 2008 R2 SP1 64-bit Standard
Enterprise
Datacenter
Windows Server 2012 R2 64-bit Standard
Datacenter
NOTE Windows Server 2008 R2 with no service pack is no longer supported.
Upgrade Requirements for View Connection Server
The View Connection Server upgrade process has specific requirements and limitations.
View Connection Server requires a valid license key for this latest release.
n
16 VMware, Inc.
Chapter 3 System Requirements for Upgrades
The domain user account that you use to install the new version of View Connection Server must have
n
administrative privileges on the View Connection Server host. The View Connection Server
administrator must have administrative credentials for vCenter Server.
When you run the installer, you authorize a View Administrators account. You can specify the local
n
Administrators group or a domain user or group account. View assigns full View Administration
rights, including the right to install replicated View Connection Server instances, to this account only. If
you specify a domain user or group, you must create the account in Active Directory before you run the
installer.
When you back up View Connection Server, the View LDAP configuration is exported as encrypted
n
LDIF data. To restore the encrypted backup View configuration, you must provide the data recovery
password. The password must contain between 1 and 128 characters.
Security-Related Requirements
View Connection Server requires an SSL certificate that is signed by a CA (certificate authority) and that
n
your clients can validate. Although a default self-signed certificate is generated in the absence of a CAsigned certificate when you install View Connection Server, you must replace the default self-signed
certificate as soon as possible. Self-signed certificates are shown as invalid in View Administrator.
Also, updated clients expect information about the server's certificate to be communicated as part of the
SSL handshake between client and server. Often updated clients do not trust self-signed certificates.
For complete information about security certificate requirements, see "Configuring SSL Certificates for
View Servers" in the View Installation guide. Also see the Scenarios for Setting Up SSL Connections to View
document, which describes setting up intermediate servers that perform tasks such as load balancing
and off-loading SSL connections.
NOTE If your original servers already have SSL certificates signed by a CA, during the upgrade, View
imports your existing CA-signed certificate into the Windows Server certificate store.
Certificates for vCenter Server, View Composer, and View servers must include certificate revocation
n
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.
If you plan to pair a security server with this View Connection Server instance, verify that Windows
n
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.
If your network topology includes a firewall between a security server and a View Connection Server
n
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.
Virtualization Software Requirements for View Connection Server
View Connection Server requires certain versions of VMware virtualization software.
If you are using vSphere, you must use a supported version of vSphere ESX/ESXi hosts and vCenter Server.
VMware, Inc. 17
View Upgrades
For details about which versions of View are compatible with which versions of vCenter Server and ESXi,
see the VMware Product Interoperability Matrix at
http://www.vmware.com/resources/compatibility/sim/interop_matrix.php.
View Administrator Requirements
Administrators use View Administrator to configure View Connection Server, deploy and manage remote
desktops and applications, control user authentication, initiate and examine system events, and carry out
analytical activities. Client systems that run View Administrator must meet certain requirements.
View Administrator is a Web-based application that is installed when you install View Connection Server.
You can access and use View Administrator with the following Web browsers:
Internet Explorer 9
n
Internet Explorer 10
n
Internet Explorer 11
n
Firefox 6 and later releases
n
Safari 6 and later releases
n
To use View Administrator with your Web browser, you must install Adobe Flash Player 10.1 or later. Your
client system must have access to the Internet to allow Adobe Flash Player to be installed.
The computer on which you launch View Administrator must trust the root and intermediate certificates of
the server that hosts View Connection Server. The supported browsers already contain certificates for all of
the well-known certificate authorities (CAs). If your certificates come from a CA that is not well known, you
must follow the instructions in the View Installation document about importing root and intermediate
certificates.
To display text properly, View Administrator requires Microsoft-specific fonts. If your Web browser runs on
a non-Windows operating system such as Linux, UNIX, or Mac OS X, make sure that Microsoft-specific
fonts are installed on your computer.
Currently, the Microsoft Web site does not distribute Microsoft fonts, but you can download them from
independent Web sites.
Horizon Client Requirements
Horizon Client runs on many types of devices: Windows, Mac, and Linux desktops and laptops; Linux thin
and zero clients; tablets; and phones. All of these devices have specific requirements.
For information about operating system requirements, hardware requirements, and browser requirements
of a specific type client device, go to
https://www.vmware.com/support/viewclients/doc/viewclients_pubs.html and see the document for that
type of client device.
IMPORTANT The features that are available for thin client devices and zero clients are determined by the
vendor and model and the configuration that an enterprise chooses to use. For information about the
vendors and models for thin and zero client devices, see the VMware Compatibility Guide, available on the
VMware Web site.
18 VMware, Inc.
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 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 3‑6. Operating Systems for Linked-Clone and Full-Clone Remote Desktops
Guest Operating System Version Edition Service Pack
Windows 8.1 64-bit and 32-bit Enterprise and
Professional
Windows 8 64-bit and 32-bit Enterprise and
Professional
Windows 7 64-bit and 32-bit Enterprise and
Professional
Windows Server 2012 R2 64-bit Datacenter None
Windows Server 2008 R2 64-bit Datacenter SP1
Chapter 3 System Requirements for Upgrades
None and Update
None
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 View Connection Server 6.1.
The following table lists the Windows operating systems versions that are supported for creating desktop
pools and application pools on an RDS host.
Table 3‑7. Operating Systems for RDS Hosts, Providing Remote Desktops or Applications
Guest Operating System Edition Service Pack
Windows Server 2008 R2 Standard, Enterprise, and
Datacenter
Windows Server 2012 Standard and Datacenter None
Windows Server 2012 R2 Standard and Datacenter None or Update 1
SP1
VMware, Inc. 19
View Upgrades
20 VMware, Inc.
Preparing for a View Upgrade 4
Before you start the upgrade process, you must review system requirements for the new version, back up
databases, take snapshots of virtual machines that host server components, and document configuration
settings.
This chapter includes the following topics:
“Preparing vCenter Server and View Composer for an Upgrade,” on page 21
n
“Preparing View Connection Server for an Upgrade,” on page 23
n
“Prepare to Upgrade or Reinstall a Security Server,” on page 24
n
Preparing vCenter Server and View Composer for an Upgrade
Because vCenter Server and View Composer are often installed on the same virtual or physical machine,
some preparation tasks apply to both.
Preparing for Upgrades That Include vSphere
If you are upgrading vCenter Server in addition to upgrading to the latest version of View, you must
consult the VMware vSphere Upgrade Guide and perform the following tasks in the following order:
VMware, Inc.
1 Verify that the virtual or physical machine meets the system requirements for the version of
vCenter Server that you want to upgrade to.
2 Verify that the virtual or physical machine on which the current View Composer is installed meets the
security requirements for the new version.
See “Upgrade Requirements for View Composer,” on page 15.
3 If vCenter Server is installed in a virtual machine, take a snapshot of the virtual machine.
For instructions on taking snapshots, see the vSphere Client™ online help.
4 If the computer name is longer than 15 characters, shorten the name to 15 or fewer characters.
5 Back up the vCenter Server database and the View Composer database.
For instructions on performing a database backup, see the documentation from your database vendor.
6 Verify that the database server is compatible with the version of vCenter Server you plan to use.
For example, if the database server is Oracle 9i, you must upgrade.
7 Verify that the database is compatible with the new version of View Composer.
21
Loading...