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
Disposable Disks for Paging and Temp Files
When you create a linked-clone pool, you can also optionally configure a separate, disposable virtual disk to
store the guest operating system's paging and temp files that are generated during user sessions. When the
virtual machine is powered off, the disposable disk is deleted. Using disposable disks can save storage space
by slowing the growth of linked clones and reducing the space used by powered off virtual machines.
Persistent Disks for Dedicated Desktops
When you create dedicated-assignment desktop pools, View Composer can also optionally create a separate
persistent virtual disk for each virtual desktop. The end user's Windows profile and application data are
saved on the persistent disk. When a linked clone is refreshed, recomposed, or rebalanced, the contents of
the persistent virtual disk are preserved. VMware recommends that you keep View Composer persistent
disks on a separate datastore. You can then back up the whole LUN that holds persistent disks.
Virtual SAN Datastores That Aggregate Local Storage Disks from a vSphere
Cluster
Virtual SAN virtualizes the local physical storage disks available on ESXi hosts into a single datastore
shared by all hosts in a vSphere cluster. A Virtual SAN datastore consists of solid-state drive (SSD) disks
and hard disk drives (HDDs), also called data disks. SSD disks are used for read caching and write
buffering. Data disks are used for persistent storage. This strategy provides high-performance storage with
automatic caching, so that you specify only one datastore when creating a desktop pool, and the various
components, such as virtual machine files, replicas, user data, and operating system files, are placed on the
appropriate SSD or data disks.
NOTE The Virtual SAN feature requires vSphere 5.5 Update 1 or a later release, and requires the
appropriate hardware. See the VMware Compatibility Guide.
When you use Virtual SAN, View defines virtual machine storage requirements, such as capacity,
performance, and availability, in the form of default storage policy profiles, which you can modify. Virtual
SAN lays out the virtual disk across the logical datastore to meet the specified requirements. Virtual SAN
also monitors and reports on the policy compliance during the life cycle of the virtual machine. If the policy
becomes noncompliant because of a host, disk, or network failure, or workload changes, Virtual SAN
reconfigures the data of the affected virtual machines and optimizes the use of resources across the cluster.
NOTE When you create a linked-clone desktop pool, a full clone is first made from the parent virtual
machine. From this full clone, or replica, linked clones are created. If you use a Virtual SAN datastore, by
default an extra copy of the replica and linked clones are created according to the availability policy.
Local Datastores for Floating, Stateless Desktops
Linked-clone desktops can be stored on local datastores, which are internal spare disks on ESXi hosts. Local
storage offers advantages such as inexpensive hardware, fast virtual-machine provisioning, high-
performance power operations, and simple management. However, using local storage limits the vSphere
infrastructure configuration options that are available to you. Using local storage is beneficial in certain
environments but not appropriate in others.
NOTE The limitations described in this section do not apply to Virtual SAN datastores, which also use local
storage disks but require specific hardware, as described in the preceding section about Virtual SAN.
Using local datastores is most likely to work well if the remote desktops in your environment are stateless.
For example, you might use local datastores if you deploy stateless kiosks or classroom and training
stations.
View Architecture Planning
36 VMware, Inc.