We are a school network (K-12) - Microsoft 2008 AD structure. We use DFS. And we redirect our Users' "My Documents" to their home directories via a domain GPO. The home directory path is set in AD user profile tab make the home directory "H" drive to the UNC (DFS) path specified.
Further we give staff (teachers and "computer assistants" in the schools) a "S:" drive mapping to the root of the student home directories (via a map drive command in the global login script).
Whether accessing the root of these directories via that drive mapping, a UNC path to the DFS share or a UNC path to the server share, some of the directories appear in the Windows explore window as "My Documents" instead of as the actual directory name.
The staff have the same setup - "H" is directed to a dfs path on a file server and their "My Documents" are redirected (via a GPO) to "H". However the staff dfs and the server that hosts the share for that DFS is completely different from the students dfs.
Up to now I've just been telling my folks to just unc path directly into the student's directory - don't stop at the parent directory - but our computer assistants whose technical skills run the gamut can't seem to grasp this or won't accept it as the answer.
For example I have one directory with 163 student home directories - in my explorer window 160 of them are appearing as their names - three appears as "MY Documents" and no amount of 'refreshing' the window seems to correct this. I have verified the three in this example are indeed named properly and the UNC path is set properly in the students' accounts.
In another directory I opened there are 139 student home directories with 134 showing by name and 5 showing as "My Documents" - near as I can tell, it varies station to station or time to time - I might see 20 of them in the same directory as "My Documents" one day and only 5 another. It would appear it is something on the work station doing the browsing.
We are working on a Windows 7 work station however I did see this also, though less often, in Windows XP on a Windows 2003 domain - prior to us upgrading this past summer so I do not believe the version has anything more to do with the issue than it seems to occur more readily than it did before.
Any idea what causes this and how (if) it can be corrected to get the Computer Assistants off our backs.