Are the global groups being used inside Group Policy Preferences, or in the Security Filtering section of GP? If you are using the Security Filtering in GP, then the CSEs should not apply here afaik.
Personally, I try to avoid using groups with computers in them since new computers do not automatically get those policies. I instead try to segment computers like this into a separate OU, or use WMI filtering (depending on the need). -Aakash Shah From: [email protected] [mailto:[email protected]] On Behalf Of Rankin, James R Sent: Wednesday, January 8, 2014 11:01 AM To: [email protected] Subject: Re: [NTSysADM] Computer Group Policy not applied to XP The Client-Side Extensions hotfix is what you need Sent from my (new!) BlackBerry, which may make me an antiques dealer, but it's reliable as hell for email delivery :-) ________________________________ From: Steve Norton <[email protected]<mailto:[email protected]>> Sender: [email protected]<mailto:[email protected]> Date: Wed, 8 Jan 2014 18:56:10 +0000 (UTC) To: <[email protected]<mailto:[email protected]>> ReplyTo: [email protected]<mailto:[email protected]> Subject: [NTSysADM] Computer Group Policy not applied to XP 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
