6.0
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
- 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
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. Pod Diagram for 10,000 Virtual Machine Desktops
switched
networks
View Connection
Servers
View building
blocks
load balancing
network core
Each switched network connects to each View Connection Server
Pod Example Using One vCenter Server
In the previous section, the View pod consisted of multiple building blocks. Each building block supported
2,000 virtual machines with a single vCenter Server. VMware has received many requests from both
customers and partners to use a single vCenter Server to manage a View pod. This request arises from the
fact that a single instance of vCenter Server can support 10,000 virtual machines. With View 5.2 and later,
customers have the ability to use a single vCenter Server to manage a 10,000-desktop environment. This
topic illustrates an architecture based on using a single vCenter Serverto manage 10,000 desktops
Although using one vCenter Server and one View Composer for 10,000 desktops is possible, doing so
creates a situation where there is a single point of failure. The loss of that single vCenter Server renders the
entire desktop deployment unavailable for power, provisioning, and refit operations. For this reason, choose
a deployment architecture that meets your requirements for overall component resiliency.
For this example, a 10,000-user pod consists of physical servers, a vSphere infrastructure, View servers,
shared storage, and 5 clusters of 2,000 virtual desktops per cluster.
Table 4‑14. Example of a LAN-Based View Pod with One vCenter Server
Item Example
vSphere clusters 6 (5 clusters with one linked-clone pool per cluster, and 1
infrastructure cluster)
vCenter Server 1
View Composer 1 (standalone)
Database server 1 (standalone) MS SQL Server or Oracle database server
Active Directory server 1 or 2
View Connection Server instances 5
Security servers 5
vLANs 8 (5 for the desktop pool clusters, and 1 each for
management, VMotion, and the infrastructure cluster)
View Architecture Planning
66 VMware, Inc.