Users losing access to "My Documents" shortcut

[skenmy]

Hi all!

Got an odd one happening here - we have users (both teachers and students) losing access to their "My Documents" shortcut on the desktop (which is mapped to their network share), seemingly randomly. Double clicking the icon gives a permissions error ("You do not have sufficient privileges to perform this action"). Accessing the same network share through a drive mapping works absolutely fine. There appears to be no correlation in machines, times, or AD groupings.

We have an interim solution to the issue - if we add the network user to local power users on any machine and log them on and off again, then remove the local power user access, they regain access to their shortcut throughout the school!

Does anyone have any ideas as to what could be happening? We are all baffled here!

[plexer]

Double check your redirection settings.

Do you use groups to redirect to different places.

Make sure gran exclusive rights is not checked.

Ben

[skenmy]

Hi Ben,

We do use our groups to redirect, but all the groups have the same policy, to redirect to the users' home directory. Grant exclusive rights is unticked.

[plexer]

What are the permissions and ownership on a persons home directory that is affected by this?

Do you use one share per user or a top level share for the home folders?

Ben

[skenmy]

As for the permissions, they are our "normal", the user and domain admins have full control, and the staff user group have everything bar full control (this is for students, omit the last part for staff users)

By default the user is the owner of the home directory. Our structure looks like this:

\\sansserver\YearOfEntryData$\StudentNumber

So we have a common share per year group, and the home directories are mapped to each individual students' number.

[Michael]

Failed My Documents redirection is usually permissions related. Using a free utility like Autoshare is great for ensuring permissions are correct across all home shares.

Looking at Event Viewer on the machine itself (where a user logs on) should reveal more information as to why it failed.