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
Table 4‑11. Virtual Machine Desktop Cluster Example (Continued)
Item Example
Non-SSD storage 32 Non-SSD datastores for clones (450 GB per datastore)
Cluster type DRS (Distributed Resource Scheduler)/HA
NOTE With vSphere 5.1 and later, if you use View Composer and store replica disks on NFS or VMFS5
datastores, the cluster can contain up to 32 ESXi hosts. With vSphere 5.5 Update 1 and later, if you use
Virtual SAN datastores, and the cluster can also contain up to 32 servers. For more information, see the
chapter about creating desktop pools, in the Setting Up Desktop and Application Pools in View.
Networking requirements depend on the type of server, the number of network adapters, and the way in
which VMotion is configured.
Storage and Bandwidth Requirements
Several considerations go into planning for shared storage of virtual machine desktops, planning for storage
bandwidth requirements with regard to I/O storms, and planning network bandwidth needs.
Details about the storage and networking components used in a test setup at VMware are provided in these
related topics.
n
Shared Storage Example on page 57
For a View 5.2 test environment, View Composer replica virtual machines were placed on high-read-
performance solid-state drives (SSD), which support tens of thousands of I/Os per second (IOPS).
Linked clones were placed on traditional, lower-performance spinning media-backed datastores,
which are less expensive and provide higher storage capacity.
n
Storage Bandwidth Considerations on page 60
In a View environment, logon storms are the main consideration when determining bandwidth
requirements.
n
Network Bandwidth Considerations on page 60
Certain virtual and physical networking components are required to accommodate a typical
workload.
n
View Composer Performance Test Results on page 62
These test results describe a View 5.2 setup with 10,000-desktops, in which one vCenter Server 5.1
instance managed 5 pools of 2,000 virtual machine desktops each. Only one maintenance period was
required for provisioning a new pool or for recomposing, refreshing, or rebalancing an existing pool of
2,000 virtual machines. A logon storm of 10,000 users was also tested.
n
WAN Support and PCoIP on page 63
For wide-area networks (WANs), you must consider bandwidth constraints and latency issues. The
PCoIP display protocol provided by VMware adapts to varying latency and bandwidth conditions.
Shared Storage Example
For a View 5.2 test environment, View Composer replica virtual machines were placed on high-read-
performance solid-state drives (SSD), which support tens of thousands of I/Os per second (IOPS). Linked
clones were placed on traditional, lower-performance spinning media-backed datastores, which are less
expensive and provide higher storage capacity.
Storage design considerations are one of the most important elements of a successful View architecture. The
decision that has the greatest architectural impact is whether to use View Composer desktops, which use
linked-clone technology. The ESXi binaries, virtual machine swap files, and View Composer replicas of
parent virtual machines are stored on the shared storage system.
Chapter 4 Architecture Design Elements and Planning Guidelines for Remote Desktop Deployments
VMware, Inc. 57