Architecture Planning
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 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 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
Reducing and Managing Storage Requirements
Deploying desktops on virtual machines that are managed by vCenter Server provides all the storage
efficiencies that were previously available only for virtualized servers. Using View Composer increases the
storage savings because all virtual machines in a pool share a virtual disk with a base image.
n
Managing Storage with vSphere on page 31
vSphere lets you virtualize disk volumes and file systems so that you can manage and configure
storage without having to consider where the data is physically stored.
n
Using Virtual SAN for High-Performance Storage and Policy-Based Management on page 32
VMware Virtual SAN is a software-defined storage tier, available with vSphere 5.5 Update 1 or a later
release, that virtualizes the local physical storage disks available on a cluster of vSphere hosts. 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 solid-state
drive (SSD) disks or direct-attached hard disks (HDDs).
n
Using Virtual Volumes for Virtual-Machine-Centric Storage and Policy-Based Management on
page 34
With Virtual Volumes (VVols), available with vSphere 6.0 or a later release, an individual virtual
machine, not the datastore, becomes a unit of storage management. The storage hardware gains
control over virtual disk content, layout, and management.
n
Reducing Storage Requirements with View Composer on page 35
Because View Composer creates desktop images that share virtual disks with a base image, you can
reduce the required storage capacity by 50 to 90 percent.
Managing Storage with vSphere
vSphere lets you virtualize disk volumes and file systems so that you can manage and configure storage
without having to consider where the data is physically stored.
Fibre Channel SAN arrays, iSCSI SAN arrays, and NAS arrays are widely used storage technologies
supported by vSphere to meet different datacenter storage needs. The storage arrays are connected to and
shared between groups of servers through storage area networks. This arrangement allows aggregation of
the storage resources and provides more flexibility in provisioning them to virtual machines.
Compatible vSphere 5.0 and 5.1 or Later Features
With vSphere 5.0 or a later release, you can use the following features:
n
With the View storage accelerator feature, you can configure ESXi hosts to cache virtual machine disk
data.
Using this content-based read cache (CBRC) can reduce IOPS and improve performance during boot
storms, when many machines start up and run anti-virus scans at the same time. Instead of reading the
entire OS from the storage system over and over, a host can read common data blocks from cache.
n
If remote desktops use the space-efficient disk format available with vSphere 5.1 and later, stale or
deleted data within a guest operating system is automatically reclaimed with a wipe and shrink
process.
n
You can deploy a desktop pool on a cluster that contains up to 32 ESXi hosts, with certain restrictions.
Replica disks must be stored on VMFS5 or later datastores or NFS datastores. If you store replicas on a
VMFS version earlier than VMFS5, a cluster can have at most eight hosts. OS disks and persistent disks
can be stored on NFS or VMFS datastores.
Chapter 3 Managing Desktop and Application Pools from a Central Location
VMware, Inc. 31