our network previously was all xp pro and we segregated profiles and user folders into seperate shares which all began with the username ie stafffolders\jbloggs this has My Docs desktop etc staffprofiles\jbloggs originally we scripted using %username% but now use dsadduser to map profile space and sharedrive space to a letter since putting several vista pcs into this domain everyone who logs in to a vista pc - the profile share continues to work ok as before- the file share though renames itself to Documents for each user so we now have 6 Documents folders in the share - the only way to check whose files they are is by checking security to find the owner - I am also not sure whether the renaming will sever them from their documents if they log onto an xp machine? what are we doing wrong - and why is vista doing this?

Hi, This behavior is by designed. It is because, on Windows Vista, there is a desktop.ini file inside of the folder, and the display name of the folder is determined in the desktop.ini file.. Workaround: ================ 1. Enabled "Give exclusive access to the redirected folder" option. If you enable it, administrators do not have read access to the desktop.ini. So, when viewing the folders, administrator will see the actual file system folder name. 2. Remove administrator read access on each of the desktop.ini files on the server. You might need a script to do this. Also, for any new users, you will need to repeat this again. Note: The workaround 1 works only for the new users. For existing folders on the server, you will still need a script to remove administrator access. 3. You can create a subfolder called documents and redirect to that subfolder instead. This will eliminate confusion by allowing you to see what folders belong to what user.For example: \\server\users\username\documents (Original is \\server\users\username.) Hope the information is helpful.

We had the exact same problem when we moved all our domain desktops to Vista.I found the simplest and permanant answer is to replace the desktop.ini file in each users folder with an empty desktop.ini file.If you merely delete the desktop.ini file, it will be re-created next time the user logs in. But if one already exists (although it is empty) it does not get replaced.Here's how it worked for us.I wrote a simple script (batch file) to do the job, placed it in the netlogon folder on the network andthen called itfrom the logon script.Step 1. Search for the existing desktop.ini files in thehome foldersand delete them.Step 2. Next time the user logs on, it will copy the new empty file to the folder._______________________________________________Script@echo offecho y|xcopy \\fileserver\netlogon\desktop.ini z:\ /H_______________________________________________I hope this helps others.RobC

Ran into this problem on Server 2008 and Vista with Redirection of any folder, not just My Documents folder. This can be resolved witha simple group policy setting new to server 2008 and Vista. Computer config/Administrative Templates/System/Folder Redirection/ Enable thesetting "Use localized subfolder names when redirecting Start and ..." RebootThis will allow you to see the "actual" name of the folder that you redirected to rather than My Documents, Downloads, etc.Hope this helps.David Bliss