I experience an annoying behavior with the folder redirection with Windows 2008 R2 and Windows 7
i think this is a sort of bug.
Server : Windows 2008 R2 STD (US)
Station : Windows Seven (Fr)
We defined a hidden share as the home folder in Active Directory.
\\Server\Users$\User1 (home folder for user 1)
\\Server\Users$\User2 (home folder for user 2)
In my GPO:
When i configure the Folder redirection Setting with this parameter :
Basic - redirect everyone's folder to the same location
Redirect to the users home directory
Move the content of Documents to the new location
Also apply rediretion policy to windows 2000 etc...
When i log to the client, the redirection works well.
When i log to the server and browse my "users" directory, the user directory appear like he was renamed in "My Documents"
The folder are not really renamed, it was just the display that was incorrect.
If i use a command line to browse the directory, the folder appear with the good name.
Someone can help to resolve this behavior ?
Hi. I am experiencing this also. I work for a High School and Teachers want to access student work but all redirected folders are locked exclusively. If I turn the exclusive option off then teachers can't access the student work either because now all 1500 student folders are called "My Documents". It seems the only option is to turn folder redirection off. Ironically, staff can't access student work when folder redirection is off as students end up saving their work locally to the machines instead of the shared network drive.
I can see that this problem existed in Vista so it is pretty evident that their won't be a fix for 7 either.
Ok I have ranted and I feel better now :-)
Can I have more info on the desktop.ini files and adding deny permissions onto it? Which desktop.ini files did you apply this to? The ones within the redirected folders, roaming profiles, everywhere? And also, does this make deleting folders off the fileserver a pain when a user leaves?
Also, did you script the changes to the files? If so, is it possible to get an script template for this?
Sorry, I was being daft about which desktop.ini file to remove permissions to. I found that. It does work and its enough to go live with our proposed folder redirection on our new terminal servers. However a sample vbscript would still be appreciated as there's 200 folders in which I will need to change this.
this behavior is idiotic. when XP users browse my "Users" folder, they see the actual names of the folders (first.last). but when win7 users browse the Users folder, they see a bunch of "My Documents." is this considered progress? what is the logic behind this?
i am confused, in workaround method #3, as to which "desktop.ini" files to deny permissions to, and which "administrator" to deny it, in me
this behaviour is by design?
this is typical of microsofts recent asinine design decision making, and further evidence that the latest generation of windows server and desktop products are not sufficiently well architected or tested for the enterprise.
I dont know if that denying read to desktop.ini will work as it may interfere/ generate errors in the backup. Unless i just dont back up desktop.ini...
Solution is crappy. Maybe a GPO to turn off this writing of the desktop.ini file or the writing of this extra windows 7 data. We are not going to move to windows 7 rigjht now, but its a pain to administer when there are a few win7 clients on the network and you want to audit for file infractions and such. All the infractions are labeled my documents.. argG!
I've found out if you run Attrib -r on the folders, the folders display the right way.
I just havent found a smart way to do it on all the folders, and haven't found out if the problem comes back again
- Proposed as answer by WillieMac99 Monday, July 25, 2011 3:49 PM
I've written a PowerShell script which denies read access to the desktop.ini file to a specified group. Anyone in this group will then not have the documents renamed .
Had the exact same problem. Used "Attribute changer" - http://download.cnet.com/Attribute-Changer/3000-2248_4-13676.html and removed the read only attribute on the affected folders.
- Proposed as answer by Shaun_Ec Monday, January 13, 2014 10:38 PM
attrib -r E:\Userdata\*.* /s /d
I believe this is a BAD idea as it will deny read rights to ALL files and folders.
I have re examined this problem because it was severely pissing off my users.
from this link: http://www.craig-tolley.co.uk/2010/12/20/redirected-my-documents-folders-showing-as-documents-rather-than-the-users-name/
I have added a VBS script to the user logoff section of my group policy. This will delete the file on logout. I have been unable to determine how to stop generation of this desktop.ini file, does not seem possible. Copy of the VBS script from the link above is reproduced below, incase the link goes dead. I did not write it.
On Error Resume Next Set WSHShell = WScript.CreateObject("WScript.Shell") Set FSO = CreateObject("Scripting.FileSystemObject") DocsPath = WSHShell.SpecialFolders("MyDocuments") If FSO.FileExists (DocsPath & "\desktop.ini") Then FSO.DeleteFile (DocsPath & "\desktop.ini") End If
what this will do, when applied at logoff, is delete the desktop.ini file from the users "my documents". Sort of like a clean up.
Doesn't solve the problem by any means, but should make after hours work easier at least.
- Proposed as answer by Eddie EC Monday, January 30, 2012 5:09 PM
For smaller environments, would creating a single blank desktop.ini file with Read-Only checked, and then pasting that into each users home directory work?
I mean it did fix the view, and it should prevent recreation of the file because the read only option is checked.
Will it create log on delays/errors?
- Edited by bebarce.el-tayib Monday, February 06, 2012 2:52 PM
Am 06.02.2012 15:51, schrieb bebarce.el-tayib:>> For smaller environments, would creating a single blank desktop.ini> file with Read-Only checked, and then pasting that into each users> home directory work?>The read only attribute has to be set on the directory containing thedesktop.ini file to make explorer respect it. The attributes of thedesktop.ini itself do not matter, but usually they are "SH".sincerely, Martin
A bissle "Experience", a bissle GMV... Wenn meine Antwort hilfreich war, freue ich mich über eine Bewertung! If my answer was helpful, I'm glad about a rating!
In our environment this seems to work too:
Add this permission to \\server\share$\User1 for User1:
Deny Write Attribute (This Folder Only)
so far it has stopped the 'renaming' for all new Win 7 (ex-XP) users. For existing 'renamed' folders we'll have to do use one the methods described in the earlier posts.
When a user logs in to a Windows 7 computer, and the home folder exists on a network share, the folder is renamed to My Documents instead of the users name.
When browsing the home folder with windows 7, a filename column can be added to view the proper name of the folder. However, in an environment with both XP and Wimdows 7, XP does not have the ability to add the filename column to explorer.
(Note: This article assumes you are familiar with editing the registry, and doing registry imports from a file. As always, backup your registry before editing. )
When a user with a home folder redirected to a network share logs in to a Windows 7 machine, windows 7 creates a desktop.ini file in the user home folder. The desktop.ini contains the line:
The line causes the folder to appear with the name My documents.
The entire desktop.ini contents:
To view the folders with the original name in Windows XP:
Changing the desktop.ini to reflect %filename% makes XP see the home folder as the file name, just like Windows 7 does when you add the filename column. (Note, the icon changes in XP, so at least you can tell when someone has logged into windows 7).
Change the desktop.ini file to reflect %filename%:
This can be set in the registry in the following key:so when Windows 7 creates the desktop.ini file, it incorporates this setting.
The regfile to change it is:
Windows Registry Editor Version 5.00
Setting PreCreate value to 0 in the same registry key stops the desktop.ini file creation altogether!
I searched the registry to find the value, LocalizedResourceName=@%SystemRoot%\system32\shell32.dll,-21770 to determine which key was used to create the desktop ini.
Then since Windows 7 can add the column filename in explorer, I thought I would try %filname%
Note: I ran a script to delete all the existing desktop.ini files, then applied the reg hack.
Networking: It's not just a job, it's an OBSSESION!
I solved this by putting a Group Policy preference to delete u:\desktop.ini at startup. It doesn't seem to have caused any issues and now all the students' work areas show up as their usernames now and not "My Documents".
- Proposed as answer by _clairehr_ Wednesday, May 15, 2013 3:10 PM