5.2
Table Of Contents
- VMware Horizon View Architecture Planning
- Contents
- VMware Horizon View Architecture Planning
- Introduction to Horizon View
- Planning a Rich User Experience
- Feature Support Matrix
- Choosing a Display Protocol
- Using View Persona Management to Retain User Data and Settings
- Benefits of Using View Desktops in Local Mode
- Accessing USB Devices Connected to a Local Computer
- Printing from a View Desktop
- Streaming Multimedia to a View Desktop
- Using Single Sign-On for Logging In to a View Desktop
- Using Multiple Monitors with a View Desktop
- Managing Desktop Pools from a Central Location
- Architecture Design Elements and Planning Guidelines
- Virtual Machine Requirements
- Horizon View ESX/ESXi Node
- Desktop Pools for Specific Types of Workers
- Desktop Virtual Machine Configuration
- vCenter Server and View Composer Virtual Machine Configuration
- View Connection Server Maximums and Virtual Machine Configuration
- View Transfer Server Virtual Machine Configuration and Storage
- vSphere Clusters
- Storage and Bandwidth Requirements
- Horizon View Building Blocks
- Horizon View Pods
- Advantages of Using Multiple vCenter Servers in a Pod
- Planning for Security Features
- Understanding Client Connections
- Choosing a User Authentication Method
- Restricting View Desktop Access
- Using Group Policy Settings to Secure View Desktops
- Implementing Best Practices to Secure Client Systems
- Assigning Administrator Roles
- Preparing to Use a Security Server
- Understanding Horizon View Communications Protocols
- Overview of Steps to Setting Up a Horizon View Environment
- Index
Planning a Rich User Experience 2
VMware Horizon View provides the familiar, personalized desktop environment that end users expect. For
example, on some client systems, end users can access USB and other devices connected to their local computer,
send documents to any printer that their local computer can detect, authenticate with smart cards, and use
multiple display monitors.
Horizon View includes many features that you might want to make available to your end users. Before you
decide which features to use, you must understand the limitations and restrictions of each feature.
This chapter includes the following topics:
n
“Feature Support Matrix,” on page 17
n
“Choosing a Display Protocol,” on page 19
n
“Using View Persona Management to Retain User Data and Settings,” on page 21
n
“Benefits of Using View Desktops in Local Mode,” on page 23
n
“Accessing USB Devices Connected to a Local Computer,” on page 24
n
“Printing from a View Desktop,” on page 25
n
“Streaming Multimedia to a View Desktop,” on page 25
n
“Using Single Sign-On for Logging In to a View Desktop,” on page 26
n
“Using Multiple Monitors with a View Desktop,” on page 26
Feature Support Matrix
Many features, such as RSA SecurID authentication, location-based printing, and PCoIP protocol, are
supported on most client operating systems. You must also take into consideration whether the feature is
supported on the View desktop operating system.
When planning which display protocol and features to make available to your end users, use the following
information to determine which client operating systems and agent (View desktop) operating systems support
the feature.
The types and editions of the supported guest operating system depend on the Windows version.
Table 2-1. View Agent Operating System Support
Guest Operating System Version Edition Service Pack
Windows 8 64-bit and 32-bit Enterprise and
Professional
N/A
Windows 7 64-bit and 32-bit Enterprise and
Professional
None and SP1
VMware, Inc. 17