Microsoft KB Archive/812542

= Script You Add to a Windows Server 2003 Policy Does Not Run =

Article ID: 812542

Article Last Modified on 12/3/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)
 * Microsoft Windows Small Business Server 2003 Premium Edition
 * Microsoft Windows Small Business Server 2003 Standard Edition

-





SYMPTOMS
When you extend a Windows Server 2003 policy by including a script file, the script may not run when the policy is called.



CAUSE
When you add a script to a policy, you can browse the network to indicate the location of the script. The Browse feature formats the location of your script file by using the universal naming convention (UNC). Locating network resources by using the UNC format requires NetBIOS name resolution on the network.

If your network does not provide Windows Internet Name Service (WINS) resolution services or if the script is stored in a server that requires the policy to cross Active Directory directory service Forest trust relationships, the UNC cannot be successfully resolved, and retrieval of the script does not work.



RESOLUTION
To resolve this issue, type the fully-qualified domain name (FQDN) when you indicate the network location of your script. For example, \\. \ \, where  is the name of the network server,   is the name of the DNS domain, and   is the name of the script file.



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

Keywords: kbbug KB812542

-

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

© Microsoft Corporation. All rights reserved.