Microsoft KB Archive/888095

= You cannot add paths to the &quot;Exclude directories in roaming profiles&quot; policy =

Article ID: 888095

Article Last Modified on 11/1/2006

-

APPLIES TO


 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
 * Microsoft Windows XP Professional

-





SYMPTOMS
You try to reduce the size of user roaming profiles by excluding additional folders from the profiles. However, when you try to add one or more paths to the &quot;Exclude directories in roaming profiles&quot; policy, you cannot type any additional characters in Policy Editor.



CAUSE
This problem occurs because the Microsoft Windows Server 2003 Policy administrative template files (.adm) have a limit of 260 characters for the ExcludeProfileDirs policy.



WORKAROUND
Important You cannot use the following workaround unless the fix that is described in Microsoft Knowledge Base article 827878 is installed on your computer. For additional information about the fix in Knowledge Base article 827878, click the following article number to view the article in the Microsoft Knowledge Base:

827878 The &quot;Exclude directories in roaming profiles&quot; policy stops working when you add paths

To work around this problem, follow these steps:  Locate the folder where your .adm files are loaded from. For additional information about how to do this, click the following article number to view the article in the Microsoft Knowledge Base:

228460 Location of ADM (Administrative Template) Files in Windows

 In the folder that you located in step 1, open the System.adm file by using a text editor such as Notepad. Locate this section in the file:

PART !!ExcludeMessage EDITTEXT

VALUENAME &quot;ExcludeProfileDirs&quot;

MAXLEN 260

END PART

 Change the &quot;MAXLEN 260&quot; line to &quot;MAXLEN 4096&quot;, and then save the change that you made to the System.adm file. Distribute the file to all the policies that require this change.

<div class="status_section">

STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the &quot;Applies to&quot; section.

<div class="moreinformation_section">

MORE INFORMATION
The procedure that is described in this article applies to the default method of handling policy .adm files. For additional information about how to change Group Policy template behavior, click the following article number to view the article in the Microsoft Knowledge Base:

316977 Group Policy template behavior in Windows Server 2003

In the scenarios that are described in Knowledge Base article 316977, you have to use local folders to find the .adm file and distribute it to other administrative stations.

If you are using the settings that are described in Knowledge Base article 813338, you must distribute the new .adm file to the following locations:
 * All the policies
 * All domain controllers where policies are edited
 * All Administrative stations

For additional information about how to minimize SYSVOL size, click the following article number to view the article in the Microsoft Knowledge Base:

813338 How to minimize SYSVOL size by removing administrative templates (.adm files)

Although Windows can handle more than 260 characters in ExcludeProfileDirs, the Windows Server 2003 Policy .adm files have a limit of 260 characters in the ExcludeProfileDirs policy.

Keywords: kbnofix kbbug KB888095

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.