Re: Group Policy Timeout on one server in an OU.
- From: dbondura@xxxxxxxxx
- Date: 7 Dec 2006 10:26:43 -0800
The script is a user logon script, it is just applied to all members of
the domain. GPresult does show it in the user settings: applied GPO
On Dec 7, 1:05 pm, "Darren Mar-Elia" <dmanonym...@xxxxxxxxxxxxx>
wrote:
So the script is a computer startup script and not a user logon script? Does
gpresult show the script and show which GPO its coming from? Another option
here is that you can reduce the timeout before scripts give up by setting
the policy at computer configuration\admin templates\system\scripts\maximum
wait time for GP scripts
--
Darren Mar-Elia
MS-MVP-Windows Server--Group Policyhttp://www.gpoguy.com-- The Windows Group Policy Information Hub:
FAQs, Training Videos, Whitepapers and Utilities for all things Group
Policy-related
Group Policy Management solutions athttp://www.sdmsoftware.com
<dbond...@xxxxxxxxx> wrote in messagenews:1165514346.661268.137600@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
When I run GPResult I can see that GPOs are applied successfully, but
it is still hanging a long time at startup and the terminated GPO error
still rears its head.
On Dec 7, 12:43 pm, "Darren Mar-Elia" <dmanonym...@xxxxxxxxxxxxx>
wrote:
And possibly its a logon script that only applies to certain users that
log
onto that machine. You might just want to run gpresult when that problem
user is logged on to see what the script is.
--
Darren Mar-Elia
MS-MVP-Windows Server--Group Policyhttp://www.gpoguy.com--The Windows
Group Policy Information Hub:
FAQs, Training Videos, Whitepapers and Utilities for all things Group
Policy-related
Group Policy Management solutions athttp://www.sdmsoftware.com
"Roger Abell [MVP]" <mvpNoS...@xxxxxxx> wrote in
messagenews:eSx8fZhGHHA.960@xxxxxxxxxxxxxxxxxxxxxxx
It sounds like a script is not completing.
Perhaps you need to look at what the scripts are doing.
<dbond...@xxxxxxxxx> wrote in message
news:1165505212.004203.294760@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hello,
This problem was brought to my attention late last week, and I have
not
been able to find much useful information to adapt to our setup. The
affected computer is a Windows 2k3 Ent. SP1 machine running Sawmill as
an application server for Sharepoint Analysis by our Web Admin. She
complained it took awhile to login.
The hangup occurs after all the settings are applied, and it hangs on
a
desktop background image, like it is waiting for the Start
Menu/services/etc. to load.
Upon analysis of the event log I found this in the application event
log:
--Execution of GPO scripts has timed out and have been terminated.
That is it. The computer is in AD, in the same OU as about 50 other
servers, and this is the only one having this problem. It will
eventually login once the time limit has been reached.
If I logon with any account local to the server it logs right in.
I can successfully run gpupdate after it logs in, there are no other
errors I get.
I have tried rejoining the machine to the domain, and a few other
tricks, but have been unsuccessful so far.
Any help would be greatly appreciated!
Thanks,
David Bondurant
FSU-College of Medicine
Sys Admin- Hide quoted text -- Show quoted text -- Hide quoted text -- Show quoted text -
.
- Follow-Ups:
- Re: Group Policy Timeout on one server in an OU.
- From: Darren Mar-Elia
- Re: Group Policy Timeout on one server in an OU.
- References:
- Group Policy Timeout on one server in an OU.
- From: dbondura
- Re: Group Policy Timeout on one server in an OU.
- From: Roger Abell [MVP]
- Re: Group Policy Timeout on one server in an OU.
- From: Darren Mar-Elia
- Re: Group Policy Timeout on one server in an OU.
- From: dbondura
- Re: Group Policy Timeout on one server in an OU.
- From: Darren Mar-Elia
- Group Policy Timeout on one server in an OU.
- Prev by Date: Re: Group Policy Timeout on one server in an OU.
- Next by Date: Re: Group Policy Timeout on one server in an OU.
- Previous by thread: Re: Group Policy Timeout on one server in an OU.
- Next by thread: Re: Group Policy Timeout on one server in an OU.
- Index(es):
Relevant Pages
|
Loading