5.2
Table Of Contents
- VMware Horizon View Architecture Planning
- Contents
- VMware Horizon View Architecture Planning
- Introduction to Horizon View
- Planning a Rich User Experience
- Feature Support Matrix
- Choosing a Display Protocol
- Using View Persona Management to Retain User Data and Settings
- Benefits of Using View Desktops in Local Mode
- Accessing USB Devices Connected to a Local Computer
- Printing from a View Desktop
- Streaming Multimedia to a View Desktop
- Using Single Sign-On for Logging In to a View Desktop
- Using Multiple Monitors with a View Desktop
- Managing Desktop Pools from a Central Location
- Architecture Design Elements and Planning Guidelines
- Virtual Machine Requirements
- Horizon View ESX/ESXi Node
- Desktop Pools for Specific Types of Workers
- Desktop Virtual Machine Configuration
- vCenter Server and View Composer Virtual Machine Configuration
- View Connection Server Maximums and Virtual Machine Configuration
- View Transfer Server Virtual Machine Configuration and Storage
- vSphere Clusters
- Storage and Bandwidth Requirements
- Horizon View Building Blocks
- Horizon View Pods
- Advantages of Using Multiple vCenter Servers in a Pod
- Planning for Security Features
- Understanding Client Connections
- Choosing a User Authentication Method
- Restricting View Desktop Access
- Using Group Policy Settings to Secure View Desktops
- Implementing Best Practices to Secure Client Systems
- Assigning Administrator Roles
- Preparing to Use a Security Server
- Understanding Horizon View Communications Protocols
- Overview of Steps to Setting Up a Horizon View Environment
- Index
Table 4-7. Connection Server Virtual Machine Example (Continued)
Item Example
Virtual SCSI adapter type LSI Logic SAS (the default for Windows Server 2008)
Virtual network adapter VMXNET 3
1 NIC 1 Gigabit
View Connection Server Cluster Design Considerations
You can deploy multiple replicated View Connection Server instances in a group to support load balancing
and high availability. Groups of replicated instances are designed to support clustering within a LAN-
connected single-datacenter environment.
IMPORTANT VMware does not recommend or support using a group of replicated View Connection Server
instances across a WAN, MAN (metropolitan area network), or other non-LAN due to the communication
traffic needed between the grouped instances. In scenarios where a View deployment needs to span
datacenters, create a separate Horizon View deployment for each datacenter.
Maximum Connections for View Connection Server
Table 4-8 provides information about the tested limits regarding the number of simultaneous connections that
a Horizon View deployment can accommodate.
This example assumes that you are using Horizon View with vSphere 4.1 or later and vCenter Server 4.1 or
later. It also assumes that View Connection Server is running on a 64-bit Windows Server 2008 R2 Enterprise
operating system.
Table 4-8. View Desktop Connections
Connection Servers per Deployment Connection Type
Maximum Simultaneous
Connections
1 Connection Server Direct connection, RDP or PCoIP;
Tunneled connection, RDP;
PCoIP Secure Gateway connection
2,000
7 Connection Servers (5 + 2 spares) Direct connection, RDP or PCoIP 10,000
1 Connection Server Unified Access to physical PCs 100
1 Connection Server Unified Access to terminal servers 200
PCoIP Secure Gateway connections are required if you use security servers for PCoIP connections from outside
the corporate network. Tunneled connections are required if you use security servers for RDP connections
from outside the corporate network and for USB and multimedia redirection (MMR) acceleration with a PCoIP
Secure Gateway connection. You can pair multiple security servers to a single connection server.
View Transfer Server Virtual Machine Configuration and Storage
View Transfer Server is required to support desktops that run View Client with Local Mode (formerly called
Offline Desktop). This server requires less memory than View Connection Server.
View Transfer Server Configuration
You must install View Transfer Server on a virtual rather than a physical machine and the virtual machine
must be managed by the same vCenter Server instance as the local desktops that it will manage. Table 4-9 lists
the virtual machine specifications for a View Transfer Server instance.
Chapter 4 Architecture Design Elements and Planning Guidelines
VMware, Inc. 47