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
View Building Blocks
A building block consists of physical servers, a vSphere infrastructure, View servers, shared storage, and
virtual machine desktops for end users. You can include up to five building blocks in a View pod.
Table 4‑12. Example of a LAN-Based View Building Block for 2,000 Virtual Machine Desktops
Item Example
vSphere clusters 1 or more
80-port network switch 1
Shared storage system 1
vCenter Server with View Composer on the same host 1 (can be run in the block itself)
Database MS SQL Server or Oracle database server (can be run in the
block itself)
VLANs 3 (a 1Gbit Ethernet network for each: management
network, storage network, and VMotion network)
With vSphere 4.1 and later versions, each vCenter Server can support up to 10,000 virtual machines. This
support enables you to have building blocks that contain more than 2,000 virtual machine desktops.
However, the actual block size is also subject to other View-specific limitations.
If you have only one building block in a pod, use two View Connection Server instances for redundancy.
View Pods
A pod is a unit of organization determined by View scalability limits.
Pod Example Using Five Building Blocks
A traditional View pod integrates five 2,000-user building blocks that you can manage as one entity.
Table 4‑13. Example of a LAN-Based View Pod Constructed of 5 Building Blocks
Item Number
Building blocks for a View pod 5
vCenter Server and View Composer 5 (1 virtual machine that hosts both in each building block)
Database server 5 (1 standalone database server in each building block) MS
SQL Server or Oracle database server
View Connection Servers 7 (5 for connections from inside the corporate network and
2 for connections from outside)
vLANs See Table 4-12.
10Gb Ethernet module 1
Modular networking switch 1
With vSphere 4.1 and later versions, each vCenter Server can support up to 10,000 virtual machines. This
support enables you to have building blocks that contain more than 2,000 virtual machine desktops.
However, the actual block size is also subject to other View-specific limitations.
For both examples described here, a network core can load balance incoming requests across View
Connection Server instances. Support for a redundancy and failover mechanism, usually at the network
level, can prevent the load balancer from becoming a single point of failure. For example, the Virtual Router
Redundancy Protocol (VRRP) can communicate with a load balancer to add redundancy and failover
capability.
Chapter 4 Architecture Design Elements and Planning Guidelines for Remote Desktop Deployments
VMware, Inc. 65