5.2
Table Of Contents
- VMware Horizon View Architecture Planning
- Contents
- VMware Horizon View Architecture Planning
- Introduction to Horizon View
- Planning a Rich User Experience
- Feature Support Matrix
- Choosing a Display Protocol
- Using View Persona Management to Retain User Data and Settings
- Benefits of Using View Desktops in Local Mode
- Accessing USB Devices Connected to a Local Computer
- Printing from a View Desktop
- Streaming Multimedia to a View Desktop
- Using Single Sign-On for Logging In to a View Desktop
- Using Multiple Monitors with a View Desktop
- Managing Desktop Pools from a Central Location
- Architecture Design Elements and Planning Guidelines
- Virtual Machine Requirements
- Horizon View ESX/ESXi Node
- Desktop Pools for Specific Types of Workers
- Desktop Virtual Machine Configuration
- vCenter Server and View Composer Virtual Machine Configuration
- View Connection Server Maximums and Virtual Machine Configuration
- View Transfer Server Virtual Machine Configuration and Storage
- vSphere Clusters
- Storage and Bandwidth Requirements
- Horizon View Building Blocks
- Horizon View Pods
- Advantages of Using Multiple vCenter Servers in a Pod
- Planning for Security Features
- Understanding Client Connections
- Choosing a User Authentication Method
- Restricting View Desktop Access
- Using Group Policy Settings to Secure View Desktops
- Implementing Best Practices to Secure Client Systems
- Assigning Administrator Roles
- Preparing to Use a Security Server
- Understanding Horizon View Communications Protocols
- Overview of Steps to Setting Up a Horizon View Environment
- Index
n
Use vStorage thin provisioning so that at first, each desktop uses only as much storage space as the disk
needs for its initial operation.
n
For power users and knowledge workers who must install their own applications, which adds data to the
operating system disk, create full virtual machine desktops.
n
If knowledge workers do not require user-installed applications except for temporary use, you can create
View Composer linked-clone desktops. The desktop images share the same base image and use less storage
space than full virtual machines.
n
If you use View Composer with vSphere 5.1 or later virtual desktops, enable the space reclamation feature
for vCenter Server and for the desktop pool. With the space reclamation feature, stale or deleted data
within a guest operating system is automatically reclaimed with a wipe and shrink process.
n
If you use View Composer linked-clone desktops, implement View Persona Management, roaming
profiles, or another profile management solution.
Configure persistent disks so that you can refresh and recompose the linked-clone OS disks while keeping
a copy of the each user profile on the persistent disks.
Pools for Mobile Users
These users can check out a View desktop and run it locally on their laptop or desktop even without a network
connection.
View Client with Local Mode provides benefits for both end users and IT administrators. For administrators,
local mode allows View security policies to extend to laptops that have previously been unmanaged.
Administrators can retain tight control over the applications that run on the View desktop and can centrally
manage the desktop just as they do remote View desktops. With local mode, all the benefits of
Horizon View can also extend to remote or branch offices that have slow or unreliable networks.
For end users, benefits include the flexibility of continuing to use their own computers online or offline. The
View desktop is automatically encrypted and can easily be synchronized with an image in the datacenter for
purposes of disaster recovery.
General Recommendations
Local mode users might need to access their desktop applications and data from their laptop when no network
connection is available. In addition, they might need this data to be regularly and automatically backed up to
the datacenter in the event that the laptop is ever lost, damaged, or stolen. To provide these capabilities, you
can use the following pool settings.
n
When creating a virtual machine to base the pool on, configure the minimum amount of RAM and virtual
CPUs required by the guest operating system. Desktops that run in local mode adjust the amount of
memory and processing power they use based on that available from the client computer.
n
Create an automated pool so that desktops can be created when the pool is created or can be generated
on demand based on pool usage.
n
Use dedicated assignment because local mode users need to log in to the same desktop every time.
n
Create View Composer linked-clone desktops so that desktops share the same base image and use less
storage space in the datacenter than full virtual machines.
n
If you want the provisioning process to generate a unique local computer SID and GUID for each linked
clone in the pool, select a Sysprep customization specification when you create the pool. Sysprep creates
new SIDs and GUIDs during the initial provisioning and after recompose operations. Because you are not
likely to recompose local mode pools, the SIDs and GUIDs are not likely to change.
n
Include in the pool only desktops that are intended to be used in local mode. Local mode virtual machines
can be placed on datastores with lower IOPS requirements than storage intended to support large numbers
of remote View desktops.
VMware Horizon View Architecture Planning
42 VMware, Inc.