GPOs only applying once a day
- From: "Russ Oliver" <tick-removethis@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 28 Mar 2007 13:21:31 -0600
Short problem description:
I have 1200 systems that are on 24/7 and rebooted once a day between 3 and
4am when an update script is run (I know, but it isn't my decision).
Policies typically (with few exceptions) apply
at that reboot. If a system is rebooted during the day, policies usually
don't apply (although some exceptions apply). Or if a system is reboot at
11pm, the 3am reboot doesn't get policies applied. Basically, policies are
applied once a day. Any attempts made by rebooting the system beyond that
will not re-apply policies.
Long problem description:
I have policies blocked in an OU that contains roughly 1200 computers. I
apply a couple policies to that OU and to OUs beneath it. As I said above,
these systems get rebooted at least once a day, sometimes more depending on
the situation. The policies are only applied once a day, although I don't
know exactly the amount of time it waits until a reboot will finally apply
the policy. It could be 16 hours, for all I know.
If I make a change to a policy, save it, and then reboot the system, then
that policy will apply again as expected, but only the first time. After
that I have to wait until the next day for it to apply.
I've looked at the winlogon.log and see nothing relating to a failure. I've
turned on verbose logging for the userenv, too. In the userenv.log file, I
can compare one from a boot that applies the policy and one that does not
apply the policy. They are identical up until the line that policies begin
to apply. Then in the log that policies applied, you can see where things
are working. That portion just doesn't exist in the log where policies did
not apply. Once the policies have applied in the first, the next line in
the log picks up and continues just the same as in the second log. The
policy stuff just doesn't exist in the second. No warnings, errors,
failures, attempts...nothing. That segment of logging just isn't in the
second log. Along with that, there is nothing in the event log relating to
GP failures, either.
I see no policies that would make this happen, either. Is it possible I
have a corrupt policy set somewhere?
I'm at a loss and I have no idea where else I should be searching. Any
ideas on how I can trace this or if you know of any possible causes, I'd be
forever in your debt.
thanks,
Russ Oliver
Systems Programmer
Information Technology
University of Wyoming
.
- Follow-Ups:
- Re: GPOs only applying once a day
- From: Norbert Fehlauer [MVP]
- Re: GPOs only applying once a day
- Prev by Date: Re: Using loopback and group filtering together
- Next by Date: Re: GPOs only applying once a day
- Previous by thread: reset policy
- Next by thread: Re: GPOs only applying once a day
- Index(es):
Relevant Pages
|