GPO not taking effect

I have recently added a GPO that enables account logon events to be logged on all workstations. I have created/linked/enabled the GPO and made the proper configs in the audit policy. I ran gpupdate /force on the server and workstation but my settings are not taking effect. What am I doing wrong?
mhmservicesAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

willettmeisterCommented:
You must have a GPO higher in precedence that is setting a conflicting policy.  Run gpresult against the traget workstation and look at the GPO's that are being applied and check to ensure that nothing is conflicting with your new policy.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
mhmservicesAuthor Commented:
It is saying that it was "filtered out"
0
snoopfroggCommented:
Like willettmeister referred to, do you have other GPOs with auditing settings enabled or disabled?  Does the GPO you created have any filtering enabled via security group or user permissions?  Are WMI filters in use on the GPO?
0
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

willettmeisterCommented:
You must be using either security filtering or WMI filtering then  Check the GPO to ensure that you are in the correct security group or that the the system you are looking at satisfies the WMI query.
0
MightySWCommented:
Yes, it was filtered out because the default domain policy is conflicting.  You need to either create another OU, block inheritance, and then link that OU or have it overwritten by the Default Domain Policy.
0
MightySWCommented:
Also, you need to just ensure that you apply it to authenticated users...Don't get fancy with groups when you are trying to troubleshoot GPO's.

Create the separate OU or change the security / audit settings in the Default Domain Policy.  
0
snoopfroggCommented:
I'd definitely stay away from filtering via security principals as it makes troubleshooting issues like this more difficult.  I prefer to use WMI or the methods MIghtySW mentioned (create another OU, or block inheritance).
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
OS Security

From novice to tech pro — start learning today.