Consider the following scenario:
- You have some folders that have a localized name are on a computer that is running Windows Vista Service Pack 1 (SP1), Windows Vista Service Pack 2 (SP2), or Windows 7.
- A file that comes alphabetically earlier than “Desktop.ini” exists in that folder that has the localized name.
- You enable the Folder Redirection feature on these localized folders.
- The redirected folders are copied to the shared drive by the folder redirection feature at the first logon.
In this scenario, the customized settings that are stored in the Desktop.ini file might not be copied.
For example, the Accessories folder has a localized name on a non-English operating system by default. When this folder is copied to the shared drive by the Folder Redirection feature, the Accessories folder no longer has its localized name. Instead, it has the "Accessories" name in English.
The customized folder settings are stored in the Desktop.ini file. When the file that uses a name that is alphabetically earlier than Desktop.ini exists in the folder and a Desktop.ini file does not yet exist on the shared drive, a new Desktop.ini file without the localized settings is created on the server when the files are redirected.
For example, assume that the start menu is redirected. The Accessories folder in the Start menu has a localized name on a non-English operating system and includes a file that is alphabetically earlier than Desktop.ini, the Commandprompt.lnk file. In this scenario, the following process describes how the new Desktop.ini file is created:
- Files are copied in alphabetical order. Therefore, the Commandprompt.lnk file is copied first.
- The Commandprompt.lnk is the first file that is copied t the shared drive. A Desktop.ini file does not yet exist on the server. Therefore, the server creates a new Desktop.ini after the Commandprompt.lnk file is successfully copied.
Note This new Desktop.ini file does not contain the customized settings.
- Next, the client tries to copy its Desktop.ini file to the shared drive but at this point, the new Desktop.ini already exists on the server. In Windows Vista SP1, in Windows Vista SP2, and in Windows 7, the Folder Redirection feature prevents a newer version of a file from being overwritten. In this scenario, the Desktop.ini on the server is newer. Therefore the new Desktop.ini file on the server-side remains and the Desktop.ini with the localized settings is not copied.
In versions of Windows that are earlier than Windows Vista SP1, a file on the computer always overwrites the file on the shared drive. Therefore, this issue does not occur on computers that are running these versions of Windows because the Desktop.ini file is copied.
To work around this issue, replace the Desktop.ini file on the shared drive with the Desktop.ini file that includes the localized settings after the files are redirected to the server at the first logon. The Desktop.ini file can be found in the default profile. The Desktop.ini file for the Accessories folder is located at the following location:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.