Discussion Locked

Romaing profile integrity

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Win2K environ; user's account is a member of the local Admins group; outlook data file is saved within their profile directory tree.

During normal day-to-day operations, everything is normal. Subject in question logs off each evening. But if the computer is restarted, their profile reverts to an older version. This also affects their outlook e-mail data.

There are some other folders (not in the profile) sync'd for offline use - these work flawlessly.

TIA
EricF

4 replies

by rkelly

Do you have disk quotas set up for this user on the volume where they save their profile? If so the file may be too large to save back to the server and hence the problems you are facing.

Hope that helped

by solvent 42

No disk quotas or anything exotic - very basic W2K environ. 1 server - doing DNS and data hosting - hardware firewall doing the DHCP stuff. All clients W2K SP3 and using some folder synchronisation.

by rkelly

One other thing springs to mind, does the user have full control access to their profile folder on the server? If not then they won't be able to write back to the server when they logoff. Check both the share and the NTFS permissions.

Hope that helps

by solvent 42

Thanks for your attention to this matter.

Hmmmm - my last response isn't showing up. Here goes again...
All share and security permissions are correct (been there, done that). The only other problem we have with this network is that ocassionally, the system login/logoff takes an inordinate amount of time to load/save personal settings. The time can vary from 5 minutes to 30; and it happens very rarely.

I just tried the following yesterday, so I can't report on whether it has worked ornot:
Copied the profile from the local machine to the network server;
Changed the user's profile from roaming to local;
Restarted;
Changed the user's profile back to roaming;
Restarted.

The file on the network was the proper version after these steps. After tomorrow, I'll be able to check if it's being updated correctly.

EricF

This discussion is closed to new replies.