You can use View Persona Management with View desktops and with physical computers and virtual machines that are not managed by VMware Horizon View. View Persona Management retains changes that users make to their profiles. User profiles comprise a variety of user-generated information.

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.

Application data and settings. For example, these settings allow applications to remember toolbar positions and preferences.

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.

View Persona Management minimizes the time it takes to log on to and off of desktops.

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.

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.

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.

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:

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.

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.

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.

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.


My Documents

Save Games


My Music



My Pictures

Start Menu


My Videos

Startup Items


Network Neighborhood



Printer Neighborhood

Temporary Internet Files


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:

Share and manage profiles across standalone systems and View desktops.

Migrate user profiles from physical systems to View desktops.

Perform a staged migration from physical systems to View desktops.

Support up-to-date profiles when users go offline.

View Persona Management has the following limitations and restrictions:

You must have a Horizon View license that includes the View Personal Management component.

View Persona Management requires a CIFS (Common Internet File System) share.

You cannot use View Persona Management with desktops that run in local mode.

A user cannot access the same profile if the user switches between desktops that have v1 user profiles and v2 user profiles. However, redirected folders can be shared between v1 and v2 profiles. Windows XP uses v1 profiles. Windows Vista, Windows 7, and Windows 8 use v2 profiles.