A User's workstation has been processed using QMM RUM (Resource Updating Manager), but after a user logs on into the target domain, a new profile is created. This article provides suggestions for troubleshooting issues that may occur with user profiles after resources have been updated.
The issue may occur for any of the following reasons:
1. Since the trust is established, the user may have accidentally logged into the target domain before his profile was updated.
2. The users profile is locked and new profile has been created (occurs only on pre-Windows XP operating systems, on Windows XP and later temporary profile is created and upon reboot the issue is fixed on its own). More details on this issue can be found in solution SOL23271 FixProf utility and Update profile on next restart if failed option or how to avoid problem with locked user profiles during resource updating.
3. If the user is not selected in ADAM he will not be included (added) to the vmover.ini file and users data will not be processed. This can happen when the option Specify Custom Map was used last time when updating resources, make sure every time you use this option and after resources have been processed to delete the custom map (Actions - Delete Custom Map).
Some troubleshooting suggestions:
-See if the log file contains any errors. When reading the log file, under profiles if you see a SID entry, this means the profile for this users SID has been updated. The log also tells how many profiles were re-permissioned on particular workstation.
-In Windows Explorer select the users profile and under the Security Tab (NTFS permissions) verify if the profile has been updated successfully. There should be a new entry for permissions of target user.
-Ask the user to log off, then log on as admin and open the registry editor. Under HKEY_USERS, verify there is only one SID present (twice), for the currently logged on user. If there is another SID visible (even if the user is not logged in) that means profile is in use and is locked.
1. Run resource updating again with the option revert changes, which will undo the previous session. Update the workstation again.
NOTE: If operating system is pre-Windows XP ensure that Update users profile on next restart if failed option is selected. If users profile is in use and locked a new profile will be created; however, the setting Update users profile on next restart if failed will ensure that after the next restart, the user will get their old profile back. On Windows XP and later temporary profile is created and upon reboot the issue is fixed on its own.
More details can be found in solution SOL23271 FixProf utility and Update profile on next restart if failed option or how to avoid problem with locked user profiles during resource updating.
Also MS utility User Profile Hive Cleanup Service also known as UPHClean can be used, which can be downloaded from; User Profile Hive Cleanup Service - http://www.microsoft.com/downloads/details.aspx?FamilyID=1b286e6d-8912-4e18-b570-42470e2f3582&displaylang=en
2. Ask the user to log off, and then rename the newly created profile using Windows Explorer. After reprocessing the users workstation with appropriate settings, ask the user to log on again.
3. If none of the above resolves the issue, open the registry editor (you can connect to users registry remotely) and under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList, highlight the target users SID on the left side. Then on right side you should see the profile name. Copy and Paste the value of the key "ProfileImagePath" from the source profile to the target profile. The entries should be now exactly the same. This will immediately resolve the problem and the target user will now use their old profile.
NOTE: This is a workaround which can be used in urgent situations for single accounts.
Quest Software does not provide support for problems that arise from improper modification of the registry. The Windows registry contains information critical to your computer and applications. Make sure you back up the registry before modifying it. For more information on the Windows Registry Editor and how to back up and restore it, refer to Microsoft Article ID 256986 “Description of the Microsoft Windows registry” at Microsoft Support.