Event ID:1217 (Winlogon) Execution of GPO scripts has timed out and ha

[laingo]

Hi all,
I'm trying to execute a login script via Group Policy to deploy an application but I get Event ID:1217 (Winlogon) Execution of GPO scripts has timed out and have been terminated.
I am on win server 2003 (Active Directory) and xp SP2 for clients.
Thanks

 

[IllogicallyLogical]

Try increasing the timeout value for Group Policy scripts under your Default Domain Policy. Look for this policy setting...

Computer Configuration\Administrative Templates\System\Scripts

"Maximum wait time for Group Policy scripts"

The default timeout value is ten minutes or 600 seconds. Try increasing the timeout to something more than 600 seconds.



Joey
CCNA, MCP, A+, Network+, Wireless#

 

[Dman33]

IllocigallyLogical, you are correct in suggesting how to increase the GPO script processing timeout value however should it be normal to allow your GPO scripts to process for over 10 minutes?

Laingo may first want to determine the type of network. Is this a remote network with a WAN infrastructure? Is VPN involved? If so, then yes it is likely that there is a script or install processing over a slow link causing the timeout. In this case, IllogiallyLogical's suggestion is spot-on.

If the network is a simple single office then there is a bad script processing and possibly falling into a loop or something causing a timeout.

If the latter is the case, I would suggest doing some GPO troubleshooting. Sure, it is not as quick and easy as modifying a single registry value but at least this way you are fixing the problem, not just dusting it under the rug - so to speak.

 

[laingo]

Hi ,
illogicallylogical's suggestion is the solution of my pbm.
Now it works fine.
Thanks for all

 

[laingo]

Hi again,
I have this another pbm with some of my clients XP SP2 behavior when executing the logging script.
More exactly,
I programmed through GPO some installations that are supposed to occur before the logon screen (CTRL,ALT,SUPPR)shows, i.e. applied on startup on the computer configuration policy.
In most cases, when the computer starts up,the installation occurs but users can already log on windows despite the installation isn’t finished yet.

So, my question: is there any workarounds to this and deny user logon ability until the install process finishes completely!

Thanks

 

[IllogicallyLogical]

Prevent the XP computers from using the Fast Logon feature. Look under this policy setting...

Computer Configuration\Administrative Templates\System\Logon

"Always wait for the network at computer startup and logon"

Enable this policy for the domain. This will require users to wait for the network to be fully initialized before they are able to login. By default, Windows XP does not wait for the network to come up, Windows 2000 does on the other hand. You may wish to return this policy back to "Not configured" after you deploy your application so your users can continue to log in quickly. Leaving this policy as "Not configured" will also allow them to login to their computers and access their files with cached credentials in the event that the DC is down. But, if you want your users to have to wait for Group Policy to be applied at all times before they are able to login, then leave this policy enabled.

The article below provides some good information on how Group Policy is processed.

- Group Policy Processing

http://technet2.microsoft.com/windo...a909-4f61-aded-c5b69f5f730b1033.mspx?mfr=true

Joey
CCNA, MCP, A+, Network+, Wireless#

 

[laingo]

Again, it works fine.:-D
thank u illogicallylogical