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
Virtual Machine Requirements for Remote Desktops
When you plan the specifications for remote desktops, the choices that you make regarding RAM, CPU, and
disk space have a significant effect on your choices for server and storage hardware and expenditures.
n
Planning Based on Types of Workers on page 44
For many configuration elements, including RAM, CPU, and storage sizing, requirements depend
largely on the type of worker who uses the virtual desktop and on the applications that must be
installed.
n
Estimating Memory Requirements for Virtual Machine Desktops on page 45
RAM costs more for servers than it does for PCs. Because the cost of RAM is a high percentage of
overall server hardware costs and total storage capacity needed, determining the correct memory
allocation is crucial to planning your desktop deployment.
n
Estimating CPU Requirements for Virtual Machine Desktops on page 47
When estimating CPU, you must gather information about the average CPU utilization for various
types of workers in your enterprise.
n
Choosing the Appropriate System Disk Size on page 48
When allocating disk space, provide only enough space for the operating system, applications, and
additional content that users might install or generate. Usually this amount is smaller than the size of
the disk that is included on a physical PC.
Planning Based on Types of Workers
For many configuration elements, including RAM, CPU, and storage sizing, requirements depend largely on
the type of worker who uses the virtual desktop and on the applications that must be installed.
For architecture planning, workers can be categorized into several types.
Task workers
Task workers and administrative workers perform repetitive tasks within a
small set of applications, usually at a stationary computer. The applications
are usually not as CPU- and memory-intensive as the applications used by
knowledge workers. Task workers who work specific shifts might all log in
to their virtual desktops at the same time. Task workers include call center
analysts, retail employees, warehouse workers, and so on.
Knowledge workers
Knowledge workers' daily tasks include accessing the Internet, using email,
and creating complex documents, presentations, and spreadsheets.
Knowledge workers include accountants, sales managers, marketing
research analysts, and so on.
Power users
Power users include application developers and people who use graphics-
intensive applications.
Kiosk users
These users need to share a desktop that is located in a public place.
Examples of kiosk users include students using a shared computer in a
classroom, nurses at nursing stations, and computers used for job placement
and recruiting. These desktops require automatic login. Authentication can
be done through certain applications if necessary.
View Architecture Planning
44 VMware, Inc.