Re: [NTSysADM] Computer Group Policy not applied to XP

[Steve Norton]

On my test unit I can disjoin and rejoin the domain and take the steps you indicated but to do that to all the remaining XP machines would not be feasible.

 

This whole thing started when I attempted to move WSUS away from the Default Domain Policy which has the default Authenticated Users Security Filtering. If I give Authenticated Users access to Apply Group Policy for the default Domain Policy (and consequently apply WSUS computer settings) it works fine on both XP and Windows 7 workstations.

 

Steve

---

From: "Aakash Shah" <aakash.s...@uci.edu>
To: ntsysadm@lists.myitforum.com
Sent: Wednesday, January 8, 2014 3:03:55 PM
Subject: RE: [NTSysADM] Computer Group Policy not applied to XP

I was going to indicate that it’s having a problem getting policies, but since it is working when you add the computer directly to the GP, that is odd. 

 

Is disjoining and rejoining the domain an option?  If so, please try that.  I would consider disjoining AD, deleting the computer from AD, rejoining AD, and then adding this new computer object to the security group to see if it helps.

 

Also, does this work if you move this computer to a new OU and apply a similar GP that has default security filtering (Authenticated Users)?  And since you are a few months out from getting rid of these computers, is moving them into a new OU and targeting a GP to just this OU an option?

 

-Aakash Shah

 

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Steve Norton
Sent: Wednesday, January 8, 2014 11:50 AM
To: ntsysadm@lists.myitforum.com
Subject: Re: [NTSysADM] Computer Group Policy not applied to XP

 

GPOs show not being applied in gpresult. Also the XP machines do not show as being part of the security group in gpresult but the Windows 7 do. RSOP show no computer settings applied. Group Policy shows Inaccessible in Group Policy Results.

 

Also when I add the computer to the Global Security Group it shows as COMPUTERNAME and does not work. When I add it directly to Security Filtering it resolves as COMPUTERNAME$.

 

Thanks.

 

Steve

 

---

From: "Christopher Bodnar" <christopher_bod...@glic.com>
To: ntsysadm@lists.myitforum.com
Sent: Wednesday, January 8, 2014 2:31:48 PM
Subject: Re: [NTSysADM] Computer Group Policy not applied to XP

 

OK are the GPO's getting applied but the settings don't take affect, or are the GPO's not showing as being applied in the output of GPRESULT ? There is a difference. What does it look like when you do an RSOP, either locally from the client or in GPM?

Christopher Bodnar Enterprise Architect I, Corporate Office of Technology:Enterprise Architecture and Engineering Services

Tel 610-807-6459   3900 Burgess Place, Bethlehem, PA 18017 christopher_bod...@glic.com

The Guardian Life Insurance Company of America www.guardianlife.com

From:        Steve Norton <chipsh...@comcast.net>
To:        ntsysadm@lists.myitforum.com
Date:        01/08/2014 01:58 PM
Subject:        [NTSysADM] Computer Group Policy not applied to XP
Sent by:        listsad...@lists.myitforum.com

---

Computer Group Policy from 2008 R2 SP1 fails when applied to XP SP3 using Global security groups. Windows 7 workstations in the same security group process the computer policy fine. If I add the XP workstations manually to Security Filtering they work fine. What am I missing?
 
Thanks.
 
Steve
----------------------------------------- This message, and any attachments to it, may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are notified that any use, dissemination, distribution, copying, or communication of this message is strictly prohibited. If you have received this message in error, please notify the sender immediately by return e-mail and delete the message and any attachments. Thank you.