RE: Rid Machine of GPO No Longer Applied
- From: Baboon <baboon@xxxxxxxxxxxxxx>
- Date: Sun, 25 Jan 2009 19:26:00 -0800
That article is mainly about troubleshooting failure of Group Policy for
multiple computers or users, as opposed to the problem I am describing which
is when a single computer in an OU is having GP problems. However, there is
a link in the article to a KB article which gave me some information that is
new to me. It says to look for a disabled DFS client service, an ACL on the
root of the System Drive that doesn't include Everyone and even a disabled
Server service. I'll take a look at those things on the trouble machines.
Thanks.
"Michael" wrote:
Check that these machines are properly properly processing group policy..
http://www.windowsnetworking.com/articles_tutorials/Troubleshooting-Group-Policy-Processing.html
"Baboon" wrote:
I see some behavior on the occassional XP client where it appears a machine
continues to process a GPO that no longer applies to it.
For example, I see a few machines that continue to contact a WSUS server
every day even though their linked GPOs no longer point them to a WSUS
server. In another case, it seems that one machine out of 20 in an OU keeps
trying to process a GPO that is linked to a parent OU, but where the link is
disabled.
I hope this is pretty straightforward - What can I do on problem machines to
get them to stop processing these GPOs? Or am I misunderstanding what is
going on?
Thanks.
- References:
- Rid Machine of GPO No Longer Applied
- From: Baboon
- RE: Rid Machine of GPO No Longer Applied
- From: Michael
- Rid Machine of GPO No Longer Applied
- Prev by Date: Re: Printer Script by OU 2008 TS
- Next by Date: Loopback processing, event id userenv 1087
- Previous by thread: RE: Rid Machine of GPO No Longer Applied
- Next by thread: Re: Rid Machine of GPO No Longer Applied
- Index(es):
Relevant Pages
|