Architecture Planning
Table Of Contents
- View Architecture Planning
- Contents
- View Architecture Planning
- Introduction to View
- Planning a Rich User Experience
- Feature Support Matrix for View Agent
- Choosing a Display Protocol
- Using Hosted Applications
- Using View Persona Management to Retain User Data and Settings
- Using USB Devices with Remote Desktops and Applications
- Using the Real-Time Audio-Video Feature for Webcams and Microphones
- Using 3D Graphics Applications
- Streaming Multimedia to a Remote Desktop
- Printing from a Remote Desktop
- Using Single Sign-On for Logging In to a Remote Desktop
- Using Multiple Monitors
- Managing Desktop and Application Pools from a Central Location
- Architecture Design Elements and Planning Guidelines for Remote Desktop Deployments
- Virtual Machine Requirements for Remote Desktops
- View ESXi Node
- Desktop Pools for Specific Types of Workers
- Desktop Virtual Machine Configuration
- RDS Host Virtual Machine Configuration
- vCenter Server and View Composer Virtual Machine Configuration
- View Connection Server Maximums and Virtual Machine Configuration
- vSphere Clusters
- Storage and Bandwidth Requirements
- View Building Blocks
- View Pods
- Advantages of Using Multiple vCenter Servers in a Pod
- Planning for Security Features
- Understanding Client Connections
- Choosing a User Authentication Method
- Restricting Remote Desktop Access
- Using Group Policy Settings to Secure Remote Desktops and Applications
- Implementing Best Practices to Secure Client Systems
- Assigning Administrator Roles
- Preparing to Use a Security Server
- Understanding View Communications Protocols
- Overview of Steps to Setting Up a View Environment
- Index
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 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.
Maximum Connections for View Connection Server
Table 4-7 provides information about the tested limits regarding the number of simultaneous connections
that a View deployment can accommodate.
This example assumes that View Connection Server is running on a 64-bit Windows Server 2008 R2
Enterprise operating system.
Table 4‑7. Remote 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 (tested limit)
2,000 (hard limit)
2,000 (hard limit)
7 Connection Servers Direct connection, RDP or PCoIP 10,000 (tested, and therefore
supported, limit)
1 Connection Server Unified Access to physical PCs 2,000
1 Connection Server Unified Access to RDS hosts 2,000
1 Connection Server Blast Secure Gateway connections to remote
desktops using HTML Access
2,000 (tested limit)
PCoIP Secure Gateway connections are required if you use security servers or Access Point appliances for
PCoIP connections from outside the corporate network. Tunneled connections are required if you use
security servers or Access Point appliances 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 View Connection Server instance.
Although the maximum number of simultaneous connections to security servers is also 2,000, instead of
using just one security server per View Connection Server instance (with 2,000 sessions), you might choose
to use 2 or 4. Monitoring of the security server might indicate that the PCoIP activity for 2,000 users is too
great. The required amount of memory and CPU usage might dictate that you add more security servers per
View Connection Server instance to spread the load. For example, you might use 2 security servers, with
each one handling 1,000 connections, or you might use 4 security servers, with each one handling 500
connections. The ratio of security servers to View Connection Server instances depends on the requirements
of the particular environment.
View Architecture Planning
56 VMware, Inc.