Intermittant GPO failure to apply



We have a problem on our workstations whereby around half of the time the
GPOs do not apply correctly but running 'GPUpdate /force' always temporarily
fixes the problem. Sometimes I can get all the workstations GPOs working
correctly then a few hours later they start failing without even rebooting!
Sometimes the machine boots and the GPOs are applied even before a user has
logged on, is that correct? When are GPOs supposed to be applied?

This manifests itself in Windows Firewall problems when the Firewall
settings Group Policy does not get applied correctly and the Firewall
reverts to its XPsp2 defaults. When that happens I find that the server
cannot remotely manage these workstations, in fact they can't even be
pinged.

Any suggestions on how I can diagnose this problem?

Nick


.



Relevant Pages

  • Re: How to ... 2nd request
    ... > I appreciate your clarification and views on my answer Glenn. ... >> OUs and GPOs, ... >> There are two policies you can set to acheive the desired results. ... >> the workstations will not revert back to their default state. ...
    (microsoft.public.windows.server.general)
  • Re: How to ... 2nd request
    ... > I appreciate your clarification and views on my answer Glenn. ... >> OUs and GPOs, ... >> There are two policies you can set to acheive the desired results. ... >> the workstations will not revert back to their default state. ...
    (microsoft.public.windows.server.active_directory)
  • RE: Intermittant GPO failure to apply
    ... DNS from an abandoned server, and sysvol shares pointing to a different drive ... Sometimes I can get all the workstations GPOs working ... > This manifests itself in Windows Firewall problems when the Firewall ...
    (microsoft.public.windows.server.sbs)
  • Re: How to ... 2nd request
    ... > OUs and GPOs, ... > There are two policies you can set to acheive the desired results. ... > And yet another caveat to policies under the security node. ... > the workstations will not revert back to their default state. ...
    (microsoft.public.windows.server.active_directory)
  • Re: How to ... 2nd request
    ... > OUs and GPOs, ... > There are two policies you can set to acheive the desired results. ... > And yet another caveat to policies under the security node. ... > the workstations will not revert back to their default state. ...
    (microsoft.public.windows.server.general)