VMware View – Using Persona Management

KB ID 0000615 


Persona Management, is the VMware version of “Roaming Profiles” and “Redirected Folders” rolled into one. Though the redirected folders bit is a lot easier to set up and less problematic than the Microsoft Folder Redirection policy.

Its handy if you using floating pools but still want your users to have a persistent user interface. Having these files centrally makes them easier to backup, and the more your users can customise their desktops and settings the better their level of equipment husbandry.


Create a “Roaming Profile” Network share with the correct permissions

1. On a network accessible server, create a folder and set the SHARE permissions as follows;

Profile Folder Permissions

Share Permissions

Everyone = Read. Domain Users = Full Control.

Note: You may also want to DISABLE Caching on this folder.

2. Stop inheritable permissions from propagating to the folders and set the security permissions as follows;

Remove Inherited Permissions

Security / NTFS Permissions

Creator Owner (Subfolders and Files Only) = Full Control. Domain Users (This folder Only) = List Folder/Read Data and Create Folders/Append Data. System (This Folder, Subfolders and files) = Full Control. Creator Owner (Subfolders and Files Only) = Full Control. Everyone = No Permissions.

Note: I’m using domain users, you might have a different security group that you want to substitute.

User Rights for Profile Folder

3. Make sure that the machines that you will be using as view targets, have the View Persona Management option selected (this is selected by default).

View Agent Persona Management

Configure Windows 7 to be a VMware View Desktop

4. You need to get the administrative template for Persona Management. You will find it on your VMware Connection Server in the following location;

C:Program FilesVMwareVMware ViewServerextrasGroupPolicyFiles

Locate the ViewPM.adm file and copy it to a domain controller.

Persona Management ADM Template

5. Create a new group policy that is linked to the OU containing your View machines.

Persona Management GPO

6. Edit the policy > Expand Computer Configuration > Policies >Administrative Templates > Right Click > add/Remove Administrative Temple > Add in the ViewPM.adm template.

Import VewPM.adm

7. Navigate to;

Computer Configuration > Polices > Administrative Templates > Classic Administrative Templates > VMware View Agent Configuration > Persona Management

Persona Management Policy

8. In the roaming and Synchronisation Section > Manage user persona > Set to Enabled > Next Setting.

Enable Persona Management

9. Enable > Enter the shared folder you created earlier > Next Setting.

Persona Management Profile Location

10. Enabled (to remove local cached copies of the profile).

Delete Local Copies Persona Management

11. Enabled to roam the local folder > That’s all I’m going to configure in this branch of the policy.

Roaming Local settings

Persona Management Folder Redirection

12. Navigate to;

Computer Configuration > Polices > Administrative Templates > Classic Administrative Templates > VMware View Agent Configuration > Persona Management > Folder Redirection

Here you will find the folders that can be redirected to a central location.

Persona Management Redirected Folders

13. For example, here I’m redirecting the users “My Documents” folder.

Persona Management Redirect My Documents

14. And their “My Pictures” folder.

Persona Management Redirect My Pictures

15. Make sure you have a pool created, and your users are have an ‘entitlement’ to them. These machines will also HAVE TO be in the OU your policy is applying to.

VMware View Pool PM

Creating a ‘Manual Pool’ and Connecting a View Client

Deploying Linked Clone View Desktops

16. Now when your users connect to their View Desktops.

Connect to View Client

17. Their user profile will be persistent.

View Customise Desktop

18. Because their settings are stored in your profile shared folder.

Persona Management Profiles

Note: Persona Management will store the profile in username.domainname format. The reason there is a V2 on the end of it, denotes the profile is for Windows 7 or Vista. If users swap between these OS’s and any older Windows OS’s, then they will get a separate profile for those as well. If this is the case rely on the folder redirection rather than the profile.

Related Articles, References, Credits, or External Links


Author: Migrated

Share This Post On