Viewing Quest vWorkspace Managed User Profile Data
Monday, 24 August 2009 by Michel Roth
One of the unique features of Quest vWorkspace is our User Profile Management. Quest vWorkspace User Profile Management (previously known by the module named Metaprofiles-IT) when implemented in concert with Microsoft Group Policy Folder Redirection provides a stable alternative to Roaming Profiles

Often referred to as Hybrid User Profiles, it allows users to retain administrator approved portions of their user profile, (typically stored in the registry) whereas everything else, including the local user profile is discarded at logoff. Users My Documents, Desktop, Application Data and optionally Start Menu are typically redirected to network file shares using Group Policy (they can also be stored using Quest vWorkspace User Profile Management), whereas the vWorkspace User Profile Storage Server manages settings that are imported to and exported from the User Registry Hive (HKCU). This unique combination provides for lightning fast logons (typically 10 seconds, or 1 -2 seconds longer than a local profile), lower data storage requirements, and a stable working environment that looks and feels personal to the end user. The cool thing is that you can create a Managed Profile for Terminal Servers users, Virtual Desktop Users, Blade PC users or all of the above!

Quest vWorkspace User Profile Management data is stored on the vWorkspace User Profile Storage Server in an encrypted manner so there is no easy tampering with user data. This does however also mean that the user data cannot be opened by administrators for troubleshooting. Sometimes administrator do need to view the Quest vWorkspace User Profile Management data. There is an easy way to do this, should you need to:

  1. Go to the  vWorkspace User Profile Storage Server and locate the  vWorkspace User Profiles directory (C:\Metaprofiles for example).
  2. Copy the profile that you want to troubleshoot. Profiles are stored with SID as the file name. You could use a a tool like PSGetSid to determine what SID translater to which user.
  3. Rename the copy from .grp (for per-silo settings) or .gbl (for global settings) to .zip
  4. Now open the .zip file and you can look inside the Quest vWorkspace User Profile Management data to perform your troubleshooting. It should look like something like this:

Quest vWorkspace User Profile Management data

All the folders (like Desktop in the screenshot) you see are the folders that are configured for inclusion in the Quest vWorkspace User Profile Management configuration.

The file “dir.txt” contains all of the files inside the folders that are synchronized as part of the Quest vWorkspace User Profile Management configuration.

Finally and probably most importantly “reg.xml” stores all of the registry keys and values that have been configured for inclusion in the Quest vWorkspace User Profile Management configuration.

Please be aware that this method should only be used for troubleshooting purposes. Changes to the Quest vWorkspace User Profile Management should always be made through the vWorkspace Management Console in the Quest vWorkspace User Profile Management configuration. Directly editing the profile is not recommended nor supported.

Source: http://blogs.inside.quest.com/provision/2009/08/24/viewing-quest-vworkspace-managed-user-profile-data/


Related Items:

Customizing the Look and Feel of Quest vWorkspace Web Access (13 August 2009)
User Environment Management and Lockdown for desktops in Quest vWorkspace 7.0 (12 January 2010)
Quest vWorkspace Web Access 6.2 MR2 (Maintenance Release 2) (6 November 2009)
Using vWorkspace With Private Certificates Part 1: The Quest vWorkspace Windows Client (6 July 2009)
Quest vWorkspace Client for Mac (26 October 2009)
Demo of Quest vWorkspace With NetApp Storage Integration (18 September 2009)
Two new BETAs available: Quest vWorkspace 6.2 Beta 1 and the Quest vWorkspace Mac AppPortal Beta 1 (13 June 2009)
Quest vWorkspace Mac AppPortal Released (23 November 2009)
IGEL Integrates Quest vWorkspace Clients into IGEL Universal Desktops (5 November 2009)
Quest and NetApp Integration (27 October 2009)
Comments (0)add feed
password
 

busy