5.0
Table Of Contents
- VMware View Architecture Planning
- Contents
- VMware View Architecture Planning
- Introduction to VMware 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
- VMware View ESX/ESXi Node
- Desktop Pools for Specific Types of Workers
- Desktop Virtual Machine Configuration
- vCenter and View Composer Virtual Machine Configuration and Desktop Pool Maximums
- View Connection Server Maximums and Virtual Machine Configuration
- View Transfer Server Virtual Machine Configuration and Storage
- vSphere Clusters
- VMware View Building Blocks
- VMware View 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 VMware View Communications Protocols
- Overview of Steps to Setting Up a VMware View Environment
- Index
Architecture Design Elements and
Planning Guidelines 4
A typical VMware View architecture design uses a pod strategy that consists of components that support up
to 10,000 virtual desktops using a vSphere 4.1 or later infrastructure. Pod definitions can vary, based on
hardware configuration, View and vSphere software versions used, and other environment-specific design
factors.
This architecture provides a standard, 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 VMware View solution.
This chapter includes the following topics:
n
“Virtual Machine Requirements,” on page 31
n
“VMware View ESX/ESXi Node,” on page 36
n
“Desktop Pools for Specific Types of Workers,” on page 37
n
“Desktop Virtual Machine Configuration,” on page 41
n
“vCenter and View Composer Virtual Machine Configuration and Desktop Pool Maximums,” on
page 42
n
“View Connection Server Maximums and Virtual Machine Configuration,” on page 43
n
“View Transfer Server Virtual Machine Configuration and Storage,” on page 44
n
“vSphere Clusters,” on page 44
n
“VMware View Building Blocks,” on page 45
n
“VMware View Pod,” on page 49
Virtual Machine Requirements
When you plan the specifications for View 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 32
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 Desktops on page 33
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.
VMware, Inc.
31