Errors when you have a large "Folder Redirection" policy settings file in Windows Vista, in Windows 7, in Windows Server 2008, or in Windows Server 2008 R2
- You set Folder Redirection policy settings for many folders in an environment.
- The folders are configured to use Advanced Settings when the user is a member of a group.
- The first time that you add all the groups to the list of folders, a large Folder Redirection policy settings file is created for many groups as expected.
When you open the Folder Redirection policy settings, you find that the folders do not display the settings. Instead, the folders are displayed as Not configured.
When you try to show the settings of the Folder Redirection policy in the Group Policy Management Console (GPMC), you receive the following error message in the Folder Redirection Policy Details section:
These symptoms occur on policies that are created and that are populated by using the Local Group Policy Editor on a computer that is running Windows Server 2003, Windows Server 2008, or a version of Windows that is newer than Windows Server 2008.
When you try to apply the new Folder Redirection policy settings to a domain user account on a computer that is running Windows Vista or a newer version of Windows, the settings are not applied. Additionally, you may receive the following error message in the Application log:
Event ID: 7016
Task Category: None
Completed Folder Redirection Extension Processing in xxx milliseconds.
<Data Name="CSEExtensionName">Folder Redirection</Data>
Cause of Symptom 1 and Symptom 2
For an .ini file that was created in Windows Vista or in a newer version of WindowsThese issues occur because the Folder_Redirection section of the .ini files is larger than 32,767 characters. However, the limit for the combined SID list for all folders is 32,767 characters. This limit is encountered when the GetPrivateProfileSection API is used to read the section.
Note If the SIDs typically have 48-50 characters, you can have about 670 SIDs in a policy for all folders before this issue occurs.
For an .ini file that was created in Windows Server 2003These issues occur because the limit for the number of groups for each redirected folder in a policy is exceeded. This limit depends on the length of the SID string that represents the group and also on the length of the redirection path. For example, you can have about 230 groups for a single folder if a SID string is about 48-50 characters, and if the UNC path of the folder is 80 characters.
- The aggregate size of all folders can exceed 32,767 characters.
- The first time that you open an existing policy, the settings may be converted to a newer format on a computer that is running Windows Vista or a newer version of Windows. This behavior may occur if the existing policy was created by using the Local Group Policy Editor in Windows Server 2003. This behavior also occurs when the policy settings are shown in the Settings view in the GPMC. Therefore, a policy might work by using the old .ini file format, depending on the settings. However, a policy might not work by using the new file format, depending on the settings.
Cause of Symptom 3This issue occurs because of a limit of the GetPrivateProfileString API that is used to read this section.
The list of groups is stored as a string of SIDs in an .ini file. When the list exceeds 32,767 characters, this problem occurs. Each string that represent a SID in the .ini file is typically about 48-50 characters. Therefore, you can have around 300 entries for each redirected folder.
For more information about the Folder Redirection feature, visit the following Microsoft TechNet Web site:
Article ID: 978098 - Last Review: 02/04/2014 04:10:00 - Revision: 2.0
- kberrmsg kbtshoot kbexpertiseinter kbsurveynew kbprb KB978098