This tip was submitted to the SearchWin2000.com tip exchange by member Mark Bagley. Let other users know how useful...
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
it is by rating it below.
You can centrally track domain user logon attempts by using the audit setting "audit account logon events." This setting generates a security event log entry whenever the computer on which the setting is active authenticates a user who is logging onto a different computer. By setting this on at a domain controller, any user logon attempts that are serviced by the domain controller will be recorded in the domain controller security event log. The event log entry will indicate whether the user was successful or not at logging in.
The most important successful event IDs are:
The most important error event IDs are:
These events also contain extremely useful information such as:
The good news is that no matter what workstation a user logs onto, the event will be recorded at the authenticating domain controller.
The bad news is that it could be on any domain controller for the domain hosting the user's account. However, it is much easier to look at a few domain controller event logs than all of the workstation or server event logs (as was the case before this setting was available).
Note that in addition to recording the user logon attempts, this setting also ensures that computer account logon attempts are recorded. You can make the setting effective on all domain controllers by modifying group policy on the domain controller's OU --> Computer ConfigurationWindows SettingsSecurity SettingsLocal PoliciesAudit PolicyAudit Account Logon Events.