7.0
Table Of Contents
- View Architecture Planning
- Contents
- View Architecture Planning
- Introduction to View
- Planning a Rich User Experience
- Feature Support Matrix for Horizon Agent
- Choosing a Display Protocol
- Using Hosted Applications
- Using View Persona Management to Retain User Data and Settings
- Using USB Devices with Remote Desktops and Applications
- 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
- Monitors and Screen Resolution
- Managing Desktop and Application Pools from a Central Location
- Advantages of Desktop Pools
- Advantages of Application Pools
- Reducing and Managing Storage Requirements
- Application Provisioning
- Deploying Individual Applications Using an RDS Host
- Deploying Applications and System Updates with View Composer
- Deploying Applications and System Updates with Instant Clones
- Managing VMware ThinApp Applications in View Administrator
- Deploying and Managing Applications Using App Volumes
- Using Existing Processes or VMware Mirage for Application Provisioning
- Using Active Directory GPOs to Manage Users and Desktops
- 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
- Using Smart Policies
- 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
You can store instant clones on traditional, spinning media-backed datastores. These disks provide lower
performance, but are less expensive and provide higher storage capacity, which makes them suited for
storing the many instant clones in a large pool. Tiered storage configurations can be used to cost-effectively
handle intensive I/O scenarios such as simultaneous running scheduled antivirus scans.
If you use Virtual SAN datastores, you cannot manually select different datastores for replicas and instant
clones. Because Virtual SAN automatically places objects on the appropriate type of disk and caches all I/O
operations, there is no need to use replica tiering for Virtual SAN data stores. Instant clone pools are
supported on Virtual SAN data stores. Instant clone pools are not supported on ordinary local storage disks.
Differences between Instant Clones and View Composer Linked Clones
Since instant clones can be created significantly faster than linked clones, the following features of linked
clones are no longer needed when you provision a pool of instant clones:
n
Instant clone pools do not support configuration of a separate, disposable virtual disk for storing the
guest operating system's paging and temp files. Each time a user logs out of an instant clone desktop,
View automatically deletes the clone and provisions and powers on another instant clone based on the
latest OS image available for the pool. Any guest operating systems paging and temp files are
automatically deleted during the logoff operation.
n
Instant clone pools do not support the creation of a separate persistent virtual disk for each virtual
desktop. Instead, you can store the end user's Windows profile and application data on App Volumes'
user writable disks. An end user's user writable disk is attached to an instant clone desktop when the
end user logs in. In addition, user writable disks can be used to persist user-installed applications.
n
Due to short-lived nature of instant clone desktops, the space-efficient disk format (SE sparse), with its
wipe and shrink process, is not needed.
Application Provisioning
With View, you have several options regarding application provisioning: You can use traditional
application provisioning techniques, you can provide remote applications rather than a remote desktop, you
can distribute application packages created with VMware ThinApp, you can deploy applications as part of a
View Composer or instant clone base image, or you can attach applications using App Volumes.
n
Deploying Individual Applications Using an RDS Host on page 44
You might choose to provide end users with remote applications rather than remote desktops.
Individual remote applications might be easier to navigate on a small mobile device.
n
Deploying Applications and System Updates with View Composer on page 44
Because linked-clone desktop pools share a base image, you can quickly deploy updates and patches
by updating the parent virtual machine.
n
Deploying Applications and System Updates with Instant Clones on page 45
Because instant clone desktop pools share a base image, you can quickly deploy updates and patches
by updating the parent virtual machine.
n
Managing VMware ThinApp Applications in View Administrator on page 45
VMware ThinApp™ lets you package an application into a single file that runs in a virtualized
application sandbox. This strategy results in flexible, conflict-free application provisioning.
n
Deploying and Managing Applications Using App Volumes on page 46
VMware App Volumes offers an alternative way to manage applications by virtualizing applications
above the operating system. By using this strategy, applications, data files, settings, middleware, and
configurations act as separate, layered containers.
Chapter 3 Managing Desktop and Application Pools from a Central Location
VMware, Inc. 43