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
n
Client Connections Using the PCoIP Secure Gateway on page 74
When clients connect to a remote desktop or application with the PCoIP display protocol from
VMware, Horizon Client can make a second connection to the PCoIP Secure Gateway component on a
View Connection Server instance, security server, or Access Point appliance. This connection provides
the required level of security and connectivity when accessing remote desktops and applications from
the Internet.
n
Tunneled Client Connections with Microsoft RDP on page 75
When users connect to a remote desktop with the Microsoft RDP display protocol, Horizon Client can
make a second HTTPS connection to the View Connection Server host. This connection is called the
tunnel connection because it provides a tunnel for carrying RDP data.
n
Direct Client Connections on page 75
Administrators can configure View Connection Server settings so that remote desktop and application
sessions are established directly between the client system and the remote application or desktop
virtual machine, bypassing the View Connection Server host. This type of connection is called a direct
client connection.
Client Connections Using the PCoIP Secure Gateway
When clients connect to a remote desktop or application with the PCoIP display protocol from VMware,
Horizon Client can make a second connection to the PCoIP Secure Gateway component on a View
Connection Server instance, security server, or Access Point appliance. This connection provides the
required level of security and connectivity when accessing remote desktops and applications from the
Internet.
Security servers and Access Point appliances include a PCoIP Secure Gateway component, which offers the
following advantages:
n
The only remote desktop and application traffic that can enter the corporate data center is traffic on
behalf of a strongly authenticated user.
n
Users can access only the resources that they are authorized to access.
n
This connection supports PCoIP, which is an advanced remote display protocol that makes more
efficient use of the network by encapsulating video display packets in UDP instead of TCP.
n
PCoIP is secured by AES-128 encryption by default. You can, however, change the encryption cipher to
AES-256.
n
No VPN is required, as long as PCoIP is not blocked by any networking component. For example,
someone trying to access their remote desktop or application from inside a hotel room might find that
the proxy the hotel uses is not configured to pass PCoIP.
For more information, see “Firewall Rules for DMZ-Based Security Servers,” on page 84.
Security servers with PCoIP support run on Windows Server 2008 R2 and Windows Server 2012 R2
operating systems and take full advantage of the 64-bit architecture. This security server can also take
advantage of Intel processors that support AES New Instructions (AESNI) for highly optimized PCoIP
encryption and decryption performance.
For more information about Access Point virtual appliances, see Deploying and Configuring Access Point.
View Architecture Planning
74 VMware, Inc.