5.0

n
Windows registry entries configured by user applications
Also, if you provision desktops with ThinApp applications, the ThinApp sandbox data can be stored in the
user profile and roamed with the user.
View Persona Management minimizes the time it takes to log in to and log off of desktops. Login and logoff
time can be a problem with Windows roaming profiles.
n
During login, View downloads only the files that Windows requires, such as user registry files. Other files
are copied to the local desktop when the user or an application opens them from the local profile folder.
n
View copies recent changes in the local profile to the remote repository, typically once every few minutes.
The default is every 10 minutes. You can specify how often to upload the local profile.
n
During logoff, only files that were updated since the last replication are copied to the remote repository.
Persona Management and Windows Roaming Profiles
When Persona Management is enabled, you cannot manage View users' personas by using the Windows
roaming profiles functions.
For example, if you log in to a desktop's guest operating system, navigate to the Advanced tab in the System
Properties dialog box, and change the User Profiles settings from Roaming profile to Local profile, View
Persona Management continues to synchronize the user's persona between the local desktop and the remote
persona repository.
However, you can specify files and folders within users' personas that are managed by Windows roaming
profiles functionality instead of View Persona Management. You use the Windows Roaming Profiles
Synchronization policy to specify these files and folders.
Configuring a View Persona Management Deployment
To configure View Persona Management, you set up a remote repository that stores user profiles, install View
Agent with the View Persona Management setup option on virtual machine desktops, add and configure
View Persona Management group policy settings, and deploy desktop pools.
Overview of Setting Up a View Persona Management Deployment
To set up a View desktop deployment with View Persona Management, you must perform several high-level
tasks.
This sequence is recommended, although you can perform these tasks in a different sequence. For example,
you can configure or reconfigure group policy settings in Active Directory after you deploy desktop pools.
1 Configure a remote repository to store user profiles.
You can configure a network share or use an existing Active Directory user profile path that you configured
for Windows roaming profiles.
2 Install View Agent with the View Persona Management setup option on the virtual machines that you
use to create desktop pools.
3 Add the View Persona Management Administrative (ADM) Template file to your Active Directory server
or the Local Computer Policy configuration on the parent virtual machine.
To configure View Persona Management for your whole View deployment, add the ADM Template file
to Active Directory.
To configure View Persona Management for one desktop pool, you can take these approaches:
n
Add the ADM Template file to the virtual machine that you use to create the pool.
VMware View Administration
176 VMware, Inc.