Troubleshooting Persona Management (2008457)
This article provides information on methods to configure View Persona Management correctly.
To enable and use View Persona Management, you must have a View Premier license. For more information, see the VMware End User Licensing Agreement (EULA).
Persona Management Policies
- The Parent virtual machine, but this requires a Recompose of the Pool(s).
- Active Directory, but need to do a proper linking of GPO and OU to properly restrict/assign the policy to the intended desktops and also need to enable loopback. For more information, see the Active Directory Group Policy Example section in the VMware View Administration Guide.
- Run rsop.msc. Fore more information, see the Microsoft Knowledge Base article 312321.
Note: The preceding link was correct as of February 27, 2015. If you find the link is broken, provide a feedback and a VMware employee will update the link.
- Navigate to:
- Windows Vista/2008 – username/Computer Configuration/Administrative Templates/Classic Administrative Templates (ADM)/VMware View Agent Configuration/Persona Management
- Windows XP/2003 – username/Computer Configuration/Administrative Templates/VMware View Agent Configuration/Persona Management
- Verify that the expected settings appear in and under that location.
- If they do not, run the gpupdate /force command then log out and in to the desktop to force a policies reload.
This interval is visible from Active Directory and from the Virtual Desktop if it has already loaded the Persona Management Active Directory policies.
Persona Management Logging
- From the View desktop, open the UNC of the repository (for example, \\server\VPRepository\profiles). If at least one profile sync is performed, then you should find a folder similar to \\server\VPRepository\profiles\username.DomainName\.
- If Persona Management works for some desktops on the pool but not for others, verify they all belong to the same OU and that it is linked to the correct GPO in Active Directory.
- Until the policies are visible from within the Virtual Desktop, Persona Management is not going to work. How do you apply them depends on your environment and requirements.
- Verify that the repository has enough space for all the users (at least N times the space required for one user, in a Pool of N desktops).
- The local profile and
- The remote (or central) profile
If folder redirection is configured, any applications that use the shell folder APIs automatically write their data to the network location instead of the local profile. Any applications that do not use the shell folder APIs continue to write their data to the local profile. For example, if My Documents is redirected, any applications that use the shell folder API to get the location of My Documents write to the redirected location. Any applications that write directly to %USERPROFILE%\My Documents continue to write to the local profile.
What happens if the same user account logs on to more than one virtual machine at a time? How are streamed accesses to the CIFS share mediated between them, if at all?
Is there is a way to customize the targets of Persona Management's attention (for example, save and restore parts of the Windows registry outside of HKLM if necessary to accommodate a Windows application that stores user-related persistent data in that part of the registry)?
Currently, Persona Management can only capture changes that are made to the user's profile. Any changes made outside the user's profile (such as HKLM) are not managed.
No. Persona Management only appears on desktop platforms. It does not appear on server platforms.
- Optimizing desktops for an implementation that includes Persona Management.
- Converting previously optimized desktops to allow for setting up Persona Management.
- Cannot configure the View Persona repository to the user's home directory in Active Directory (2007219)
- View Persona folder redirection fails when redirecting to an existing folder in the Persona managed profile (2019502)