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
Architecture Design Elements and
Planning Guidelines for Remote
Desktop Deployments 4
A typical View architecture design uses a pod strategy that consists of components that support up to 10,000
remote desktops using a vSphere 5.1 or later infrastructure. Pod definitions can vary, based on hardware
configuration, View and vSphere software versions used, and other environment-specific design factors.
The examples in this document illustrate a scalable design that you can adapt to your enterprise
environment and special requirements. This chapter includes key details about requirements for memory,
CPU, storage capacity, network components, and hardware to give IT architects and planners a practical
understanding of what is involved in deploying a View solution.
IMPORTANT This chapter does not cover the following topics:
Architecture design
for hosted
applications
A View pod can support up to 200 farms of Microsoft RDS hosts, and each farm can contain up to
200 RDS hosts. Supported operating systems for RDS hosts include Windows Server 2008 R2,
Windows Server 2012, and Windows Server 2012 R2. For more information, see the Setting Up
Desktop and Application Pools in View. If you plan to use virtual machines for RDS hosts, also see
“RDS Host Virtual Machine Configuration,” on page 53.
Architecture design
for View Agent
Direct Connect
Plugin
With this plugin running on a remote virtual machine desktop, the client can connect directly to
the virtual machine. All the remote desktop features, including PCoIP, HTML Access, RDP, USB
redirection, and session management work in the same way, as if the user had connected through
View Connection Server. For more information, see View Agent Direct-Connection Plugin
Administration.
This chapter includes the following topics:
n
“Virtual Machine Requirements for Remote Desktops,” on page 44
n
“View ESXi Node,” on page 48
n
“Desktop Pools for Specific Types of Workers,” on page 49
n
“Desktop Virtual Machine Configuration,” on page 52
n
“RDS Host Virtual Machine Configuration,” on page 53
n
“vCenter Server and View Composer Virtual Machine Configuration,” on page 54
n
“View Connection Server Maximums and Virtual Machine Configuration,” on page 55
n
“vSphere Clusters,” on page 57
n
“Storage and Bandwidth Requirements,” on page 59
n
“View Building Blocks,” on page 67
n
“View Pods,” on page 67
n
“Advantages of Using Multiple vCenter Servers in a Pod,” on page 70
VMware, Inc.
43