Discussion Locked

Profile is always cached on NT 4.0

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Here is my problem. One of my customers was logged on while the network connection died. Now everytime THEY try to logon they get a cached account. Everybody else that interactively (at the keyboard) logs on authenticates to the domain. The onlyway I have resolved this problem in the past is to rebuild the profile by deleting the NTUSER.DAT file. I have not been able to piece anything together from TECHNET. Is there a better method to this madness???

5 replies

by cheins

Assuming that the user has a roaming profile....
Since the local profile is newer you get the cached profile or should get a choice between network and local profile. I don't have the why answer but one workaround for future problems is to have the user logon to a different workstation, delete the profile from the machine where the 'network connection died' then have the user logon after a reboot.

by robcoxon

You can delete the profile from the computer that they logged onto in the c:\winnt\profiles sub-directory. Just find the name of the person who logged on and delete the whole folder. You'll need to logon as an administrator. They can now logon again and get their roaming profile. To change this so it doesn't happen again you need to have a system policy installed on your domain. In system policy choose "default computer properties" and open the "Windows NT User Profiles" choice. Put a check in the "Choose Profile Default Operation" box and choose "Download profile" from the Default option dropdown menu. This will not fix the profile being left on a machine if the machine shuts off without the user logging off, but it will give them a choice of profiles at next logon. I believe Windows 2000 fixes this problem.

This discussion is closed to new replies.