VMware Horizon View - 6.1, Horizon 6.1 Installation Manual

View Installation

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-001722-00

View Installation

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:

[e-mail]

Copyright © 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 Installation 5

System Requirements for Server Components 7

1

View Connection Server Requirements 7

View Administrator Requirements 9

View Composer Requirements 9

System Requirements for Guest Operating Systems 13

2

Supported Operating Systems for View Agent 13

Supported Operating Systems for Standalone View Persona Management 14

Remote Display Protocol and Software Support 14

Installing View in an IPv6 Environment 19

3

Setting Up View in an IPv6 Environment 19

Supported vSphere , Database, and Active Directory Versions in an IPv6 Environment 20

Supported Operating Systems for View Servers in an IPv6 Environment 20

Supported Windows Operating Systems for Desktops and RDS Hosts in an IPv6 Environment 21

Supported Clients in an IPv6 Environment 21

Supported Remoting Protocols in an IPv6 Environment 21

Supported Authentication Types in an IPv6 Environment 22

Other Supported Features in an IPv6 Environment 22

Preparing Active Directory 25

4

Configuring Domains and Trust Relationships 25

Creating an OU for Remote Desktops 26

Creating OUs and Groups for Kiosk Mode Client Accounts 26

Creating Groups for Users 27

Creating a User Account for vCenter Server 27

Creating a User Account for a Standalone View Composer Server 27

Create a User Account for View Composer AD Operations 27

Configure the Restricted Groups Policy 28

Using View Group Policy Administrative Template Files 29

Prepare Active Directory for Smart Card Authentication 29

VMware, Inc.

Installing View Composer 33

5

Prepare a View Composer Database 33

Configuring an SSL Certificate for View Composer 40

Install the View Composer Service 41

Configuring Your Infrastructure for View Composer 43

3

View Installation

Installing View Connection Server 45

6

Installing the View Connection Server Software 45

Installation Prerequisites for View Connection Server 45

Install View Connection Server with a New Configuration 46

Install a Replicated Instance of View Connection Server 52

Configure a Security Server Pairing Password 58

Install a Security Server 58

Firewall Rules for View Connection Server 65

Reinstall View Connection Server with a Backup Configuration 67

Microsoft Windows Installer Command-Line Options 68

Uninstalling View Components Silently by Using MSI Command-Line Options 70

Configuring SSL Certificates for View Servers 71

7

Understanding SSL Certificates for View Servers 71

Overview of Tasks for Setting Up SSL Certificates 73

Obtaining a Signed SSL Certificate from a CA 74

Configure View Connection Server, Security Server, or View Composer to Use a New SSL

Certificate 75

Configure Client Endpoints to Trust Root and Intermediate Certificates 80

Configuring Certificate Revocation Checking on Server Certificates 82

Configure the PCoIP Secure Gateway to Use a New SSL Certificate 83

Setting View Administrator to Trust a vCenter Server or View Composer Certificate 87

Benefits of Using SSL Certificates Signed by a CA 87

Troubleshooting Certificate Issues on View Connection Server and Security Server 88

Configuring View for the First Time 89

8

Configuring User Accounts for vCenter Server and View Composer 89

Configuring View Connection Server for the First Time 92

Configuring Horizon Client Connections 103

Replacing Default Ports for View Services 109

Sizing Windows Server Settings to Support Your Deployment 113

Configuring Event Reporting 115

9

Add a Database and Database User for View Events 115

Prepare an SQL Server Database for Event Reporting 116

Configure the Event Database 117

Configure Event Logging for Syslog Servers 118

Index 121

4 VMware, Inc.

View Installation

View Installation explains how to install the VMware Horizon™ 6 server and client components.

Intended Audience

This information is intended for anyone who wants to install VMware Horizon 6. The information is written
for experienced Windows or Linux system administrators who are familiar with virtual machine technology
and datacenter operations.

VMware, Inc. 5

View Installation

6 VMware, Inc.

System Requirements for Server

Components 1

Hosts that run View server components must meet specific hardware and software requirements.

This chapter includes the following topics:

“View Connection Server Requirements,” on page 7

n

“View Administrator Requirements,” on page 9

n

“View Composer Requirements,” on page 9

n

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 on page 8

n

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.

Supported Operating Systems for View Connection Server on page 8

n

You must install View Connection Server on a supported Windows Server operating system.

Virtualization Software Requirements for View Connection Server on page 8

n

View Connection Server requires certain versions of VMware virtualization software.

Network Requirements for Replicated View Connection Server Instances on page 9

n

When installing replicated View Connection Server instances, you must usually configure the
instances in the same physical location and connect them over a high-performance LAN. Otherwise,
latency issues could cause the View LDAP configurations on View Connection Server instances to
become inconsistent. A user could be denied access when connecting to a View Connection Server
instance with an out-of-date configuration.

VMware, Inc.

7

View Installation

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 1‑1. 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

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.

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

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 1‑2. 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.

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.

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.

8 VMware, Inc.

Chapter 1 System Requirements for Server Components

Network Requirements for Replicated View Connection Server Instances

When installing replicated View Connection Server instances, you must usually configure the instances in
the same physical location and connect them over a high-performance LAN. Otherwise, latency issues could
cause the View LDAP configurations on View Connection Server instances to become inconsistent. A user
could be denied access when connecting to a View Connection Server instance with an out-of-date
configuration.

IMPORTANT To use a group of replicated View Connection Server instances across a WAN, MAN
(metropolitan area network), or other non-LAN, in scenarios where a View deployment needs to span
datacenters, you must use the Cloud Pod Architecture feature. You can link together four View pods to
provide a single large desktop brokering and management environment for two geographically distant sites
and manage up to 20,000 remote desktops. For more information, see Administering View Cloud Pod
Architecture.

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.

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 on page 10

n

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.

VMware, Inc. 9

View Installation

Hardware Requirements for Standalone View Composer on page 10

n

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.

Database Requirements for View Composer on page 11

n

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.

Supported Operating Systems for View Composer

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 1‑3. Operating System Support for View Composer

Operating System Version Edition

Windows Server 2008 R2 SP1 64-bit Standard

Windows Server 2012 R2 64-bit Standard

Enterprise

Datacenter

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 10.

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 1‑4. 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

2GHz or faster and 4 CPUs

1Gbps NICs

remote desktops

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.

10 VMware, Inc.

Chapter 1 System Requirements for Server Components

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 1-5. 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 1‑5. 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)

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)

No SP Standard

Enterprise

No SP, SP1, SP2 Express

Standard

Enterprise

SP1, SP2, SP3 Express

Standard

Enterprise

Datacenter

SP4 Express

Standard

Enterprise

Standard

Enterprise

Release 2 (11.2.0.4) Standard One

Standard

Enterprise

NOTE Oracle 10g Release 2 is no longer supported.

VMware, Inc. 11

View Installation

12 VMware, Inc.

System Requirements for Guest

Operating Systems 2

Systems running View Agent or Standalone View Persona Management must meet certain hardware and
software requirements.

This chapter includes the following topics:

“Supported Operating Systems for View Agent,” on page 13

n

“Supported Operating Systems for Standalone View Persona Management,” on page 14

n

“Remote Display Protocol and Software Support,” on page 14

n

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 2‑1. 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

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.

To use the View Persona Management setup option with View Agent, you must install View Agent on
Windows 8, Windows 7, Windows Server 2012 R2, or Windows Server 2008 R2 virtual machines. This
option does not operate on physical computers or RDS hosts.

None and Update

None

SP1

VMware, Inc.

13

View Installation

You can install the standalone version of View Persona Management on physical computers. See

“Supported Operating Systems for Standalone View Persona Management,” on page 14.

The following table lists the Windows operating systems versions that are supported for creating desktop
pools and application pools on an RDS host.

Table 2‑2. 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

Supported Operating Systems for Standalone View Persona Management

The standalone View Persona Management software provides persona management for standalone physical
computers and virtual machines that do not have View Agent installed. When users log in, their profiles are
downloaded dynamically from a remote profile repository to their standalone systems.

NOTE To configure View Persona Management for View desktops, install View Agent with the View
Persona Management setup option. The standalone View Persona Management software is intended for

non-View systems only.

Table 2-3 lists the operating systems supported for the standalone View Persona Management software.

Table 2‑3. Operating System Support for Standalone View Persona Management

Guest Operating System Version Edition Service Pack

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

The standalone View Persona Management software is not supported on Microsoft Remote Desktop
Services.

Remote Display Protocol and Software Support

Remote display protocols and software provide access to remote desktops and applications. The remote
display protocol used depends on the type of client device, whether you are connecting to a remote desktop
or a remote application, and how the administrator configures the desktop or application pool.

PCoIP on page 15

n

PCoIP (PC over IP) provides an optimized desktop experience for the delivery of a remote application
or an entire remote desktop environment, including applications, images, audio, and video content for
a wide range of users on the LAN or across the WAN. PCoIP can compensate for an increase in latency
or a reduction in bandwidth, to ensure that end users can remain productive regardless of network
conditions.

Microsoft RDP on page 16

n

Remote Desktop Protocol is the same multichannel protocol many people already use to access their
work computer from their home computer. Microsoft Remote Desktop Connection (RDC) uses RDP to
transmit data.

14 VMware, Inc.

Chapter 2 System Requirements for Guest Operating Systems

PCoIP

PCoIP (PC over IP) provides an optimized desktop experience for the delivery of a remote application or an
entire remote desktop environment, including applications, images, audio, and video content for a wide
range of users on the LAN or across the WAN. PCoIP can compensate for an increase in latency or a
reduction in bandwidth, to ensure that end users can remain productive regardless of network conditions.

PCoIP is supported as the display protocol for remote applications and for remote desktops that use virtual
machines, physical machines that contain Teradici host cards, or shared session desktops on an RDS host.

PCoIP Features

Key features of PCoIP include the following:

Users outside the corporate firewall can use this protocol with your company's virtual private network

n

(VPN), or users can make secure, encrypted connections to a security server in the corporate DMZ.

Advanced Encryption Standard (AES) 128-bit encryption is supported and is turned on by default. You

n

can, however, change the encryption key cipher to AES-192 or AES-256.

Connections to Windows desktops with the View Agent operating system versions listed in “Supported

n

Operating Systems for View Agent,” on page 13 are supported.

Connections from all types of client devices.

n

Optimization controls for reducing bandwidth usage on the LAN and WAN.

n

32-bit color is supported for virtual displays.

n

ClearType fonts are supported.

n

Audio redirection with dynamic audio quality adjustment for LAN and WAN.

n

Real-Time Audio-Video for using webcams and microphones on some client types.

n

Copy and paste of text and, on some clients, images between the client operating system and a remote

n

application or desktop. For other client types, only copy and paste of plain text is supported. You
cannot copy and paste system objects such as folders and files between systems.

Multiple monitors are supported for some client types. For example, on Windows-based clients, you

n

can use up to four monitors and adjust the resolution for each monitor separately, with a resolution of
up to 2560 x 1600 per display. Pivot display and autofit are also supported.

When the 3D feature is enabled, up to 2 monitors are supported with a resolution of up to 1920 x 1200.

USB redirection is supported for some client types.

n

MMR redirection is supported for some Windows client operating systems and some remote desktop

n

operating systems (with View Agent-installed).

For information about which desktop operating systems support specific PCoIP features, see "Feature
Support Matrix for View Agent" in the View Architecture Planning document.

For information about which client devices support specific PCoIP features, go to

https://www.vmware.com/support/viewclients/doc/viewclients_pubs.html.

Recommended Guest Operating System Settings

1GB of RAM or more and a dual CPU is recommended for playing in high-definition, full screen mode, or
720p or higher formatted video. To use Virtual Dedicated Graphics Acceleration for graphics-intensive
applications such as CAD applications, 4GB of RAM is required.

VMware, Inc. 15

View Installation

Video Quality Requirements

480p-formatted video

720p-formatted video

1080p-formatted video

3D rendering

You can play video at 480p or lower at native resolutions when the remote
desktop has a single virtual CPU. If you want to play the video in high­definition Flash or in full screen mode, the desktop requires a dual virtual
CPU. Even with a dual virtual CPU desktop, as low as 360p-formatted video
played in full screen mode can lag behind audio, particularly on Windows
clients.

You can play video at 720p at native resolutions if the remote desktop has a
dual virtual CPU. Performance might be affected if you play videos at 720p
in high definition or in full screen mode.

If the remote desktop has a dual virtual CPU, you can play 1080p formatted
video, although the media player might need to be adjusted to a smaller
window size.

You can configure remote desktops to use software- or hardware-accelerated
graphics. The software-accelerated graphics feature enables you to run
DirectX 9 and OpenGL 2.1 applications without requiring a physical graphics
processing unit (GPU). The hardware-accelerated graphics features enable
virtual machines to either share the physical GPUs (graphical processing
unit) on a vSphere host or dedicate a physical GPU to a single virtual
machine desktop.

For 3D applications, up to 2 monitors are supported, and the maximum
screen resolution is 1920 x 1200. The guest operating system on the remote
desktops must be Windows 7 or later.

Hardware Requirements for Client Systems

For information about processor and memory requirements, see the "Using VMware Horizon Client"
document for the specific type of desktop or mobile client device. Go to

https://www.vmware.com/support/viewclients/doc/viewclients_pubs.html.

Microsoft RDP

Remote Desktop Protocol is the same multichannel protocol many people already use to access their work
computer from their home computer. Microsoft Remote Desktop Connection (RDC) uses RDP to transmit
data.

Microsoft RDP is a supported display protocol for remote desktops that use virtual machines, physical
machines, or shared session desktops on an RDS host. (Only the PCoIP display protocol is supported for
remote applications.) Microsoft RDP provides the following features:

RDP 7 has true multiple monitor support, for up to 16 monitors.

n

You can copy and paste text and system objects such as folders and files between the local system and

n

the remote desktop.

32-bit color is supported for virtual displays.

n

RDP supports 128-bit encryption.

n

Users outside the corporate firewall can use this protocol with your company's virtual private network

n

(VPN), or users can make secure, encrypted connections to a View security server in the corporate
DMZ.

16 VMware, Inc.

Chapter 2 System Requirements for Guest Operating Systems

Hardware Requirements for Client Systems

For information about processor and memory requirements, see the "Using VMware Horizon Client"
document for the specific type of client system. Go to

https://www.vmware.com/support/viewclients/doc/viewclients_pubs.html.

NOTE Mobile client devices use only the PCoIP display protocol.

VMware, Inc. 17

View Installation

18 VMware, Inc.

Installing View in an IPv6

Environment 3

View supports IPv6 as an alternative to IPv4. The environment must be either IPv6 only or IPv4 only. View
does not support a mixed IPv6 and IPv4 environment.

Not all View features that are supported in an IPv4 environment are supported in an IPv6 environment.
View does not support upgrading from an IPv4 environment to an IPv6 environment. Also, View does not
support migration between IPv4 and IPv6 environments.

IMPORTANT To run View in an IPv6 environment, you must specify IPv6 when you install all View
components.

This chapter includes the following topics:

“Setting Up View in an IPv6 Environment,” on page 19

n

“Supported vSphere, Database, and Active Directory Versions in an IPv6 Environment,” on page 20

n

“Supported Operating Systems for View Servers in an IPv6 Environment,” on page 20

n

“Supported Windows Operating Systems for Desktops and RDS Hosts in an IPv6 Environment,” on

n

page 21

“Supported Clients in an IPv6 Environment,” on page 21

n

“Supported Remoting Protocols in an IPv6 Environment,” on page 21

n

“Supported Authentication Types in an IPv6 Environment,” on page 22

n

“Other Supported Features in an IPv6 Environment,” on page 22

n

Setting Up View in an IPv6 Environment

To run View in an IPv6 environment, you must be aware of the requirements and choices that are specific to
IPv6 when you perform certain administrative tasks.

Before you install View, you must have a working IPv6 environment. The following View administrative
tasks have options that are specific to IPv6.

Installing View Connection Server. See “Install View Connection Server with a New Configuration,” on

n

page 46.

Installing View Replica Server. See “Install a Replicated Instance of View Connection Server,” on

n

page 52.

Installing View Security Server. See “Install a Security Server,” on page 58.

n

Configuring the PCoIP External URL. See “Configuring External URLs for Secure Gateway and Tunnel

n

Connections,” on page 105.

VMware, Inc.

19

View Installation

Setting the PCoIP External URL. See “Set the External URLs for a View Connection Server Instance,” on

n

page 106.

Modifying the PCoIP External URL. See “Set the External URLs for a View Connection Server Instance,”

n

on page 106.

Installing View Agent. See the View Agent installation topics in the Setting Up Desktop and Application

n

Pools document.

Installing Horizon Client for Windows. See the VMware Horizon Client for Windows document in

n

https://www.vmware.com/support/viewclients/doc/viewclients_pubs.html. Only Windows clients are

supported.

NOTE View does not require you to enter an IPv6 address in any administrative tasks. In cases where you
can specify either a fully qualified domain name (FQDN) or an IPv6 address, it is highly recommended that
you specify an FQDN to avoid potential errors.

Supported vSphere , Database, and Active Directory Versions in an IPv6 Environment

In an IPv6 environment, View supports specific vSphere, database server, and Active Directory versions.

The following vSphere versions are supported in an IPv6 environment.

6.0

n

5.5 U2

n

The following database servers are supported in an IPv6 environment.

Database Server Version Edition

SQL Server 2012 SP1 32/64-bit Standard, Enterprise

SQL Server 2012 Express 32/64-bit Free

Oracle 11g R2 32/64-bit Standard, Standard Edition One, Enterprise

The following Active Directory versions are supported in an IPv6 environment.

Microsoft Active Directory 2008 R2

n

Microsoft Active Directory 2012 R2

n

Supported Operating Systems for View Servers in an IPv6 Environment

In an IPv6 environment, you must install View servers on specific Windows Server operating systems.

View servers include View Connection Server instances, replica servers, security servers, and View
Composer instances.

Operating System Edition

Windows Server 2008 R2 Standard, Enterprise

Windows Server 2008 R2 SP1 Standard, Enterprise

Windows Server 2012 R2 Standard

20 VMware, Inc.

Chapter 3 Installing View in an IPv6 Environment

Supported Windows Operating Systems for Desktops and RDS Hosts in an IPv6 Environment

In an IPv6 environment, View supports specific Windows operating systems for desktop machines and RDS
hosts. RDS hosts provide session-based desktops and applications to users.

The following Windows operating systems are supported for desktop machines.

Operating System Version Edition

Windows 7 SP1 32/64-bit Enterprise, Professional

Windows 8 32/64-bit Enterprise, Professional

Windows 8.1 32/64-bit Enterprise, Professional

Windows Server 2008 R2 SP1 Datacenter

The following Windows operating systems are supported for RDS hosts.

Operating System Edition

Windows Server 2008 R2 SP1 Standard, Enterprise, Datacenter

Windows Server 2012 R2 Standard, Datacenter

Supported Clients in an IPv6 Environment

In an IPv6 environment, View supports clients that run on specific desktop operating systems.

Operating System Version Edition

Windows 7 32/64-bit Home, Professional, Enterprise, Ultimate

Windows 7 SP1 32/64-bit Home, Professional, Enterprise, Ultimate

Windows 8 32/64-bit Enterprise, Professional

Windows 8.1 32/64-bit Enterprise, Professional

The following types of clients are not supported.

Clients that run on OS X, Android, iOS, Linux, or Windows Store

n

Horizon Client for Windows with the Local Mode option

n

PCoIP Zero Client

n

Supported Remoting Protocols in an IPv6 Environment

In an IPv6 environment, View supports specific remoting protocols.

The following remoting protocols are supported:

RDP

n

RDP with Secure Tunnel

n

PCoIP

n

PCoIP through PCoIP Secure Gateway

n

The following remoting protocols are not supported:

HTML Access

n

VMware, Inc. 21

View Installation

HTML Access through Blast Secure Gateway

n

Supported Authentication Types in an IPv6 Environment

In an IPv6 environment, View supports specific authentication types.

The following authentication types are supported:

Password authentication using Active Directory

n

Smart Card

n

Single Sign-On

n

The following authentication types are not supported:

SecurID

n

RADIUS

n

SAML

n

Other Supported Features in an IPv6 Environment

In an IPv6 environment, View supports certain features that are not covered in previous topics.

The following features are supported:

Automated desktop pools, including full virtual machines and View Composer linked clones

n

Manual desktop pools, including vCenter Server virtual machines, physical computers, and virtual

n

machines not managed by vCenter Server

RDS desktop pools

n

Application pools

n

View Storage Accelerator

n

Disk space reclamation

n

Native NFS snapshots (VAAI)

n

ThinApp

n

Virtual Printing

n

Events

n

Role-based administration

n

System health dashboard

n

LDAP backup

n

View Composer database backup

n

Customer Experience Improvement Program (CEIP)

n

Single Sign-on, including the Log in as current user feature

n

Audio-out

n

The following features are not supported:

Virtual SAN

n

Virtual Volumes

n

Cloud Pod Architecture

n

22 VMware, Inc.

Scanner redirection

n

USB redirection

n

Multimedia redirection (MMR)

n

Real-time audio-video (RTAV)

n

Persona Management

n

vRealize Operations Desktop Agent

n

Lync

n

Syslog

n

Log Insight

n

Serial redirection

n

Flash URL redirection

n

Teradici TERA host card

n

Chapter 3 Installing View in an IPv6 Environment

VMware, Inc. 23

View Installation

24 VMware, Inc.

Preparing Active Directory 4

View uses your existing Microsoft Active Directory infrastructure for user authentication and management.
You must perform certain tasks to prepare Active Directory for use with View.

View supports the following Active Directory Domain Services (AD DS) domain functional levels:

Windows Server 2003

n

Windows Server 2008

n

Windows Server 2008 R2

n

Windows Server 2012

n

Windows Server 2012 R2

n

This chapter includes the following topics:

“Configuring Domains and Trust Relationships,” on page 25

n

“Creating an OU for Remote Desktops,” on page 26

n

“Creating OUs and Groups for Kiosk Mode Client Accounts,” on page 26

n

“Creating Groups for Users,” on page 27

n

“Creating a User Account for vCenter Server,” on page 27

n

“Creating a User Account for a Standalone View Composer Server,” on page 27

n

“Create a User Account for View Composer AD Operations,” on page 27

n

“Configure the Restricted Groups Policy,” on page 28

n

“Using View Group Policy Administrative Template Files,” on page 29

n

“Prepare Active Directory for Smart Card Authentication,” on page 29

n

Configuring Domains and Trust Relationships

You must join each View Connection Server host to an Active Directory domain. The host must not be a
domain controller. You place remote desktops in the same domain as the View Connection Server host or in
a domain that has a two-way trust relationship with the View Connection Server host's domain. Specifically
this must be an external non-transitive two-way trust.

You can entitle users and groups in the View Connection host's domain to remote desktops and
applications. You can also select users and groups from the View Connection Server host's domain to be
administrators in View Administrator. To entitle or select users and groups from a different domain, you
must establish a two-way trust relationship between that domain and the View Connection Server host's
domain.

VMware, Inc.

25

View Installation

Users are authenticated against Active Directory for the View Connection Server host's domain and against
any additional user domains with which a trust agreement exists.

NOTE Because security servers do not access any authentication repositories, including Active Directory,
they do not need to reside in an Active Directory domain.

Trust Relationships and Domain Filtering

To determine which domains it can access, a View Connection Server instance traverses trust relationships
beginning with its own domain.

For a small, well-connected set of domains, View Connection Server can quickly determine the full list of
domains, but the time that it takes increases as the number of domains increases or as the connectivity
between the domains decreases. The list might also include domains that you would prefer not to offer to
users when they connect to their remote desktops and applications.

You can use the vdmadmin command to configure domain filtering to limit the domains that a View
Connection Server instance searches and that it displays to users. See the View Administration document for
more information.

Creating an OU for Remote Desktops

You should create an organizational unit (OU) specifically for your remote desktops. An OU is a subdivision
in Active Directory that contains users, groups, computers, or other OUs.

To prevent group policy settings from being applied to other Windows servers or workstations in the same
domain as your desktops, you can create a GPO for your View group policies and link it to the OU that
contains your remote desktops. You can also delegate control of the OU to subordinate groups, such as
server operators or individual users.

If you use View Composer, you should create a separate Active Directory container for linked-clone
desktops that is based on the OU for your remote desktops. Administrators that have OU administrator
privileges in Active Directory can provision linked-clone desktops without domain administrator privileges.
If you change administrator credentials in Active Directory, you must also update the credential
information in View Composer.

Creating OUs and Groups for Kiosk Mode Client Accounts

A client in kiosk mode is a thin client or a locked-down PC that runs the client software to connect to a View
Connection Server instance and launch a remote desktop session. If you configure clients in kiosk mode, you
should create dedicated OUs and groups in Active Directory for kiosk mode client accounts.

Creating dedicated OUs and groups for kiosk mode client accounts partitions client systems against
unwarranted intrusion and simplifies client configuration and administration.

See the View Administration document for more information.

26 VMware, Inc.

Creating Groups for Users

You should create groups for different types of users in Active Directory. For example, you can create a
group called View Users for your end users and another group called View Administrators for users that
will administer remote desktops and applications.

Creating a User Account for vCenter Server

You must create a user account in Active Directory to use with vCenter Server. You specify this user account
when you add a vCenter Server instance in View Administrator.

You must give the user account privileges to perform certain operations in vCenter Server. You can create a
vCenter Server role with the appropriate privileges and assign the role to the vCenter Server user. The list of
privileges you add to the vCenter Server role varies, depending on whether you use View with or without
View Composer. See “Configuring User Accounts for vCenter Server and View Composer,” on page 89 for
information on configuring these privileges.

If you install View Composer on the same machine as vCenter Server, you must add the vCenter Server user
to the local Administrators group on the vCenter Server machine. This requirement allows View to
authenticate to the View Composer service.

If you install View Composer on a different machine than vCenter Server, you do not have to make the
vCenter Server user a local administrator on the vCenter Server machine. However, you do have to create a
standalone View Composer Server user account that must be a local administrator on the View Composer
machine.

Chapter 4 Preparing Active Directory

Creating a User Account for a Standalone View Composer Server

If you install View Composer on a different machine than vCenter Server, you must create a domain user
account in Active Directory that View can use to authenticate to the View Composer service on the
standalone machine.

The user account must be in the same domain as your View Connection Server host or in a trusted domain.
You must add the user account to the local Administrators group on the standalone View Composer
machine.

You specify this user account when you configure View Composer settings in View Administrator and
select Standalone View Composer Server. See “Configure View Composer Settings,” on page 96.

Create a User Account for View Composer AD Operations

If you use View Composer, you must create a user account in Active Directory that allows View Composer
to perform certain operations in Active Directory. View Composer requires this account to join linked-clone
virtual machines to your Active Directory domain.

To ensure security, you should create a separate user account to use with View Composer. By creating a
separate account, you can guarantee that it does not have additional privileges that are defined for another
purpose. You can give the account the minimum privileges that it needs to create and remove computer
objects in a specified Active Directory container. For example, the View Composer account does not require
domain administrator privileges.

Procedure

1 In Active Directory, create a user account in the same domain as your View Connection Server host or

in a trusted domain.

VMware, Inc. 27

View Installation

2 Add the Create Computer Objects, Delete Computer Objects, and Write All Properties permissions to

the account in the Active Directory container in which the linked-clone computer accounts are created
or to which the linked-clone computer accounts are moved.

The following list shows all the required permissions for the user account, including permissions that
are assigned by default:

List Contents

n

Read All Properties

n

Write All Properties

n

Read Permissions

n

Reset Password

n

Create Computer Objects

n

Delete Computer Objects

n

NOTE Fewer permissions are required if you select the Allow reuse of pre-existing computer accounts
setting for a desktop pool. Make sure that the following permissions are assigned to the user account:

List Contents

n

Read All Properties

n

Read Permissions

n

Reset Password

n

3 Make sure that the user account's permissions apply to the Active Directory container and to all child

objects of the container.

What to do next

Specify the account in View Administrator when you configure View Composer domains in the Add
vCenter Server wizard and when you configure and deploy linked-clone desktop pools.

Configure the Restricted Groups Policy

To be able to connect to a remote desktop, users must belong to the local Remote Desktop Users group of
the remote desktop. You can use the Restricted Groups policy in Active Directory to add users or groups to
the local Remote Desktop Users group of every remote desktop that is joined to your domain.

The Restricted Groups policy sets the local group membership of computers in the domain to match the
membership list settings defined in the Restricted Groups policy. The members of your remote desktop
users group are always added to the local Remote Desktop Users group of every remote desktop that is
joined to your domain. When adding new users, you need only add them to your remote desktop users
group.

Prerequisites

Create a group for remote desktop users in your domain in Active Directory.

28 VMware, Inc.

Chapter 4 Preparing Active Directory

Procedure

1 On the Active Directory server, navigate to the Group Policy Management plug-in.

AD Version Navigation Path

Windows 2003

Windows 2008

a Select Start > All Programs > Administrative Tools > Active Directory

Users and Computers.

b Right-click your domain and click Properties.

c On the Group Policy tab, click Open to open the Group Policy

Management plug-in.

d Right-click Default Domain Policy, and click Edit.

a Select Start > Administrative Tools > Group Policy Management.

b Expand your domain, right-click Default Domain Policy, and click

Edit.

2 Expand the Computer Configuration section and open Windows Settings\Security Settings.

3 Right-click Restricted Groups, select Add Group, and add the Remote Desktop Users group.

4 Right-click the new restricted Remote Desktop Users group and add your remote desktop users group

to the group membership list.

5 Click OK to save your changes.

Using View Group Policy Administrative Template Files

View includes several component-specific group policy administrative (ADM and ADMX) template files.

All ADM and ADMX files that provide group policy settings for View are available in a bundled .zip file
named VMware-Horizon-View-Extras-Bundle-x.x.x-yyyyyyy.zip, where x.x.x is the version and yyyyyyy is
the build number. You can download the file from the VMware Horizon 6 download site at

http://www.vmware.com/go/downloadview.

You can optimize and secure remote desktops by adding the policy settings in these files to a new or
existing GPO in Active Directory and then linking that GPO to the OU that contains your desktops.

See the View Administration and Setting Up Desktop and Application Pools in View documents for information
on using View group policy settings.

Prepare Active Directory for Smart Card Authentication

You might need to perform certain tasks in Active Directory when you implement smart card
authentication.

Add UPNs for Smart Card Users on page 30

n

Because smart card logins rely on user principal names (UPNs), the Active Directory accounts of users
and administrators that use smart cards to authenticate in View must have a valid UPN.

Add the Root Certificate to Trusted Root Certification Authorities on page 30

n

If you use a certification authority (CA) to issue smart card login or domain controller certificates, you
must add the root certificate to the Trusted Root Certification Authorities group policy in Active
Directory. You do not need to perform this procedure if the Windows domain controller acts as the
root CA.

Add an Intermediate Certificate to Intermediate Certification Authorities on page 31

n

If you use an intermediate certification authority (CA) to issue smart card login or domain controller
certificates, you must add the intermediate certificate to the Intermediate Certification Authorities
group policy in Active Directory.

VMware, Inc. 29

View Installation

Add the Root Certificate to the Enterprise NTAuth Store on page 31

n

If you use a CA to issue smart card login or domain controller certificates, you must add the root
certificate to the Enterprise NTAuth store in Active Directory. You do not need to perform this
procedure if the Windows domain controller acts as the root CA.

Add UPNs for Smart Card Users

Because smart card logins rely on user principal names (UPNs), the Active Directory accounts of users and
administrators that use smart cards to authenticate in View must have a valid UPN.

If the domain a smart card user resides in is different from the domain that your root certificate was issued
from, you must set the user’s UPN to the Subject Alternative Name (SAN) contained in the root certificate of
the trusted CA. If your root certificate was issued from a server in the smart card user's current domain, you
do not need to modify the user's UPN.

NOTE You might need to set the UPN for built-in Active Directory accounts, even if the certificate is issued
from the same domain. Built-in accounts, including Administrator, do not have a UPN set by default.

Prerequisites

Obtain the SAN contained in the root certificate of the trusted CA by viewing the certificate properties.

n

If the ADSI Edit utility is not present on your Active Directory server, download and install the

n

appropriate Windows Support Tools from the Microsoft Web site.

Procedure

1 On your Active Directory server, start the ADSI Edit utility.

2 In the left pane, expand the domain the user is located in and double-click CN=Users.

3 In the right pane, right-click the user and then click Properties.

4 Double-click the userPrincipalName attribute and type the SAN value of the trusted CA certificate.

5 Click OK to save the attribute setting.

Add the Root Certificate to Trusted Root Certification Authorities

If you use a certification authority (CA) to issue smart card login or domain controller certificates, you must
add the root certificate to the Trusted Root Certification Authorities group policy in Active Directory. You
do not need to perform this procedure if the Windows domain controller acts as the root CA.

Procedure

1 On the Active Directory server, navigate to the Group Policy Management plug-in.

AD Version Navigation Path

Windows 2003

Windows 2008

2 Expand the Computer Configuration section and open Windows Settings\Security Settings\Public

Key.

a Select Start > All Programs > Administrative Tools > Active Directory

Users and Computers.

b Right-click your domain and click Properties.

c On the Group Policy tab, click Open to open the Group Policy

Management plug-in.

d Right-click Default Domain Policy, and click Edit.

a Select Start > Administrative Tools > Group Policy Management.

b Expand your domain, right-click Default Domain Policy, and click

Edit.

30 VMware, Inc.