Question Locked

Corrupted ntuser.dat in roaming profile W2K3 - XPSP3 - MS Outlook

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

Hello,

I have problem with roaming profiles. When my users log on to your system the ntuser.dat fails (ntuser.dat has 256 KB size) and they have their pulpits and documents but they can not use MS Outlook 2003. When I replace ntuser.dat with backup file everythig works fine.

I have checked user folder / share permissions, there is no disk quotas. There is some redirection for *.pst files/not for all users.

Have you any suggestion how to resolve this?

What is cause this?

Thank you in advance.

Mark

(sorry for my english)

8 replies

by barryhiggins

Hi,

I am having the same problem, I provied support in a Win2k3 Active directory domain, using roaming profiles and Outlook2003.

Frequently users are presented with what looks like a corrupt profile (missing files from the desktop, no mapped drivers or printers) and in all cases the ntuser.dat file only has a fraction of the required information (with a size of 256KB).

If anyone has any ideas I would also be glad to hear them.

Thanks,

Barry

by kopieck

I am having the same problem ( W2K AD server )since autumn of 2006. Ideas :
1) Symantec Antivirus CE 10.1 ??
2) outlook PST files on the server ?

KK

by animatech

Does your user has a TS specific profile and a normal profile?
If he has 2 profiles then are they pointing to different locations or to the same location?
If both are pointing to the same location that may cause a problem.

by witold.madej

Hi, We don't use TS environment. "Normal" profiles are stored on file server (W2003 AD), no quota, permission structure according Microsoft advice, shadow copies - disabled. It looks that user can't load his profile, then XP Pro. load default (256kb) and replace on share. Everything is in LAN (100/1000, about 100 users), I don't observe any communication bottlenecks. In NT4 environment everything was fine. Problem has started when we migrated to AD environment (root domain is located out my country).

by Former member

If I follow this correctly, it sounds like the issue is for a single user. if that is the case, is that user in the appropriate OU in AD and if so, are you positive that the folder share in which that users profile is stored/created has the correct permissions?
for example. if the user is in the STUDENT OU and the share permissions do have STUDENTS group list, but the STUDENTS group only has READ ONLY privileges, then the profile will not be able to be written to this share. This is a common problem I see.

This discussion is closed to new replies.