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
Figure 4‑1. Tiered Storage Example for a Large Desktop Pool
ESX
ESX
ESX
Parent 2
Parent 3
Parent 4
Parent 5
PARENT SSD, shared across all clusters
ESX cluster, consisting of 192
Intel cores and 2.3TB RAM,
connected via 10Gb FCoE
Replica SSD, one per pool/cluster
Linked clones
Parent 1
Pool datastores,
15K RAID1/0
32 datastores per pool
Replica 1
2000-desktop pool
staorage cross section
From an architectural perspective, View Composer creates desktop images that share a base image, which
can reduce storage requirements by 50 percent or more. You can further reduce storage requirements by
setting a refresh policy that periodically returns the desktop to its original state and reclaims space that is
used to track changes since the last refresh operation.
If you use View Composer with vSphere 5.1 or later virtual machine desktops, you can use the space
reclamation feature. With this feature, stale or deleted data within a guest operating system is automatically
reclaimed with a wipe and shrink process when the amount of unused disk space reaches a certain
threshold. Note that the space reclamation feature is not supported if you use a Virtual SAN datastore.
You can also reduce operating system disk space by using View Composer persistent disks or a shared file
server as the primary repository for the user profile and user documents. Because View Composer lets you
separate user data from the operating system, you might find that only the persistent disk needs to be
backed up or replicated, which further reduces storage requirements. For more information, see “Reducing
Storage Requirements with View Composer,” on page 35.
NOTE Decisions regarding dedicated storage components can best be made during a pilot phase. The main
consideration is I/Os per second (IOPS). You might experiment with a tiered-storage strategy or Virtual
SAN storage to maximize performance and cost savings.
For more information, see the best-practices guide called Storage Considerations for VMware View.
Chapter 4 Architecture Design Elements and Planning Guidelines for Remote Desktop Deployments
VMware, Inc. 59