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
Table 4-11. Example of a VMware View Pod (Continued)
Item Number
Modular networking switch 1
Load-balancing module 1
VPN for WAN 1 (optional)
The network core load balances incoming requests across View Connection Server instances. Support for a
redundancy and failover mechanism, usually at the network level, prevents the load balancer from becoming
a single point of failure. For example, the Virtual Router Redundancy Protocol (VRRP) communicates with the
load balancer to add redundancy and failover capability.
If a View Connection Server instance fails or becomes unresponsive during an active session, users do not lose
data. Desktop states are preserved in the virtual machine desktop so that users can connect to a different View
Connection Server instance and their desktop session resumes from where it was when the failure occurred.
Figure 4-2 shows how all the components can be integrated into one manageable entity.
Figure 4-2. Pod Diagram for 10,000 View Desktops
switched networks
VMware View
Connection Servers
VMware View
building blocks
load balancing
network core
Each switched network connects to each View Connection Server
VMware View Architecture Planning
50 VMware, Inc.