Microsoft KB Archive/814608

= Group Policy Scripts Extension Truncates Script File Name If Path and File Name Is Greater Than 256 Characters =

Article ID: 814608

Article Last Modified on 2/28/2007

-

APPLIES TO


 * Microsoft Windows Server 2003, 64-Bit Datacenter Edition
 * Microsoft Windows Server 2003, Enterprise x64 Edition
 * Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)

-



SYMPTOMS
When you add a script to the Logon or Logoff scripts of a Group Policy object, the script may not run when the Group Policy object is applied.

Additionally, when you click Edit in the script Logon Properties or Logoff Properties dialog box, the script name may be truncated.



CAUSE
This issue may occur if both of the following conditions are true:
 * You type a 256-character file name in the Script Name box in the Add a Script dialog box.

-and-
 * You type the path of that script at the beginning of the script name, in the Script Name box.

When you insert the path of the 256-character file name in front the file name, the last portion of that file name is truncated so that the whole path and file name is not greater than 256 characters. Because of this, the script does not work when the Group Policy is applied.



WORKAROUND
To work around this issue, rename the script so that the complete path and file name is not greater than 256 characters.



STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.

Keywords: kbnofix kbpending kbbug KB814608

-

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

© Microsoft Corporation. All rights reserved.