The IT administrators often need to know who logged on to their computers and when for security and compliance reasons. Although you can use the native auditing methods supplied through Windows to track user account logon and logoff events, you may end up having to sift through thousands of records to reach the required log. Once you’ve found the required log, getting the required information for compliance and security reports is not an easy process.
In this article, you will learn how to audit who logged into a computer and when. You will also learn about an easier way in which you can audit logon/logoff events with LepideAuditor.
You can do this through two GPO settings:
Audit Logon Events: This setting generates events for starting and ending logon sessions. These events happen on the machine where you log in.
Audit Account Logon Events: This setting generates events on the computer that validates logons. When a domain controller authenticates a domain user account, events are generated and stored on that domain controller.
1. Open “Group Policy Management” console by running the “gpmc.msc” command.
2. If you want to configure auditing for the entire domain, right-click on the domain and click “Create a GPO in this domain, and Link it here…”.
3. Create a new GPO dialog box appears on the screen. Enter a new GPO name.
4. Go to the new GPO, right-click on it, and select “Edit” from the context menu.
5. “Group Policy Management Editor” window appears on the screen.
6. In the navigation pane, go to “Computer Configuration” ➔ “Policies” ➔ “Windows Settings” ➔ “Security Settings” ➔ “Local Policies” ➔ “Audit Policy”.
7. In the right pane, double-click “Audit logon events” policy to open its properties window.
8. Select the “Success” and “Failure” checkboxes, and click “OK”.
9. Similarly, you have to enable “Success” and “Failure” for “Audit Account Logon Events”.
10. Close “Group Policy Management Editor”.
11. Now, you have to configure this new Group Policy Object (containing this audit policy) on all Active Directory objects including all users and groups. Perform the following steps.
- In “Group Policy Management Console”, select the new GPO (containing above change).
- In “Security Filtering” section in the right panel, click “Add” to access “Select User, Computer or Group” dialog box.
- Type “Everyone”. Click “Check Names” to validate this entry. Click “OK” to add it and apply on all objects.
12. Close “Group Policy Management Console”.
13. Now, run following command to update GPO. gpupdate /force
After you have configured log on auditing, whenever users logon into network systems, the event logs will be generated and stored. To find out the details, you have to use Windows Event Viewer. Follow the below steps to view logon audit events:
1. Go to Start ➔ Type “Event Viewer” and click enter to open the “Event Viewer” window.
2. In the left navigation pane of “Event Viewer”, open “Security” logs in “Windows Logs”.
3. You will have to look for the following event IDs for the purposes mentioned herein below.
- 4624 – A successful account logon event
- 4625 – An account failed to log on
- 4648 – A logon was attempted using explicit credentials
- 4634 – An account was logged off
- 4647 – User initiated logoff
For user logon, you have to search for 4624 and 4648 event IDs. For failed logon, you have to search for 4625. For logoff events, you have to search for 4634 and 4647.
4. In this article, we are searching for events 4624 and 4648. The following screenshot shows Windows Event ID 4648 for the user logon attempted using explicit credentials.
Using LepideAuditor for auditing User Logon/Logoff events
Using LepideAuditor for Active Directory, you can easily monitor a user’s log on and log off activity (avoiding the complexities of native auditing). The solution collects log on information from all added domain controllers automatically. Its report contains details on logon or logoff events, including when users logged in, from which computer, and when. You get accurate and instant reports on login details of users in the network. The following screenshot shows a successful user logon report event captured by LepideAuditor:
In this article, the steps to audit the user logon and logoff events through native auditing are explained. However, much noise is generated for the logon or logoff events that make it complicated for the IT administrators to have a real-time view. The easiest and more efficient way to audit the same with LepideAuditor has also been explained. To try LepideAuditor for yourself, download the free trial version today.
- How to identify the source of Account Lockouts in Active Directory
- How to Audit Successful Logon/Logoff and Failed Logons in Active Directory
- How to enable the Security Auditing of Active Directory
- How to track changes made in Active Directory
- How to delegate rights to “Unlock account”
- How to track Privileged Users' Activities in Active Directory