Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 254
  • Last Modified:

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?
0
mhmservices
Asked:
mhmservices
  • 2
  • 2
  • 2
  • +1
3 Solutions
 
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
 
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
Lessons on Wi-Fi & Recommendations on KRACK

Simplicity and security can be a difficult  balance for any business to tackle. Join us on December 6th for a look at your company's biggest security gap. We will also address the most recent attack, "KRACK" and provide recommendations on how to secure your Wi-Fi network today!

 
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

Featured Post

Configuration Guide and Best Practices

Read the guide to learn how to orchestrate Data ONTAP, create application-consistent backups and enable fast recovery from NetApp storage snapshots. Version 9.5 also contains performance and scalability enhancements to meet the needs of the largest enterprise environments.

  • 2
  • 2
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now