VMware Horizon View - 6.0 Installation Manual

View Installation

VMware Horizon 6.0

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-001496-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:

docfeedback@vmware.com

VMware, Inc.

3401 Hillview Ave. Palo Alto, CA 94304 www.vmware.com

2 VMware, Inc.

View Installation 5

System Requirements for Server Components 7

View Connection Server Requirements 7

View Administrator Requirements 9

View Composer Requirements 9

System Requirements for Guest Operating Systems 13

Supported Operating Systems for View Agent 13

Supported Operating Systems for Standalone View Persona Management 14

Remote Display Protocol and Software Support 14

Preparing Active Directory 19

Configuring Domains and Trust Relationships 19

Creating an OU for Remote Desktops 20

Creating OUs and Groups for Kiosk Mode Client Accounts 20

Creating Groups for Users 21

Creating a User Account for vCenter Server 21

Create a User Account for View Composer 21

Configure the Restricted Groups Policy 22

Using View Group Policy Administrative Template Files 23

Prepare Active Directory for Smart Card Authentication 23

VMware, Inc.

Installing View Composer 27

Prepare a View Composer Database 27

Configuring an SSL Certificate for View Composer 33

Install the View Composer Service 33

Configuring Your Infrastructure for View Composer 35

Installing View Connection Server 37

Installing the View Connection Server Software 37

Installation Prerequisites for View Connection Server 37

Install View Connection Server with a New Configuration 38

Install a Replicated Instance of View Connection Server 43

Configure a Security Server Pairing Password 49

Install a Security Server 50

Firewall Rules for View Connection Server 56

Reinstall View Connection Server with a Backup Configuration 58

Microsoft Windows Installer Command-Line Options 59

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

View Installation

Configuring SSL Certificates for View Servers 63

Understanding SSL Certificates for View Servers 63

Overview of Tasks for Setting Up SSL Certificates 65

Obtaining a Signed SSL Certificate from a CA 66

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

Certificate 67

Configure Client Endpoints to Trust Root and Intermediate Certificates 72

Configuring Certificate Revocation Checking on Server Certificates 74

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

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

Benefits of Using SSL Certificates Signed by a CA 79

Troubleshooting Certificate Issues on View Connection Server and Security Server 80

Configuring View for the First Time 81

Configuring User Accounts for vCenter Server and View Composer 81

Configuring View Connection Server for the First Time 84

Configuring Horizon Client Connections 94

Replacing Default Ports for View Services 100

Sizing Windows Server Settings to Support Your Deployment 104

Configuring Event Reporting 107

Add a Database and Database User for View Events 107

Prepare an SQL Server Database for Event Reporting 108

Configure the Event Database 109

Configure Event Logging for Syslog Servers 110

Index 113

4 VMware, Inc.

View Installation

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

Intended Audience

This information is intended for anyone who wants to install View. 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

“View Administrator Requirements,” on page 9

“View Composer Requirements,” on page 9

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

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

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

Virtualization Software Requirements for View Connection Server on page 8

View Connection Server requires certain versions of VMware virtualization software.

Network Requirements for Replicated View Connection Server Instances on page 9

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.

View Installation

Hardware Requirements for View Connection Server

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 64-bit

Memory

Windows Server 2012 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 use a static IP address.

4GB RAM or higher At least 10GB RAM for deployments of 50 or more

4 CPUs

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 64-bit Standard

Enterprise

Windows Server 2008 R2 SP1 64-bit Standard

Enterprise

Windows Server 2012 R2 64-bit Standard

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

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 8

Internet Explorer 9

Internet Explorer 10 (from a Windows 8 system in Desktop mode)

Firefox 6 and later releases

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

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

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 10

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

Table 1‑3. Operating System Support for View Composer

Operating System Version Edition

Windows Server 2008 R2 64-bit Standard

Windows Server 2008 R2 SP1 64-bit Standard

Windows Server 2012 R2 64-bit Standard

Enterprise

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-toone 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

IMPORTANT The physical or virtual machine that hosts View Composer must use a static IP address.

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

10 VMware, Inc.

Chapter 1 System Requirements for Server Components

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 and View database events.

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. For a complete list of database versions supported with vCenter Server, see the VMware Product Interoperability Matrixes at

http://www.vmware.com/resources/compatibility/sim/interop_matrix.php.

The versions of vCenter Server listed in the table column headings are general. For specific supported update versions of each vCenter Server release, see the VMware Product Interoperability Matrixes at

http://www.vmware.com/resources/compatibility/sim/interop_matrix.php.

Table 1‑5. Supported Database Servers for View Composer

Database

Microsoft SQL Server 2012 Express

(32- and 64-bit)

Microsoft SQL Server 2012 (SP1) Standard and Enterprise

(32- and 64-bit)

Microsoft SQL Server 2008 Express (R2 SP2)

(64-bit)

Microsoft SQL Server 2008 (SP3), Standard, Enterprise, and Datacenter

(32- and 64-bit)

Microsoft SQL Server 2008 (R2 SP2), Standard and Enterprise

(32- and 64-bit)

Oracle 10g Release 2, Standard, Standard ONE, and Enterprise [10.2.0.4]

(32- and 64-bit)

Oracle 11g Release 2, Standard, Standard ONE, and Enterprise [11.2.0.3]

(32- and 64-bit)

vCenter Server

5.5

Yes Yes Yes No

No Yes Yes No

No Yes Yes Yes

Yes Yes Yes Yes

No Yes Yes Yes

Yes Yes Yes Yes

vCenter Server

5.1

vCenter Server

5.0

vCenter Server 4.1

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

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

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

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.

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 Vista 32-bit Business and

Enterprise

Windows XP 32-bit Professional SP3

Windows Server 2008 R2 64-bit Datacenter SP1

None and Update

None

None and SP1

SP2

VMware, Inc.

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

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

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.

View Installation

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

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 5.x 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 Pro - Desktop and Enterprise -

Desktop

Windows 7 64-bit and 32-bit Enterprise and Professional None and SP1

Windows Vista 32-bit Business and Enterprise SP1 and SP2

Windows XP 32-bit Professional SP3

The standalone View Persona Management software is not supported on Microsoft Terminal Services or 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

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.

N/A

Microsoft RDP on page 16

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

(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

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

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

Connections from all types of client devices.

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

32-bit color is supported for virtual displays.

ClearType fonts are supported.

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

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

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

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

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.

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

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

Recommended operating system settings for remote desktops include the following settings:

For Windows XP desktops: 768MB RAM or more and a single CPU.

VMware, Inc. 15

View Installation

Video Quality Requirements

For Windows 7 or 8 desktops or Windows Server 2012 or R2 desktops: 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.

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 the operating system is Windows 7 or later and 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

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:

With RDP 6, you can use multiple monitors in span mode. RDP 7 has true multiple monitor support, for

up to 16 monitors.

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

the remote desktop.

32-bit color is supported for virtual displays.

RDP supports 128-bit encryption.

16 VMware, Inc.

Chapter 2 System Requirements for Guest Operating Systems

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

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

NOTE For Windows XP desktop virtual machines, you must install the RDP patches listed in Microsoft Knowledge Base (KB) articles 323497 and 884020. If you do not install the RDP patches, a Windows Sockets

failed error message might appear on the client.

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.

Preparing Active Directory 3

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

Windows Server 2008

Windows Server 2008 R2

Windows Server 2012

Windows Server 2012 R2

This chapter includes the following topics:

“Configuring Domains and Trust Relationships,” on page 19

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

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

“Creating Groups for Users,” on page 21

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

“Create a User Account for View Composer,” on page 21

“Configure the Restricted Groups Policy,” on page 22

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

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

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.

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.

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

The user account must be in the same domain as your View Connection Server host or in a trusted domain. If you use View Composer, you must add the user account to the local Administrators group on the vCenter Server computer.

You must give the user account privileges to perform certain operations in vCenter Server. If you use View Composer, you must give the user account additional privileges. See “Configuring User Accounts for

vCenter Server and View Composer,” on page 81 for information on configuring these privileges.

Create a User Account for View Composer

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

Chapter 3 Preparing Active Directory

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.

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

Read All Properties

Write All Properties

Read Permissions

Reset Password

Create Computer Objects

VMware, Inc. 21

View Installation

Delete Computer Objects

NOTE If you select the Allow reuse of pre-existing computer accounts setting for a desktop pool, you only need to add the following permissions:

List Contents

Read All Properties

Read Permissions

Reset Password

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 for vCenter Server 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.

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.

22 VMware, Inc.

Chapter 3 Preparing Active Directory

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-GPO-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 (with View) 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 23

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 24

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 25

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.

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

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.

VMware, Inc. 23

View Installation

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

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

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\Public

Key.

3 Right-click Trusted Root Certification Authorities and select Import.

4 Follow the prompts in the wizard to import the root certificate (for example, rootCA.cer) and click OK.

5 Close the Group Policy window.

All of the systems in the domain now have a copy of the root certificate in their trusted root store.

What to do next

If an intermediate certification authority (CA) issues your smart card login or domain controller certificates, add the intermediate certificate to the Intermediate Certification Authorities group policy in Active Directory. See “Add an Intermediate Certificate to Intermediate Certification Authorities,” on page 25.

24 VMware, Inc.

Chapter 3 Preparing Active Directory

Add an Intermediate Certificate to Intermediate Certification Authorities

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 the policy for 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.

3 Right-click Intermediate Certification Authorities and select Import.

4 Follow the prompts in the wizard to import the intermediate certificate (for example,

intermediateCA.cer) and click OK.

5 Close the Group Policy window.

All of the systems in the domain now have a copy of the intermediate certificate in their intermediate certification authority store.

Add the Root Certificate to the Enterprise NTAuth Store

Procedure

On your Active Directory server, use the certutil command to publish the certificate to the Enterprise

NTAuth store.

For example: certutil -dspublish -f path_to_root_CA_cert NTAuthCA

The CA is now trusted to issue certificates of this type.

VMware, Inc. 25

View Installation

26 VMware, Inc.

Installing View Composer 4

To use View Composer, you create a View Composer database, install the View Composer service, and optimize your View infrastructure to support View Composer. You can install the View Composer service on the same host as vCenter Server or on a separate host.

View Composer is an optional feature. Install View Composer if you intend to deploy linked-clone desktop pools.

You must have a license to install and use the View Composer feature.

This chapter includes the following topics:

“Prepare a View Composer Database,” on page 27

“Configuring an SSL Certificate for View Composer,” on page 33

“Install the View Composer Service,” on page 33

“Configuring Your Infrastructure for View Composer,” on page 35

Prepare a View Composer Database

You must create a database and data source name (DSN) to store View Composer data.

VMware, Inc.

The View Composer service does not include a database. If a database instance does not exist in your network environment, you must install one. After you install a database instance, you add the View Composer database to the instance.

You can add the View Composer database to the instance on which the vCenter Server database is located. You can configure the database locally, or remotely, on a network-connected Linux, UNIX, or Windows Server computer.

The View Composer database stores information about connections and components that are used by View Composer:

vCenter Server connections

Active Directory connections

Linked-clone desktops that are deployed by View Composer

Replicas that are created by View Composer

Each instance of the View Composer service must have its own View Composer database. Multiple View Composer services cannot share a View Composer database.

For a list of supported database versions, see “Database Requirements for View Composer,” on page 10.

To add a View Composer database to an installed database instance, choose one of these procedures.

View Installation

Create a SQL Server Database for View Composer on page 28

View Composer can store linked-clone desktop information in a SQL Server database. You create a View Composer database by adding it to SQL Server and configuring an ODBC data source for it.

Create an Oracle Database for View Composer on page 30

View Composer can store linked-clone desktop information in an Oracle 11g or 10g database. You create a View Composer database by adding it to an existing Oracle instance and configuring an ODBC data source for it. You can add a new View Composer database by using the Oracle Database Configuration Assistant or by running a SQL statement.

Create a SQL Server Database for View Composer

View Composer can store linked-clone desktop information in a SQL Server database. You create a View Composer database by adding it to SQL Server and configuring an ODBC data source for it.

Add a View Composer Database to SQL Server

You can add a new View Composer database to an existing Microsoft SQL Server instance to store linkedclone data for View Composer.

If the database resides locally, on the system on which View Composer will be installed, you can use the Integrated Windows Authentication security model. If the database resides on a remote system, you cannot use this method of authentication.

Prerequisites

Verify that a supported version of SQL Server is installed on the computer on which you will install

View Composer or in your network environment. For details, see “Database Requirements for View

Composer,” on page 10.

Verify that you use SQL Server Management Studio or SQL Server Management Studio Express to

create and administer the data source. You can download and install SQL Server Management Studio Express from the following Web site.

http://www.microsoft.com/downloadS/details.aspx? familyid=C243A5AE-4BD1-4E3D-94B8-5A0F62BF7796

Procedure

1 On the View Composer computer, select Start > All Programs > Microsoft SQL Server 2008 or

Microsoft SQL Server 2005.

2 Select SQL Server Management Studio Express and connect to the existing SQL Server instance for

vSphere Management.

3 In the Object Explorer panel, right-click the Databases entry and select New Database.

4 In the New Database dialog box, type a name in the Database name text box.

For example: viewComposer

5 Click OK.

SQL Server Management Studio Express adds your database to the Databases entry in the Object Explorer panel.

6 Exit Microsoft SQL Server Management Studio Express.

What to do next

Follow the instructions in “Add an ODBC Data Source to SQL Server,” on page 29.

28 VMware, Inc.

Chapter 4 Installing View Composer

Add an ODBC Data Source to SQL Server

After you add a View Composer database to SQL Server, you must configure an ODBC connection to the new database to make this data source visible to the View Composer service.

When you configure an ODBC DSN for View Composer, secure the underlying database connection to an appropriate level for your environment. For information about securing database connections, see the SQL Server documentation.

If the underlying database connection uses SSL encryption, we recommend that you configure your database servers with SSL certificates signed by a trusted CA. If you use self-signed certificates, your database connections might be susceptible to man-in-the-middle attacks.

Prerequisites

Complete the steps described in “Add a View Composer Database to SQL Server,” on page 28.

Procedure

1 On the computer on which View Composer will be installed, select Start > Administrative Tools > Data

Source (ODBC).

2 Select the System DSN tab.

3 Click Add and select SQL Native Client from the list.

4 Click Finish.

5 In the Create a New Data Source to SQL Server setup wizard, type a name and description of the View

Composer database.

For example: ViewComposer

6 In the Server text box, type the SQL Server database name.

Use the form host_name\server_name, where host_name is the name of the computer and server_name is the SQL Server instance.

For example: VCHOST1\VIM_SQLEXP

7 Click Next.

8 Make sure that the Connect to SQL Server to obtain default settings for the additional configuration

options check box is selected and select an authentication option.

Option Description

Windows NT authentication

SQL Server authentication

Select this option if you are using a local instance of SQL Server. This option is also known as trusted authentication. Windows NT authentication is supported only if SQL Server is running on the local computer.

Select this option if you are using a remote instance of SQL Server. Windows NT authentication is not supported on remote SQL Server.

9 Click Next.

10 Select the Change the default database to check box and select the name of the View Composer

database from the list.

For example: ViewComposer

11 If the SQL Server connection is configured with SSL enabled, navigate to the Microsoft SQL Server DSN

Configuration page and select Use strong encryption for data.

12 Finish and close the Microsoft ODBC Data Source Administrator wizard.

VMware, Inc. 29

View Installation

What to do next

Install the new View Composer service. See “Install the View Composer Service,” on page 33.

Create an Oracle Database for View Composer

Add a View Composer Database to Oracle 11g or 10g on page 30

You can use the Oracle Database Configuration Assistant to add a new View Composer database to an existing Oracle 11g or 10g instance.

Use a SQL Statement to Add a View Composer Database to an Oracle Instance on page 31

The View Composer database must have certain table spaces and privileges. You can use a SQL statement to create the View Composer database in an Oracle 11g or 10g database instance.

Configure an Oracle Database User for View Composer on page 31

By default, the database user that runs the View Composer database has Oracle system administrator permissions. To restrict the security permissions for the user that runs the View Composer database, you must configure an Oracle database user with specific permissions.

Add an ODBC Data Source to Oracle 11g or 10g on page 32

After you add a View Composer database to an Oracle 11g or 10g instance, you must configure an ODBC connection to the new database to make this data source visible to the View Composer service.

Add a View Composer Database to Oracle 11g or 10g

You can use the Oracle Database Configuration Assistant to add a new View Composer database to an existing Oracle 11g or 10g instance.

Prerequisites

Verify that a supported version of Oracle 11g or 10g is installed on the local or remote computer. See

“Database Requirements for View Composer,” on page 10.

Procedure

1 Start the Database Configuration Assistant on the computer on which you are adding the View

Composer database.

Database Version Action

Oracle 11g

Oracle 10g

2 On the Operations page, select Create a database.

Select Start > All Programs > Oracle-OraDb11g_home > Configuration and Migration Tools > Database Configuration Assistant.

Select Start > All Programs > Oracle-OraDb10g_home > Configuration and Migration Tools > Database Configuration Assistant.

3 On the Database Templates page, select the General Purpose or Transaction Processing template.

4 On the Database Identification page, type a Global Database Name and an Oracle System Identifier

(SID) prefix.

For simplicity, use the same value for both items.

5 On the Management Options page, click Next to accept the default settings.

30 VMware, Inc.

+ 86 hidden pages