General discussion

Locked

Problems with roaming profiles

By fayad ·
For years I have this problem with users roaming profiles and I hope somebody can help me to solve this problem. This is the problem: I'm working with a Windows NT 4.0 server (SP3). The clients are Windows NT 4.0 workstation (Also SP3). I use roaming profiles that are stored on \\"ServerName"\Profiles\"User" directory on the server. On random occacion, (can happen on every workstation and any user at any time) the Ntuser.dat gets corrupted. Everytime this happen the size of the Ntuser.dat is exactly 32kb!?!?! You can still open the regisry but almost all the keys are gone. The only thing I can do is remove the Ntuser.dat, but then the user will lose all their local settings....!

My questions are: Why is the Ntuser.dat always 32 kb? What can I do to track where the problem occure? Does somebody expirienced such a problem, and what was the solution?

I hope sombody can help me with a solution, or indication where/ how to find the solution...

Greetings, Michel Fayad

This conversation is currently closed to new comments.

5 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Problems with roaming profiles

by kevin_b In reply to Problems with roaming pro ...

The ntuser.dat is the basic one from the default user. When a profile gets corrupted, or when NT says enough, it changes its name from xxx.dat to xxx.bak and the new profile xxx.dat is the default 32kb one. You can log on as admin and delete the new xxx.dat and rename the xxx.bak to xxx.dat and it should work. First thing, however, is to get the profiles off of the server profile directory! Move them to another share! Make sure the users have permissions to it.

Collapse -

Problems with roaming profiles

by fayad In reply to Problems with roaming pro ...

The question was auto-closed by TechRepublic

Collapse -

Problems with roaming profiles

by sukesh75 In reply to Problems with roaming pro ...

You can try doing the top option and also just check in the properties of the ntuser.dat to see whether the readonly attribute is checked or not if its not checked you should put a check as then i dont think the problem should occur after doing this.

Collapse -

Problems with roaming profiles

by fayad In reply to Problems with roaming pro ...

The question was auto-closed by TechRepublic

Collapse -

Problems with roaming profiles

by fayad In reply to Problems with roaming pro ...

This question was auto closed due to inactivity

Back to Windows Forum
5 total posts (Page 1 of 1)  

Operating Systems Forums