I have seen this issue on many different offices and would really like to have better knowledge on how to handle this situation.
What happens is when a folder is redirected, some people on the network see the folder as the actual folder name. Where others view the redirected folder as the label of the folder from the workstation that has redirected the folder.
Here is an example:
- Example assumes that the office wants to share the users documents folders to the rest of the office.
- DC 2012 server called "Server" with share "USERS"
- Workstation with user named "DENISE" and "documents" folder
- When the local profile of "Denise" documents folder location is modified to point to " U:\Users\Denise", everything functions as normal and works just fine.
Some people will see that U:\ folder as "My Documents" and others will see as "Denise". In another office there are like 8 folders all called "My Documents" where the underlying folders are their specific user names.
Desired is that everyone sees the folder as Denise, but locally on the computer it is still called "documents". So far the only work around that I have found is to rename the local folder label to like "Denise Docs" so that it is easy to see on the server, and also ok on the workstation. The other option of naming to"denise" is very confusing to the local user but is great for everyone else. Thus, so far the only solution that I have found is to rename the label to something like "denise Docs".
Please help me better understand this. I have a feeling that the preference of what and how it is viewed is a workstation specific setting. Not sure what is causing different computers to see differently with the same OS. Have seen differences also in the different OS versions when viewing the redirected folder on the server.