VCAP-DTA Section 9 Notes

By | February 11, 2014

Section 9 – Configure Persona Management for a View Implementation

Objective 9.1 – Deploy a Persona Management Solution

  • Create a Persona Management repository
    • Separate from Windows Roaming profile location.  Create share\UNC on file server.
    • Or you can use existing Windows profile location (Persona repository location – leave blank)
    • Set path for new repository in ViewPM.adm settings
  • Implement optimized Persona Management GPOs
    • Add ViewPM.adm to Computer Configuration>Policies>Administrative Templates via new GPO or Local Policy (gpedit.msc)
    • Settings are under VMware View Agent Configurations
    • Settings to enable for optimization are under the following folders:
      • Roaming and Synchronization
      • Folder Redirection
  • Implement optimized Windows Roaming Profiles with Persona Management

Deployments where users access both View desktops managed by Persona Management and standard Windows desktops managed by roaming profiles can cause problems. The best solution if the desktops are in the same domain is to use different profiles for the two desktop environments. To accomplish this:

  • Configure Windows roaming profiles (either with Windows GPO settings or on the user object in Active Directory)
  • Configure View Persona Management and Enable Persona repository location
  • Enable Override Active Directory user profile path, if it is configured

This prevents Windows roaming profiles from overwriting a View Persona Management profile when the user logs out of the desktop.

If users will share data between Windows roaming profiles and View Persona Management profiles, configure

Windows folder redirection. In folder redirection group policy settings for user profile folders, be sure to include %username% in the folder path      \\lab-dc\personadata\%username%\MyVideos

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.

Persona Management deployment guide

Objective 9.2 – Migrate a Windows Profile

  • Ensure pre-requisites are met for a profile migration
    • Run the migration utility on a Win 7 or Win 8 32-bit system, because most V1 profiles are 32-bit
    • Run the migration utility on a Win 7 Win 8 physical computer or virtual machine
    • Ensure network access to v1 profiles and login as administrator on Win7\Win8 machine
    • Ensure users are not logged in and don’t use their profile until migration complete

User profile migration

  • Perform profile migration using migprofile.exe

When you install View Agent with the View Persona Management setup option on a virtual machine, the migprofile.exe utility is installed in the directory \VMware\VMware View\Agent\bin

    • migprofile.exe [/s:source_path] [/t:target_path] [/r-:] [/takeownership] [config_file]

The following example migrates all V1 user profiles under the \\file01\profiles folder to the same location. V2 user profiles are created with .V2 appended to each user’s root folder name. The utility takes ownership of the user profiles during the migration:

    • migprofile.exe /s:\\file01\profiles\* /takeownership
    • migprofile.exe “/s:\\test\c$\documents and settings\user” /t:\\file01\profiles\ /takeownership /r-
  • Modify migration configuration file 

Note: Copy the content from the official documentation into notepad, then save as .xml to create the configuration file.  Modify as needed.

Migration file configuration

Leave a Reply