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
During logon, by default, Horizon View downloads only the files that Windows requires, such as user
registry files. Other files are copied to the View desktop when the user or an application opens them from
the profile folder in the View desktop.
You can configure Horizon View to download specified files when the user logs in and download other
files in the background.
n
With View Persona Management, during logoff, only files that were updated since the last replication are
copied to the remote repository.
With View Persona Management, you can avoid making any changes to Active Directory in order to have a
managed profile. To configure Persona Management, you specify a central repository, without changing the
user's properties in Active Directory. With this central repository, you can manage a user's profile in one
environment without affecting the physical machines that users might also log on to.
With View Persona Management, if you provision desktops with VMware ThinApp applications, the ThinApp
sandbox data can also be stored in the user profile. This data can roam with the user but does not significantly
affect logon times. This strategy provides better protection against data loss or corruption.
Configuration Options
You can configure View personas at several levels: a single View desktop, a desktop pool, an OU, or all View
desktops in your deployment. You can also use a standalone version of View Persona Management on physical
computers and virtual machines that are not managed by View.
By setting group policies (GPOs), you have granular control of the files and folders to include in a persona:
n
Specify whether to include the local settings folder. For Windows 7, Windows 8, and Windows Vista, this
policy affects the AppData\Local folder. For Windows XP, this policy affects the Local Settings folder.
n
Specify which files and folders to load at login time. For example: Application
Data\Microsoft\Certificates. Within a folder, you can also specify files to exclude.
n
Specify which files and folders to download in the background after a user logs in to the desktop. Within
a folder, you can also specify files to exclude.
n
Specify which files and folders within a user's persona to manage with Windows roaming profiles
functionality instead of View Persona Management. Within a folder, you can also specify files to exclude.
As with Windows roaming profiles, you can configure folder redirection. You can redirect the following folders
to a network share.
Contacts My Documents Save Games
Cookies My Music Searches
Desktop My Pictures Start Menu
Downloads My Videos Startup Items
Favorites Network Neighborhood Templates
History Printer Neighborhood Temporary Internet Files
Links Recent Items
To configure a remote repository to store personas, you can use either a network share or an existing Active
Directory user profile path that you configured for Windows roaming profiles. The network share can be a
folder on a server, a network-attached storage (NAS) device, or a network server. To support a large View
deployment, you can configure separate repositories for different desktop pools.
With Horizon View 5.1 and later, you can install a standalone version of View Persona Management on physical
computers and virtual machines that are not managed by View, allowing you to accomplish these goals:
n
Share and manage profiles across standalone systems and View desktops.
VMware Horizon View Architecture Planning
22 VMware, Inc.