If you are using a migration tool (ADMT, Quest, NetIQ etc ) to migrate workstation and user profile, it will automatically translate the SID and assign the same profile to the target user account. The following procedure is used in the background to achieve this:
· The C:\Documents and Settings\UserName originally has Source SID listed in the ACL. Target SID is added or Source SID is replaced with Target SID depends on your migration tool configuration.
· The 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:\Documents and Settings\UserName.
For some reason, if a migrated user gets a new profile (or lost the old profile) you can use the following procedure to re-assign the old profile back to the target account:
1. Ask the user to log off from the user workstation.
2. Run Regedit from your computer. Connect Network Registry to the user workstation.
3. Go to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\ProfileList
4. Go through the Profile list and identify the Source account. Copy the value from the ProfileImagePath key.
5. Again go through the Profile list and identify the Target account. Paste the ProfileImagePath key value there.
6. Restart the user workstation.
The ProfileImagePath key will be same value for both Source and Target user accounts. This ensures both source and target users will receive the same profile which is stored under C:\Documents and Settings\UserName.
4 comments:
Not always change profileimagepath value is enough: if new profile is a result of ADMT mistake, then you must also add new SID ACL to old user profile folders and to NTUSER.Dat Hive in regedit. I obscure this ADMT v3.0 mistake when many users have profiles on the same PC
I mentioned these two steps in the blogs: ACL and ProfileList
• The C:\Documents and Settings\UserName originally has Source SID listed in the ACL. Target SID is added or Source SID is replaced with Target SID depends on your migration tool configuration.
FYI- If you have many profile on the workstation, make sure the user information is in the ADMT database otherwise ADMT won’t update the profile.
Hi, it works for windows 7 too ??? thanks 4u reply.
It should. Are you seeing any issues?
Post a Comment