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 2‑3. Features Supported on Windows Operating Systems Where View Agent Is Installed (Continued)
Feature
Windows 7
Desktop
Windows 8.x
Desktop
Windows 10
Desktop
Windows
Server
2008/2012 R2
Desktop
Microsoft RDS-
Hosted Desktops
and Apps
Single sign-on X X X X X
Multiple monitors X X X X X
NOTE For information about which features are supported on the various types of client devices, see the
Horizon Client documentation at
https://www.vmware.com/support/viewclients/doc/viewclients_pubs.html.
In addition, several VMware partners offer thin and zero client devices for View deployments. The features
that are available for each thin or zero client device are determined by the vendor and model and the
configuration that an enterprise chooses to use. For information about the vendors and models for thin and
zero client devices, see the VMware Compatibility Guide, available on the VMware Web site.
Choosing a Display Protocol
A display protocol provides end users with a graphical interface to a remote desktop or application that
resides in the datacenter. Depending on which type of client device you have, you can choose between
PCoIP (PC-over-IP), which VMware provides, or Microsoft RDP (Remote Desktop Protocol).
You can set policies to control which protocol is used or to allow end users to choose the protocol when they
log in to a desktop.
NOTE For some types of clients, neither the PCoIP nor the RDP remote display protocol is used. For
example, if you use the HTML Access client, available with the HTML Access feature, the Blast protocol is
used, rather than PCoIP or RDP.
PCoIP
PCoIP (PC over IP) provides an optimized desktop experience for the delivery of a remote application or an
entire remote desktop environment, including applications, images, audio, and video content for a wide
range of users on the LAN or across the WAN. PCoIP can compensate for an increase in latency or a
reduction in bandwidth, to ensure that end users can remain productive regardless of network conditions.
PCoIP is supported as the display protocol for remote applications and for remote desktops that use virtual
machines, physical machines that contain Teradici host cards, or shared session desktops on an RDS host.
PCoIP Features
Key features of PCoIP include the following:
n
Users outside the corporate firewall can use this protocol with your company's virtual private network
(VPN), or users can make secure, encrypted connections to a security server or Access Point appliance
in the corporate DMZ.
n
Advanced Encryption Standard (AES) 128-bit encryption is supported and is turned on by default. You
can, however, change the encryption key cipher to AES-192 or AES-256.
n
Connections from all types of client devices.
n
Optimization controls for reducing bandwidth usage on the LAN and WAN.
n
32-bit color is supported for virtual displays.
n
ClearType fonts are supported.
Chapter 2 Planning a Rich User Experience
VMware, Inc. 21