5.0
Table Of Contents
- VMware View Architecture Planning
- Contents
- VMware View Architecture Planning
- Introduction to VMware 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
- VMware View ESX/ESXi Node
- Desktop Pools for Specific Types of Workers
- Desktop Virtual Machine Configuration
- vCenter and View Composer Virtual Machine Configuration and Desktop Pool Maximums
- View Connection Server Maximums and Virtual Machine Configuration
- View Transfer Server Virtual Machine Configuration and Storage
- vSphere Clusters
- VMware View Building Blocks
- VMware View 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 VMware View Communications Protocols
- Overview of Steps to Setting Up a VMware View Environment
- Index
n
You can copy and paste text and system objects such as folders and files between the local system and the
View desktop.
n
RDP supports 32-bit color.
n
RDP supports 128-bit encryption.
n
You can use this protocol for making secure, encrypted connections to a View security server in the
corporate DMZ.
Using View Persona Management to Retain User Data and Settings
View Persona Management retains changes that users make to their profiles. User profiles comprise a variety
of user-generated information.
n
User-specific data and desktop settings, which allow the desktop appearance to be the same regard less
of which desktop a user logs in to.
n
Application data and settings. For example, these settings allow applications to remember toolbar
positions and preferences.
n
Windows registry entries configured by user applications.
To facilitate these abilities, View Persona Management requires storage on a CIFS share equal or greater than
the size of the user's local profile.
Minimizing Logon and Logoff Times
View Persona Management minimizes the time it takes to log on to and off of desktops.
n
View takes recent changes in the profile on the View desktop and copies them to the remote repository at
regular intervals. The default is every 10 minutes. In contrast, Windows roaming profiles wait until logoff
time and copy all changes to the server at logoff.
n
During logon, 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.
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. 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 or 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.
VMware View Architecture Planning
18 VMware, Inc.