How RUM (Resource Updating Manager), QMM updates user profiles (4262054)

After using the RUM console to process a workstation, a user should not notice any difference in his work environment, unless something has gone wrong with the processing.

What exactly happens during resource updating, and how is a user profile switched so that target users can gain access to all the same settings that the source user had?

****WARNING: Using Registry Editor incorrectly can cause serious problems that can damage the operating system and the software installed. Quest cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.****


User profile settings are stored on the hard drive under C:\Users\UserID. There is also additional information placed within the registry. During resource updating, the following two steps provide seamless user profile migration:

1. C:\Users\UserID originally has Source_SID listed in the ACL (Access Control List). Target_SID is added or Source_SID is replaced with Target_SID depending on the RUM (Resource Updating Manager) job configuration.

2. Target_SID is added under HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\ProfileList and "ProfileImagePath" key is assigned the same value that "ProfileImagePath" has under Source_SID. This ensures both source and target users will receive the same profile which is stored under C:\Users\UserID.

Source_SID and Target_SID are matched account pairs migrated within the QMM or DMW  projects.