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
Figure 5-2. Load-Balanced Security Servers in a DMZ
vCenter
Management Server
Microsoft
Active Directory
View
Connection
Servers
load balancing
View
Security
Servers
DMZ
external network
remote
View Client
ESX hosts running
Virtual Desktop
virtual machines
When remote users connect to a security server, they must successfully authenticate before they can access
View desktops. With appropriate firewall rules on both sides of the DMZ, this topology is suitable for accessing
View desktops from client devices located on the Internet.
You can connect multiple security servers to each instance of View Connection Server. You can also combine
a DMZ deployment with a standard deployment to offer access for internal users and external users.
The topology illustrated in Figure 5-3 shows an environment where four instances of View Connection Server
act as one group. The instances in the internal network are dedicated to users of the internal network, and the
instances in the external network are dedicated to users of the external network. If the View Connection Server
instances paired with the security servers are enabled for RSA SecurID authentication, all external network
users are required to authenticate by using RSA SecurID tokens.
VMware Horizon View Architecture Planning
70 VMware, Inc.