Summary
After you enable folder auditing on a Windows Server 2019 file server, audit events don't appear in Event Viewer. This article helps you identify and fix common configuration issues that prevent folder audit events from being recorded.
Symptoms
You configure folder auditing to monitor a folder on a Windows Server 2019 file server for access and change operations. However, you don't see the audit events that you expect to be logged in Event Viewer. Additionally, you don't see any events or error codes that indicate an auditing issue.
Cause
This issue can occur if audit policies or permissions are incomplete or incorrectly configured on the file server. Windows Server 2019 doesn't generate the folder access or change audit logs unless the audit policy settings and folder-specific audit entries are correctly configured.
Resolution
To configure folder auditing, follow these steps.
Step 1: Verify the audit policy settings
-
If you use Group Policy objects (GPOs) to manage your configuration, follow these steps to find the correct settings:
- On a domain controller (DC), open Server Manager, and then select Tools > Group Policy Management.
- Open or create a Group Policy object (GPO) that links to the affected computer. To open the Group Policy Management Editor, right-click the GPO, and then select Edit.
- In the editor, select Computer Configuration > Policies > Windows Settings > Security Settings > Advanced Audit Policy Configuration > Audit Policies > Object Access.
-
If you don't configure GPOs, and you use Group Policy at the local level, follow these steps to find the correct settings:
- On the affected computer, select Start, type gpedit.msc, and then select Edit group policy from the search results.
- In the editor, select Computer Configuration > Windows Settings > Security Settings > Advanced Audit Policy Configuration > System Audit Policies - Local Group Policy Object > Object Access.
-
Right-click the policy that you want to enable (such as Audit File System), and then select Properties.
-
Make sure that Configure the following audit events is selected, and that the types of events that you want to audit are selected (Success, Failure, or both).
-
On the affected computer, open an administrative Command Prompt window.
-
To force the computer to update its Group Policy settings, run the following command at the command prompt:
gpupdate /force
Step 2: Configure the user or group for whom you want to audit folder usage
- In File Explorer on the affected computer, right-click the target folder, and then select Properties.
- Select Security > Advanced > Auditing.
- On the Auditing tab, add the user or group whose access you want to audit.
- Select the types of access that you want to audit (for example, Create files/write data or Read data/list folder).
- Select whether to audit successful attempts, failed attempts, or both.
Step 3: Verify that audit logging is working
-
On the affected computer, verify that the Windows Event Log service is running.
-
To verify that the computer is recording folder access events, open Event Viewer, and then select Windows Logs > Security.
-
To test the auditing configuration, use an account that matches the auditing rules to access or change the target folder.
The audit events that document your actions should now appear in Event Viewer.
Data collection
The following types of data can help you troubleshoot this issue. Additionally, if you contact Microsoft Support, you can attach this data to your support request.
-
Exported data from the Security event log
-
Windows Server 2019 version and build details
Note: To see the exact version and build number, run
winverat a command prompt on the affected computer. -
Screenshots of the audit policy configuration in the Group Policy Management console
-
Screenshots of the folder's auditing entries in the folder Properties dialog box
-
Details of the steps that were used in testing, including the user account that was used and the actions that were performed
References
Source: Microsoft Learn / IT Pro troubleshooting by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.
