Solved

Redirected folder names not consistent as viewed by other users

Posted on 2015-02-09
7
95 Views
Last Modified: 2015-02-23
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.

Issue:

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.
0
Comment
Question by:SolutionsHarmony
  • 4
  • 3
7 Comments
 
LVL 78

Accepted Solution

by:
David Johnson, CD, MVP earned 500 total points
ID: 40598239
rule #1: only the user should have access to this personal data, other users should not have access to this information.  If it is meant to be department or company-wide it should be saved in the appropriate folder
Cause: you are seeing the results of the desktop.ini
Solution: put an explicit deny on desktop.ini for all but the owner, If you have hundreds of users then you've just added a lot  of unnecessary work for yourself
0
 

Author Comment

by:SolutionsHarmony
ID: 40598902
In both the examples discuses the clients have the bad habbit or working from their user folders and not the recommended shared folders. The trust and security if the office is very relaxed so the normal privacy does not apply here.

With that said. I am not following what you mean for the desktop.ini file. Do you mean if I modify the permission of the desktop.ini in each of the user folder to now allow access to others, then the folder name will be the folder name only??
0
 

Author Comment

by:SolutionsHarmony
ID: 40627020
I would like to better understand this.  I believe you have the answer but I do not understand.

In other words, in my example where they DO access each other's user folders, you are saying that I remove permission to the "desktop.ini" file to only the owner of the file the issue will be resolved?

Is there a good way to do that in the GPO, do you think the best if to manually change the file permissions in each users folder in question.
0
What Is Threat Intelligence?

Threat intelligence is often discussed, but rarely understood. Starting with a precise definition, along with clear business goals, is essential.

 
LVL 78

Expert Comment

by:David Johnson, CD, MVP
ID: 40627065
no no no remove the permission from OTHERS so that they don't get the desktop.ini but the OWNER needs to have permissions on that file.
0
 

Author Comment

by:SolutionsHarmony
ID: 40627143
Ok thank you.  We are on the same page.  Just explained in opposite direction.  

I will remove all the permissions to the desktop.ini except for the backup user and the "Owner" of the file.

I was wondering if there is a way to make a rule with the file security to accomplish the same.  Or you recommend to just manually do in each users directory?  It is only like 30 users, but I would love to have a solution to do for new users also.  Not the end of the world though.

I understand your direction also.  I would LOVE the office to put common files in the shared directories that we have available.  Old habits die hard and I can not say I did not try.  

Thank you for your assistance and helping clear the fog on this strange issue.  Makes sense too where the results are mixed.  The desktop.ini must be different on different versions of Windows and update patches.  IE - Some show as the local folder name on the server and others pick up the "My Documents" label from the users computer.
0
 
LVL 78

Expert Comment

by:David Johnson, CD, MVP
ID: 40627168
Better to start the right way and keep these documents personal like they were actually on a users computer.
0
 

Author Comment

by:SolutionsHarmony
ID: 40627193
If I could turn back the clock 15 year on the one client, and turn back the clock 5 years on the other client I could implement correctly the first time like how the permissions are intended and redirected folder are done in GPO.

However, as stated they will NOT change their habits and especially to see a folder named different.

I guess I am done asking the same question to you about a better way to implement the permissions on the folders.  I understand that the world is flat and the only way to do things is the right way with no exceptions.  I got the message.
0

Featured Post

How to run any project with ease

Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
- Combine task lists, docs, spreadsheets, and chat in one
- View and edit from mobile/offline
- Cut down on emails

Join & Write a Comment

Nothing in an HTTP request can be trusted, including HTTP headers and form data.  A form token is a tool that can be used to guard against request forgeries (CSRF).  This article shows an improved approach to form tokens, making it more difficult to…
Never store passwords in plain text or just their hash: it seems a no-brainier, but there are still plenty of people doing that. I present the why and how on this subject, offering my own real life solution that you can implement right away, bringin…
In this video, we discuss why the need for additional vertical screen space has become more important in recent years, namely, due to the transition in the marketplace of 4x3 computer screens to 16x9 and 16x10 screens (so-called widescreen format). …
Sending a Secure fax is easy with eFax Corporate (http://www.enterprise.efax.com). First, Just open a new email message.  In the To field, type your recipient's fax number @efaxsend.com. You can even send a secure international fax — just include t…

760 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

19 Experts available now in Live!

Get 1:1 Help Now