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
Architecture Design Elements and
Planning Guidelines 4
A typical Horizon View architecture design uses a pod strategy that consists of components that support up
to 10,000 virtual desktops using a vSphere 5.1 or later infrastructure. Pod definitions can vary, based on
hardware configuration, Horizon 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 Horizon View solution.
This chapter includes the following topics:
n
“Virtual Machine Requirements,” on page 33
n
“Horizon View ESX/ESXi Node,” on page 39
n
“Desktop Pools for Specific Types of Workers,” on page 40
n
“Desktop Virtual Machine Configuration,” on page 44
n
“vCenter Server and View Composer Virtual Machine Configuration,” on page 45
n
“View Connection Server Maximums and Virtual Machine Configuration,” on page 46
n
“View Transfer Server Virtual Machine Configuration and Storage,” on page 47
n
“vSphere Clusters,” on page 48
n
“Storage and Bandwidth Requirements,” on page 50
n
“Horizon View Building Blocks,” on page 57
n
“Horizon View Pods,” on page 57
n
“Advantages of Using Multiple vCenter Servers in a Pod,” on page 59
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 34
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.
VMware, Inc.
33