Event 4740 Not Logged for a Single Account Lockout

Question

Domain Functional Level: 2003
PDC Emulator: 2008 R2
Lockout Origin DC (also the RADIUS server): 2003 R2
For quite a while now I have been relying on Event 4740 on the PDC Emulator to track account lockouts.  Usually when the RADIUS server causes an account lockout, the Caller Computer Name is blank in the Event 4740.  This usually tells me that our
Cisco WLAN Controller caused the lockout.
Our Default Domain Policy is set to audit Account Logon Events for failure, Account Management for success/failure, and Logon Events for success/failure (plus numerous other things).
This time there is no Event 4740 for this account lockout and I can't figure out why.  The events are there for other lockouts several minutes before or after this one.  Windows just hates me so it decided to skip this one.  The main reason
this is a problem is because I just set up Scheduled Task on the PDC Emulator, triggered by Event 4740, to run a PowerShell script that will provide the help desk with a report for each account lockout, even parsing the IIS logs on the Client Access Server
to identify which ActiveSync device caused it.  Of course the week after I announce that, Windows decides not to log one.
Using LockoutStatus.exe I determined that the Origin DC for the lockout was the RADIUS server.
NetLogon debug logging is enabled on the RADIUS server, however I took a nap today after being let out of work early for the holiday so by the time I checked the netlogon.bak file it had already been overwritten with newer data.
There was, however, an Event 644 locked on the RADIUS server (pasted below with domain/computer/user details edited for privacy).  I don't even know where to start as far as trying to prevent this from happening again.  Anyone have any suggestions?
 Within the next couple months I will spin up a 2012 RADIUS server and a separate 2008 R2 DC to replace the 2003 multipurpose server, but it's not high on my boss's priority list so it's a tough sell considering the WLAN is functional right now.
Event Type: Success Audit
Event Source: Security
Event Category: Account Management 
Event ID: 644
Date: 12/31/2014
Time: 10:00:35 AM
User: NT AUTHORITY\SYSTEM
Computer: DomainControllerAndRadiusServer
Description:
User Account Locked Out:
Target Account Name:
LockedOutUser
Target Account ID:
DOMAIN\LockedOutUser
Caller Machine Name:
CISCO
Caller User Name:
DomainControllerAndRadiusServer$
Caller Domain:
DOMAIN
Caller Logon ID:
(0x0,0x3E7)
For quite a while now I have been relying on Event 4740 on the PDC Emulator to track account lockouts.  Usually when the RADIUS server causes an account lockout, the Caller Computer Name is blank in the
Event 4740.  This usually tells me that our Cisco WLAN Controller caused the lockout.
For quite a while now I have been relying on Event 4740 on the PDC Emulator to track account lockouts.  Usually when the RADIUS server causes an account lockout, the Caller Computer Name is blank in the
Event 4740.  This usually tells me that our Cisco WLAN Controller caused the lockout.
For quite a while now I have been relying on Event 4740 on the PDC Emulator to track account lockouts.  Usually when the RADIUS server causes an account lockout, the Caller Computer Name is blank in the
Event 4740.  This usually tells me that our Cisco WLAN Controller caused the lockout.

Answer 1

Hi,
I suggest you use Auditpol command to check the current auditing status on Domain Controller.
You can type this command below:
Auditpol /get /Category:Logon/Logoff
If the Account Lockout subcategory is set to no auditing, please use /set option to enable auditing:
Auditpol /set /Subcategory:”Account Lockout” /Success:enable /Failure:enable
More information for you:
Auditpol
http://technet.microsoft.com/en-us/library/cc731451.aspx
Best Regards,
Amy
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]