Event ID 1217
- On some of our Windows XP Pro SP3 clients we are getting the following - warning message in the application log:
Event Type: Warning
Event Source: Winlogon
Event Category: None
Event ID: 1217
Date: 9/26/2008
Time: 12:08:57 PM
User: N/A
Computer: XXXXXXXXXXX
Description:
Execution of GPO scripts has timed out and have been terminated
Is there any way in terms for GPO settings we can increase the time out value on the clients?
Answers
Hi,
Please understand that how much time the script needs to run does not depend on the size of the script.
In this case, I suspect that this issue occurs because the client machine cannot complete the tasks in the script. I suggest that you run the script manually on the machine encountering the issue and check if the script completes successfully.
If the script completes successfully and it does consume more than 10 minutes, you may configure the policy "Maximum wait time for Group Policy scripts" as Florian suggested.
If the script fails to complete, you can identify the issue according to the error message.
Hope it helps.
- Marked As Answer byJoson ZhouMSFT, ModeratorMonday, October 06, 2008 1:59 AM
All Replies
- Howdie!
See: http://technet.microsoft.com/en-us/library/cc757265.aspx
"Maximum wait time for Group Policy scripts". Before messing around with that setting I'd first check if you can't do anything with your script so that they don't run into those timeouts. Most of the scripts that run into timeouts that I've seen were involved with tasks that were better triggered with a scheduled task in the background.
cheers,
Florian
Microsoft MVP - Group Policy -- blog: http://www.frickelsoft.net/blog - If the default interval is 10 minutes or do we have to set this in order for it to go to the default, it should run almost 100% of the time. The script is only 49 K runs under the User configuration. We are only searching for the username and then mapping drives. We are only getting this warning on a couple of clients within our domain.
Do you have any other options where we could set drive mapping for an user? We thought the logon script would be our best option.
Is there anything else in terms of GPO to help this situation? - Howdie!
Have you rolled out the "Always wait for the network" policy?
Generally, mapping drives with a script is a common approach - I wonder why it would take that long. You should really check whether the "Always wait for the network" policy helps. In addition - how large is the script. How do you go about "searching for the user name" and then map the drives? Any special applications/exe files used in there that may run into a time out?
cheers,
Florian
Microsoft MVP - Group Policy -- blog: http://www.frickelsoft.net/blog - Yes, we have that setting set on the computer conifguration policy.
Our script gets the username and then uses if statements to assign the mapped drives accordingly to the username. the script is not that large so that is what I cannot understand. - Okay --
I've seen the following help. Not sure if that solves the problem you encounter:
http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/gp/10.mspx?mfr=true
cheers,
Florian
Microsoft MVP - Group Policy -- blog: http://www.frickelsoft.net/blog - We do have this set to enabled, so from what I read we should set that setting to disabled, is that a true statement, these group policy settings are very confusing.
Hi,
Please understand that how much time the script needs to run does not depend on the size of the script.
In this case, I suspect that this issue occurs because the client machine cannot complete the tasks in the script. I suggest that you run the script manually on the machine encountering the issue and check if the script completes successfully.
If the script completes successfully and it does consume more than 10 minutes, you may configure the policy "Maximum wait time for Group Policy scripts" as Florian suggested.
If the script fails to complete, you can identify the issue according to the error message.
Hope it helps.
- Marked As Answer byJoson ZhouMSFT, ModeratorMonday, October 06, 2008 1:59 AM
Yes, we have that setting set on the computer conifguration policy.
Our script gets the username and then uses if statements to assign the mapped drives accordingly to the username. the script is not that large so that is what I cannot understand.
If you're assigning a COMPUTER policy vs. a USER policy, this might be your issue... %USERNAME% is going to be system during boot (pre-user login). You have to map drives under a user context - they're per user.
-Adam
http://www.adamanthony.net/adama/?tab=C
