Trying to execute a login script (Batch file) 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 suppose the server recognizes the connection as 'slow connection' and therefore don't execute the script for this reason.

http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/Operations/92c46246-7cb7-441e-92d6-2b6671c2980e.mspx

I supposed the same thing so I made the relevant modifications in that particular GPO to process over slow link and set the slow lint detection down to 1Kbit

Have you tried to disable the slow link detection completely?

See link (towards bottem):  http://support.microsoft.com/default.aspx?scid=kb%3BEN-US%3B328991

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

Tried all that but it still doesn't run the script and I get the same message in the event log.

It's not that large but does reside on a remote server so the run time will definatly exceed 10 minutes during busy times.

Is there a solution?

Yes, you can increase the timeout. It's described in the linked technet-article of my post above.

Hi.
If you want to deploy an application, it might be best to have that app install reside on the other LAN, along with the script.
A new Group Policy should be apllied to the other machines over the LAN to LAN VPN link, and that policy should point to the site-local paths for installation.

If you are assigning an .msi package, remember that EVERY time the app is opened on every machine, the LAN to LAN VPN will be used to check the validity of the application and its files, so it's always a good idea to have site-local repositories for packages.

Why not have a deploy application in the user section.  You do it like gpriceee suggested.  Place the source app on a server besides the one you are creating the MSI in if you don't have the msi.  If you have the msi then just place it on a shared folder where everyone can get to it and deploy it under the user section in the GPO and use UNC path names to publish it.  This should provide a better way of deploying the application than using a batch script in the startup folder.

Kevin

Nice one JBlond.
Good spot there.

Problem solved and applications deploying nicely.

J.

I'm glad I could help :)

what was the resolution?

hbpub

I suppose the reolution was to increase the time limit for group policy scripts. The option is called "Maximum wait time for Group Policy scripts". But be VERY careful. If the script terminates or runs not correctly and you set the time limit e. g. to one hour, the users cannot login until the time limit has expired.
BTW the link doesn't point to the correct website anymore.
This link works now... http://technet.microsoft.com/en-us/library/cc757265.aspx