Script Policy Is Not Run When a Slow Link Is Detected

If you use a Group Policy object (GPO) to set logon scripts, the logon scripts do not run when a slow link is detected. This behavior occurs even if you perform the following procedure:

1. Enable the Scripts Policy Processing policy setting. This policy setting has three options:
   • Allow processing across a slow network connection
   • Do not apply during periodic background processing
   • Process even if the Group Policy objects have not changed
2. You click to select the Allow processing across a slow network connection check box.

The client side extension (Gptext.dll) uses the following two internal flags to decide to run the script:

• The slow link flag
• The link transition flag

During the first logon, the extension's DLL entry routine (ProcessScriptsGroupPolicy) is called and these two flags are passed. If both flags are set, this routine quits without running the logon scripts. During the second logon, the extension's DLL entry routine may not be called because the GPO has not been changed since the first logon. Therefore, the following registry key is still not set:

Service Pack Information

To resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

Hotfix Information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language. The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

As a partial workaround, you can enable Scripts Policy Processing and then click to select the Process even if the Group Policy objects have not been changed check box. However, if you perform this workaround, two issues occur:

• The script is not run during the initial logon (the first time that the user logs on to a specific computer).
• The script is not run the first time that the link is detected as slow. Additionally, the script is not run after the first transition (from high link to slow link). However, after this transition (if the link is detected continuously as slow), the script always runs.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Windows 2000 Service Pack 4.

Important To make sure that the logon script runs, enable the Scripts Policy Processing policy setting, and then click to select the following check boxes:

• Allow processing across a slow network connection
• Process even if the Group Policy objects have not been changed

For additional information about how to obtain a hotfix for Windows 2000 Datacenter Server, click the article number below to view the article in the Microsoft Knowledge Base: