Profiles not loading at random 1

[pinkpanther56]

We currently use a Default Profile hosted in the server netlogon share which worked flawlessly until recently now at random some people aren't getting a profile. To try to solve this problem I temporally set a mandatory profile in the users tab but this is having the same issue sometimes they get it sometimes they don't.

I was thinking it might be due to load but when I watch the servers during logon the servers are hardly under any load and I can see that logons are being distributed between our three DC's.

I'm going to have a scour through group policy to see if there's a setting to force XP to wait for the remote profile.

Can anyone suggest other things to check and ways to troubleshoot this issue?

Thanks.

 

[linney]

Check in the Server Forums too.

http://www.tek-tips.com/threadminder.cfm?pid=1674

http://www.tek-tips.com/threadminder.cfm?pid=931

Is the policy mentioned in this KB of any use?

Scripts May Not Run Before Windows Explorer Starts Even Though the "Run Logon Scripts Synchronously" Setting is Enabled

http://support.microsoft.com/kb/304970

 

[porkchopexpress]

It's a flaw in XP SP3 that only causes an issue if the user changes their password at the logon prompt.

You have a user account that is configured to use a roaming profile. When you log on to a Windows XP Service Pack 3 (SP3)-based client computer by using this user account, the roaming profile does not load as expected. Instead, the system loads the local copy of the user profile or the default user profile.

This problem occurs if you are prompted to change the password when you log on to a Windows XP SP3-based client computer.

http://support.microsoft.com/kb/958058

 

[pinkpanther56]

Usually to integrate a patch into a CD image I would use this command "servicepackfilename /integrate:drive:\XPfolder" I tried that with this patch and the files unpacked to the usual location in the i386 directory but when I build a PC from the image the patch still needs applying. I had the same result when I applied it to a WDS image.

Any ideas why this might be?

Thanks.