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
Table 5‑2. Back-End Firewall Rules (Continued)
Source
Default
Port Protocol Destination
Default
Port Notes
Security
server
TCP Any
UDP
55000
PCoIP Remote
desktop or
application
TCP 4172
UDP 4172
Security servers connect to remote desktops and
applications on TCP port 4172 and UDP port 4172 to
exchange PCoIP traffic.
Remote
desktop or
application
UDP 4172 PCoIP Security server UDP
55000
Remote desktops and applications send PCoIP data
back to a security server from UDP port 4172 .
The destination UDP port will be the source port from
the received UDP packets and so as this is reply data, it
is normally unnecessary to add an explicit firewall rule
for this.
Security
server
TCP Any USB-R Remote
desktop
TCP 32111 Security servers connect to remote desktops on TCP
port 32111 to exchange USB redirection traffic between
an external client device and the remote desktop.
Security
server
TCP Any HTTPS Remote
desktop
TCP 22443 If you use HTML Access, security servers connect to
remote desktops on HTTPS port 22443 to communicate
with the Blast agent.
Security
server
ESP Connection
Server
Encapsulated AJP13 traffic when NAT traversal is not
required. ESP is IP protocol 50. Port numbers are not
specified.
Connection
Server
ESP Security server Encapsulated AJP13 traffic when NAT traversal is not
required. ESP is IP protocol 50. Port numbers are not
specified.
Understanding View Communications Protocols
View components exchange messages by using several different protocols.
Figure 5-5 illustrates the protocols that each component uses for communication when a security server is
not configured. That is, the secure tunnel for RDP and the PCoIP secure gateway are not turned on. This
configuration might be used in a typical LAN deployment.
View Architecture Planning
86 VMware, Inc.