Windows XP, Mandatory profiles and GPO Failure

[dhorowitz]

I've created a new mandatory profile for students, and using my test user account, I'm getting the following failures upon login:

 

1 - Unable to apply folder redirection policy, initialization failed

2 - The Group Policy client-side extension Folder Redirection failed to execute

3 - The client-side extension caught the unhandled exception '0xC0000005' inside: 'threadEntry : client main'

4 - The Group Policy client-side extension Group Policy Drive Maps failed to execute

and another set of entries for 3 and 4 for Group Policy Registry.

 

If I use the current profile, everything reports and operates normally. I created the profile as Microsoft says, step by step. Can anyone help pinpoint a fix for this?

[Steve21]

Need a bit more info really

 

Any chance of the full userenv logs?

 

Also, generally I'm assuming that from the order of the fails, it can't find your profile. ('0xC0000005' is access violation normally, I assume people have access to the share they're on?)

 

Where are the profiles, and what did you do in "Microsoft says, STep by step" ?

 

Thanks,

Steve

Edited April 29, 2011 by Steve21

[dhorowitz]

Please see attached file. This specific profile is located on our DFS share \\uufsd\district\profiles\hs\student_new.

 

The desktop portion of the user profile loads properly.

userenv.txt

[Steve21]

Wow That's a lot of errors lol.

 

Nearly everyone is suggesting problems finding the profile.

 

Error 5 = access denieds.

Can't find autoexec.bat = no access, or file hidden etc

ProcessGPORegistryPolicy: Failed to move archive file to temporary file due to error: 2. = Can't find valid file

 

Can you directly access:

 

\\uufsd\district\profiles\hs\student_new

 

from the account? Explorer style?

 

Really seems you're missing some permission to view it, or it's typo'd. (There isn't a $ for hidden file or something you're missing?)

 

(Would be cool to see entire file path to profile file + the "user" set profile path just incase)

 

Steve

[dhorowitz]

Attached is a picture of the profile info tab from the user's account in AD. I can successfully explore to the location of the profile. If I log in as a user with the old profile, everything works normally. According to the application log on the workstation, the user that is generating the errors is the NT Authority\System account.

user.bmp