6.0
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
- 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
Table 4‑9. Remote Desktop Connections (Continued)
Connection Servers per
Deployment Connection Type
Maximum Simultaneous
Connections
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
800
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
View Connection Server instance.
NOTE In this example, although 5 View Connection Server instances could handle 10,000 connections, the
number 7 is shown in the table for availability planning purposes, to accommodate connections coming
from both inside and outside of the corporate network.
For example, if you had 10,000 users, with 8,000 of them inside the corporate network, you would need 5
View Connection Server instances inside the corporate network. That way, if one of the instances became
unavailable, the 4 remaining instances could handle the load. Similarly, for the 2,000 connections coming
from outside the corporate network, you would use 2 View Connection Server instances so that if one
became unavailable, you would still have one instance left that could handle the load.
.
vSphere Clusters
View deployments can use VMware HA clusters to guard against physical server failures. With vSphere 5.1
and later, if you use View Composer and store replica disks on NFS datastores or VMFS5 datastores, the
cluster can contain up to 32 servers, or nodes. With vSphere 5.5 Update 1 and later, you can use Virtual SAN
datastores, and the cluster can contain up to 32 servers.
vSphere and vCenter Server provide a rich set of features for managing clusters of servers that host virtual
machine desktops. The cluster configuration is also important because each virtual machine desktop pool
must be associated with a vCenter Server resource pool. Therefore, the maximum number of desktops per
pool is related to the number of servers and virtual machines that you plan to run per cluster.
In very large View deployments, vCenter Server performance and responsiveness can be improved by
having only one cluster object per datacenter object, which is not the default behavior. By default,
vCenter Server creates new clusters within the same datacenter object.
Determining Requirements for High Availability
vSphere, through its efficiency and resource management, lets you achieve industry-leading levels of virtual
machines per server. But achieving a higher density of virtual machines per server means that more users
are affected if a server fails.
Requirements for high availability can differ substantially based on the purpose of the desktop pool. For
example, a stateless desktop image (floating-assignment) pool might have different recovery point objective
(RPO) requirements than a stateful desktop image (dedicated-assignment) pool. For a floating-assignment
pool, an acceptable solution might be to have users log in to a different desktop if the desktop they are using
becomes unavailable.
Chapter 4 Architecture Design Elements and Planning Guidelines for Remote Desktop Deployments
VMware, Inc. 55