<div>
Sounds like the wizard has already given you the problem. None of the security groups associated with the policy have the AD object you want to apply as a member. A WMI filter issue would report differently.
</div>


<div>
Those users \ computers to whom you wanted to apply GPO through security filtering must need to be in same OU \ sub OU in the hierarchy as GPO, meaning it will not work if the OU on which you applied GPO is different from OU that contains actual user\computer<br />
<br />
I think that is the issue here<br />
<br />
Mahesh
</div>


<div>
thanks for your input<br />
<br />
&gt;&nbsp;Those users \ computers to whom you wanted to apply GPO through security <br />
&gt;&nbsp;filtering must need to be in same OU \ sub OU in the hierarchy as GPO, meaning<br />
&gt;&nbsp;it will not work if the OU on which you applied GPO is different from OU that<br />
&gt;&nbsp;contains actual user\computer<br />
<br />
I confirm that both the intended users and the GPO are in the same OU<br />
<br />
&gt;&nbsp;None of the security groups associated with the policy have the AD object you want <br />
&gt;&nbsp;to apply as a member. A WMI filter issue would report differently. <br />
<br />
Not sure I understand your point. Here is what I have<br />
<br />
OU = myComp<br />
<br />
in said OU I have a group - say gTargetGPO with some user of the OU<br />
<br />
I also have a GPO under myComp. I have set it apply to gTargetGPO.<br />
<br />
What am I missing ?!
</div>


<div>
Not sure if this is orphaned GPOs issue<br />
please download PowerShell script in below link and find orphaned GPOs<br />
<a href="http://www.jhouseconsulting.com/2012/09/03/finding-orphaned-group-policy-objects-807" rel="ugc">http://www.jhouseconsulting.com/2012/09/03/finding-orphaned-group-policy-objects-807</a><br />
Just remove those orphaned GPOs and check if now GPOs are applying correctly<br />
<br />
Check below thread for complete information<br />
<a href="https://www.experts-exchange.com/questions/28309861/GPO-on-Window-2003.html" rel="ugc">https://www.experts-exchange.com/questions/28309861/GPO-on-Window-2003.html</a><br />
<br />
Mahesh
</div>


<div>
<div class="content wysiwyg-content">
I am having an issue with a GPO not executing as expected (it's a pretty simple drive mapping policy but anyhow I guess the content itself is irrelevant).<br />
<br />
Using the &quot;GPO modeling&quot; wizard I see that said GPO is not executing because it has a denied access (security filtering) issue.<br />
<br />
I muss confess I can't figure out why it would not be readable in this context (user / machine).<br />
<br />
Is there any way to explicitly find out what mechanism is blocking this GPO ?<br />
<br />
Thanks for any pointer / advice in the matter (this is w2k8 domain)
</div>
</div>


I am having an issue with a GPO not executing as expected (it's a pretty simple drive mapping policy but anyhow I guess the content itself is irrelevant).

Using the "GPO modeling" wizard I see that said GPO is not executing because it has a denied access (security filtering) issue.

I muss confess I can't figure out why it would not be readable in this context (user / machine).

Is there any way to explicitly find out what mechanism is blocking this GPO ?

Thanks for any pointer / advice in the matter (this is w2k8 domain)

GPO not accessible issue

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.

Active Directory

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.