• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1969
  • Last Modified:

SBS2003 Assigning permissions to the registry hive - ntuser.dat error the process cannot access the file, because it is being used by another process

I'm trying to reconnect a recreated user to their domain profile per the included  instructions. When I try to " assign permissions to the registry hive" ((NTUSER.DAT) second step). I get the message. "the process can not access the file, because it is being used by another process".  What process is stopping me?  Thank you.

(INSTRUCTIONS)

You'll need to assign the user full access permissions recursively to the old profile folder. You'll also need to do the same for the registry hive (NTUSER.DAT) in the old profile. Then you'll need to edit the ProfileImagePath key as you've previously noted.

To assign permissions to the profile folder:

1.Log in as a user with administrative rights.
2.Right-click the old profile folder (C:\Documents and Settings[user name]) and click Permissions. Go to the Security tab. Click Advanced.
3.Go to the Owner tab. Recursively change the owner to Administrators. (If you get an error, proceed to step 4.)
4.Go to the Permissions tab. Add the new user account, with full permissions. Apply this recursively.
5.If you get an error in either step 3 or step 4, repeat both steps in sequence until they both complete successfully without errors.

To assign permissions to the registry hive:  (MY PROBLEM)

1.Log in as a user with administrative rights.
2.Open Registry Editor. Select the HKEY_USERS hive.
3.Click File - Load Hive. Browse to the old profile folder and select the file ntuser.dat. Give it a friendly name when prompted -- it doesn't really matter what you put here.
4.Select the newly loaded hive key under the HKEY_USERS hive. Right-click this key and click Permissions. Go to the Security tab. Click Advanced.
5.Go to the Owner tab. Recursively change the owner to Administrators. (If you get an error, proceed to step 6.)
6.Go to the Permissions tab. Add the new user account, with full permissions. Apply this recursively.
7.If you get an error in either step 5 or step 6, repeat both steps in sequence until they both complete successfully without errors.
8.Select the hive key (from step 4), then click File - Unload Hive.

To modify the ProfileImagePath registry entry:
1.In Registry Editor, browse to HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList (Note the Windows NT not Windows in the path).
2.Under this key, you will see several subkeys, each corresponding to user SIDs. You'll need to identify the SID for the current user account you are attempting to associate with an old profile.
3.Under the key corresponding to the SID for the user account, modify the ProfileImagePath entry to reflect the path of the old profile folder.
4.Close Registry Editor.

Restart the computer. (You may be able to simply log out, but if the registry hives do not unload correctly, the next step may fail.)

Log in as the user, and you should get the user's profile back.

NOTE: Certain saved passwords will be lost, because Windows XP provides a method for saving passwords in an encrypted format that uses the user SID and password as part of the encryption algorithm.

Note also that if the user was previously applied to ACLs on network resources, you may need to modify those ACLs to reflect the user's new SID.
0
Joemt
Asked:
Joemt
  • 2
1 Solution
 
LesterClaytonCommented:
This can happen if the Operating System is in the process of unloading the hive but has not succeeded, so it keeps the hive open.  Rebooting the server will close the hive.  If you find that you are still having trouble after the server has rebooted, then clearly the hive is being loaded and is in use either by another user on the system, or perhaps even yourself.  

Also, be sure that you are browsing to the correct NTUSER.DAT file - you shouldn't be opening your own, but that of the profile you wish to change.
0
 
JoemtAuthor Commented:
I was able to complete the instructions above.

When the user logs in to her Workstation, she does not get her domain profile and has no access to the network.   She is logging into the domain and not the local workstation. Seems the PC is not logging her into the server at all as if the domain profile listing at the pc is corrupt?  Any suggestions.....not sure what my next step is.
0
 
JoemtAuthor Commented:
Excellent - thank you
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Microsoft Azure 2017

Azure has a changed a lot since it was originally introduce by adding new services and features. Do you know everything you need to about Azure? This course will teach you about the Azure App Service, monitoring and application insights, DevOps, and Team Services.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now