This article was previously published under Q275506
This article has been archived. It is offered "as is" and will no longer be updated.
When you configure logon scripts, there are settings that allow an administrator to control the maximum time the logon script is allowed to run, and whether to run the logon script synchronously. When a logon script is run synchronously, the user does not have access to the desktop until the logon script terminates.
The setting that controls the length of time a logon script is allowed to run is "Maximum wait time for Group Policy scripts", and this setting is in seconds. If this setting is greater than 10 minutes (600 seconds), and the script is running synchronously, the user is given access to their desktop after 10 minutes even though the logon script has not completed. For a synchronous logon script, the user should not have access to their desktop until after the logon script terminates.
This problem can occur because a timer is hard coded to a 10 minute setting. When this timer activates, the desktop is presented to the user, even though the logon script is still running.
To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack
The English version of this fix should have the following file attributes or later:
Date Time Version Size File name -------------------------------------------------------- 10/26/2000 03:07p 5.0.2195.2578 177,936 Winlogon.exe
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 Windows 2000 Service Pack 2.
For additional information about how to install Windows 2000 and Windows 2000 hotfixes at the same time, click the article number below to view the article in the Microsoft Knowledge Base:
249149 Installing Microsoft Windows 2000 and Windows 2000 Hotfixes
The timer is no longer a hard-coded value. This hotfix modifies the timer so it is now "aware" of the "Maximum wait time for Group Policy scripts" setting.