5.0

n
(Optional) To use View Persona Management with manual desktop pools, select desktop sources on which
View Agent with the View Persona Management option is installed.
NOTE After you deploy View Persona Management on your View desktops, if you remove the View Persona
Management setup option on the desktops, or uninstall View Agent altogether, the local user profiles are
removed from the desktops of users who are not currently logged in. For users who are currently logged in,
the user profiles are downloaded from the remote profile repository during the uninstall process.
Best Practices for Configuring a View Persona Management
Deployment
You should follow best practices for configuring View Persona Management to enhance your users' desktop
experience, improve desktop performance, and ensure that View Persona Management operates efficiently
with other View features.
Determining Whether to Remove Local User Profiles at Logoff
By default, View Persona Management does not delete user profiles from the local desktops when users log
off. The Remove local persona at log off policy is disabled. In many cases, the default setting is a best practice
because it reduces I/O operations and avoids redundant behavior.
For example, keep this policy disabled if you deploy floating-assignment pools and either refresh or delete the
desktops on logoff. The local profile is deleted when the virtual machine is refreshed or deleted. In a floating-
assignment, automated pool, full virtual machines can be deleted after logoff. In a floating-assignment, linked-
clone pool, the clones can be refreshed or deleted on logoff.
If you deploy dedicated-assignment pools, you can keep the policy disabled because users return to the same
desktops at each session. With the policy disabled, when a user logs in, View Persona Management does not
have to download files that are present in the local profile. If you configure dedicated-assignment, linked-clone
pools with persistent disks, keep the policy disabled to avoid deleting user data from the persistent disks.
In some cases, you might want to enable the Remove local persona at log off policy.
Handling Deployments That Include View Persona Management and Windows
Roaming Profiles
In deployments in which Windows roaming profiles are configured, and users access View desktops with
View Persona Management and standard desktops with Windows roaming profiles, the best practice is to use
different profiles for the two desktop environments. If a View desktop and the client computer from which the
desktop is launched are in the same domain, and you use an Active Directory GPO to configure both Windows
roaming profiles and View Persona Management, enable the Persona repository location policy and select
Override Active Directory user profile path if it is configured.
This approach prevents Windows roaming profiles from overwriting a View Persona Management profile
when the user logs off from the client computer.
If users intend to share data between existing Windows roaming profiles and View Persona Management
profiles, you can configure Windows folder redirection.
Configuring Paths for Redirected Folders
When you use the Folder Redirection group policy setting, configure the folder path to include %username%,
but make sure that the last subfolder in the path uses the name of the redirected folder, such as My Videos. The
last folder in the path is displayed as the folder name on the user's desktop.
For example, if you configure a path such as \\myserver\videos\%username%\My Videos, the folder name that
appears on the user's desktop is My Videos.
Chapter 9 Configuring User Profiles with View Persona Management
VMware, Inc. 183