What is the GPO needed to enalbe windows server audit logging for account lockout

Sys Justin 41 Reputation points
2020-08-07T18:37:36.93+00:00

I am trying to identify where a user account lockout keeps happening, by searching for the source in our DC's event logs -> Windows Logs -> Security, but I am not seeing any lock out events in our domain controller. I can see other successful logon/logoff events for all users, but nothing matching ID 4740 User Account Lockout. My hunch is that this is not enabled/being logged, and I was hoping to find the right GPO setting to enable this. Is it the GPO for Computer Policies -> Windows Settings -> Security Settings -> Local Policies -> Audit Policy -> Audit User Account Management ? Or is there another one? Please help!!

Windows
Windows
A family of Microsoft operating systems that run across personal computers, tablets, laptops, phones, internet of things devices, self-contained mixed reality headsets, large collaboration screens, and other devices.
4,746 questions
Windows Server Security
Windows Server Security
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Security: The precautions taken to guard against crime, attack, sabotage, espionage, or another threat.
1,721 questions
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Fan Fan 15,291 Reputation points Microsoft Vendor
    2020-08-10T01:02:44.233+00:00

    Hi,
    Based on experience, you are right .
    If you can't find any events about the account lockout , then we need to enable the audit policy on the Domain controllers under[Computer Configuration\Windows Settings\Security Settings\Local Policies\Audit Policy\Audit account management] 
    You can enable or disable it as your requirements.

    According to the audit events on PDC determine which clients or DCs sent the failed authentication request. If the failed authentication request was sent by a DC, then we should gather the audit event on the DC. So we can find out which clients sent the BAD password.
    After we get the workstations IP, then we need enable Audit Logon Events – Failure and Audit Process Tracking for this client, then analyze the event log to find out which process or apps send the BAD passwod.

    Best Regards,


  2. Jeff Netwrix 1 Reputation point
    2020-09-14T15:31:59.37+00:00

    In the corresponding Group Policy Object (or Local policy if you configured auditing there)

    1. Go to Computer Configuration - Policies - Security Settings - Local Policies - Audit Policy
    2. Make sure Audit Account Management is set to Success
      24591-image.png

    If you use Advanced Audit Policy please check the following setting:

    1. Go to Computer Configuration - Policies - Security Settings - Advanced Audit Policy Configuration - Audit Policies - Account management
    2. Make sure Audit User Account Management is set to Success
      GP1.png

    Even if Group Policy Object is configured correctly there might still be some conflicts that prevent GP from applying correctly.
    To find out the effective audit policy on a DC, execute the following command auditpol /get /category:* In the output check that User Account Management is set to Success

    0 comments No comments

  3. -EviL- 1 Reputation point
    2020-09-14T17:20:26.243+00:00

    Did you check all of the DC's? You can try and use this tool -> https://www.microsoft.com/en-us/download/details.aspx?id=15201 It queries all of the DC's on the network.

    0 comments No comments