How To Rebuild a Corrupted NT Profile

 

Classic signs of a corrupt NT profile

Causes of corrupt NT profiles

What to do about it

To force an NT profile to be rebuilt, you must have administrative access to the PC(s) that the user uses, as well as administrative access to the user's home directory (or have the user there to type his password in).  The following instructions will assume this is an account in the EECS infrastructure, with roaming profile located in the user's home directory on coeus.
  1. Make sure the user is not logged in on any NT machine (his profile should not be in use).
  2. Delete the user's cached profile on each PC he uses (C:\winnt\profiles\username).  It's most important to do this on the PC that he will first login on, but I'd be wary about logging in on any PC that has a cached copy of the corrupt profile.  Note that you can do this remotely by mapping the network drive \\computer\c$, if you have admin access.
  3. Gain access to the user's home directory.  If the user is within earshot, you can do this by doing Start -> Run... -> \\coeus\username, getting prompted for his username and password.
  4. Rename his profile directory to profile.bak.
  5. Let the user know that when he next logs in, his profile will be recreated.  Settings like wallpaper will need to be redone, and items such as files on the desktop can be found in profile.bak in his home directory.