Configuration
Configure Windows File Servers in ADAudit Plus
Add one File Server at a time
Use this method when adding a small number of File Servers or when validating the setup for the first time.
- Log in to the ADAudit Plus web console.
- Click the File Audit tab.
- Select Windows File Server from the Configured Server(s) drop-down list.
- Click Add Server.
- Follow the wizard to add the File Server and required shares.
- In the final step, choose whether ADAudit Plus should automatically configure audit policies and object-level auditing:
- Select Yes to let ADAudit Plus configure the required audit policies and object-level auditing.
- Select No if you want to configure audit policies and object-level auditing manually.
Note: Automatic configuration requires the domain data collection identity to have the required permissions.
Add a File Cluster
Use this method to configure auditing for Windows failover clusters that host file shares.
- Log in to the ADAudit Plus web console.
- Click the File Audit tab.
- Click Add File Cluster.
- Follow the wizard to add the cluster and select the shares that must be audited.
- In the final step, choose whether ADAudit Plus should automatically configure audit policies and object-level auditing, or whether you will configure them manually.
Note: Ensure the domain data collection identity has the required privileges on the cluster nodes and audited shares.
Add File Servers in bulk
Use bulk configuration when adding multiple File Servers or shares.
- Create a CSV file named servers.csv in:
<installation_dir>\ManageEngine\ADAudit Plus\bin
- Save the file in UTF-8 encoding.
- Add one File Server name per line. Example:
- Test-FS1
- Test-FS2
- Test-FS3
- Create a CSV file named shares.csv in the same bin directory.
- Save the file in UTF-8 encoding.
- Add one share path per line. Example:
\\SERVERNAME\testfolder1
\\SERVERNAME\testfolder2
\\SERVERNAME\testfolder3 - Open Command Prompt on the ADAudit Plus server.
- Navigate to:
<installation_dir>\ManageEngine\ADAudit Plus\bin
- Run cmdUtil.bat.
- Enter ADAudit Plus administrator credentials when prompted.
- Run the bulk configuration command.
Bulk configuration command reference
Use the following command format:
config server add -machinetype fs -shares all|single|shares.csv -issacl true|false -isauditpolicy true|false
| Parameter | Value | Description |
|---|---|---|
| -machinetype | fs | Adds Windows File Servers. |
| -shares | all | Audit all shares on the specified File Servers. |
| -shares | single | Audit one random share. Use only for test scenarios. |
| -shares | shares.csv | Audit only shares listed in shares.csv. |
| -issacl | true | Automatically configure required object-level auditing settings. |
| -issacl | false | Do not configure object-level auditing automatically; configure manually. |
| -isauditpolicy | true | Automatically configure the required Object Access audit policy. |
| -isauditpolicy | false | Do not configure audit policies automatically; configure manually. |
Example: To audit selected shares in all File Servers and automatically configure object access audit policy and object-level auditing, run:
config server add -machinetype fs -shares shares.csv -issacl true -isauditpolicy true
Verify File Server configuration
After adding File Servers:
- Go to File Audit > Windows File Server.
- Confirm the File Server appears in the configured server list.
- Confirm the intended shares are listed.
- Confirm audit policy and object-level auditing status.
- If shares are missing, verify share discovery privileges in Agentless privileges for Windows File Server auditing.
Configure audit policies
Why audit policies are required
Audit policies must be configured so Windows logs file activity events. Without the correct audit policy settings, Windows may not generate the Security events required for File Audit reports.
Automatic audit policy configuration
ADAudit Plus can configure the required audit policies automatically.
- Log in to the ADAudit Plus web console.
- Click the File Audit tab.
- Select Windows File Server from the Configured Server(s) drop-down list.
- Click Configure Audit Policy in the top-right area above the table view.
- Confirm the action.
For automatic configuration, ADAudit Plus creates a Group Policy Object (GPO) named <domainname>_ADAuditPlusPolicy and configures the required audit policies for Windows File Server auditing.
Note: Automatic policy configuration requires permissions to create/edit/link the GPO and manage the security filtering group.
Manual audit policy configuration overview
Manual configuration uses a dedicated GPO and security filtering group so the settings apply only to monitored File Servers.
High-level steps:
- Create a domain local security group named ADAuditPlusFS.
- Add monitored File Server computer accounts as members of ADAuditPlusFS.
- Create and link a GPO named ADAuditPlusFSPolicy for manual configuration.
- Remove Authenticated Users from Security Filtering.
- Add ADAuditPlusFS to Security Filtering.
- Configure advanced or legacy audit policy settings in ADAuditPlusFSPolicy.
Configure the File Server security filtering group
- Open Active Directory Users and Computers.
- Right-click the domain and select New, then click Group.
- In the New Object - Group window, configure:
Field Value Group name ADAuditPlusFS Group scope Domain Local Group type Security - Click OK.
- Right-click the newly created group and select Properties.
- Go to Members, then click Add.
- Add all Windows File Server computer accounts that must be audited.
- Open Group Policy Management Console (GPMC).
- Right-click the domain and select Create a GPO in this domain, and Link it here.
- Name the GPO ADAuditPlusFSPolicy and click OK.
- Select the ADAuditPlusFSPolicy GPO.
- Under Security Filtering, remove Authenticated Users.
- Add the ADAuditPlusFS group.
Configure advanced audit policies
Use advanced audit policies for Windows Server 2008 and later.
- Right-click ADAuditPlusFSPolicy and select Edit.
- Navigate to Computer Configuration > Policies > Windows Settings > Security Settings > Advanced Audit Policy Configuration > Audit Policies
- Configure the settings listed in Recommended advanced audit policy settings.
Enforce advanced audit policy settings
When using advanced audit policies, ensure that advanced audit policy subcategory settings override legacy policy category settings.
- Edit ADAuditPlusFSPolicy.
- Navigate to Computer Configuration > Policies > Windows Settings > Security Settings > Local Policies > Security Options
- Enable Audit: Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings.
Configure legacy audit policies
Legacy audit policies apply only to older environments where advanced audit policies are not available.
Important: Windows Server 2003 / 2003 R2 is past end-of-life support from Microsoft. This section is retained only as legacy reference material and should not be treated as a recommendation for new deployments.
- Right-click ADAuditPlusFSPolicy and select Edit.
- Navigate to Computer Configuration > Policies > Windows Settings > Security Settings > Audit Policy Configuration
- Configure the settings listed in Recommended legacy audit policy settings.
Recommended advanced audit policy settings
| Category | Subcategory | Audit events | Purpose |
|---|---|---|---|
| Object Access | Audit File System | Success, Failure | File and folder auditing |
| Object Access | Audit File Share | Success | File share auditing |
| Object Access | Audit Handle Manipulation | Success, Failure | File access and permission change auditing |
| Policy Change | Audit Policy Change | Success, Failure | Audit policy change auditing |
| Policy Change | Audit Authorization Policy Change | Success | File permission change auditing |
Recommended legacy audit policy settings
| Category | Audit events | Purpose |
|---|---|---|
| Object Access | Success, Failure | File share auditing and file permission change auditing |
Configure object-level auditing (SACL)
Why object-level auditing is required
To audit file and folder access, object-level auditing must be applied to the shares, files, and folders you want to monitor. Audit policies enable event generation at the category level; object-level auditing controls exactly which file system objects generate events.
Automatic object-level auditing configuration
ADAudit Plus can automatically apply object-level auditing to configured shares.
- Log in to the ADAudit Plus web console.
- Go to the File Audit tab.
- Click Windows File Server under Configured Server(s) in the left pane.
- Click the Remove or View Configured File Shares icon for the File Server.
- Select the required shares.
- Click Apply object-level audit settings on configured shares.
Object-level auditing status color codes
Hover over a share to view any error code or status details.
| Color | Meaning |
|---|---|
| Green | Object-level auditing is set correctly. |
| Red | Object-level auditing is not set correctly or an error occurred during configuration. |
| Orange | Object-level auditing configuration is in progress. |
Manual SACL configuration using Windows shares
Use this method when configuring SACL entries manually from Windows share or folder properties.
- Right-click the share folder that you want to audit.
- Select Properties.
- Click the Security tab.
- Click Advanced.
- Click the Auditing tab.
- Add the following entries for the Everyone principal.
| Activity | Principal | Type | Access | Applies to |
|---|---|---|---|---|
| File/folder changes | Everyone | Success, Failure | Create files / Write Data; Create folders / Append data; Write attributes; Write extended attributes; Delete subfolders and files; Delete | This folder, subfolders, and files |
| Folder permission and owner changes | Everyone | Success, Failure | Take ownership; Change permissions | This folder and subfolders |
| File read | Everyone | Success, Failure | List folder / Read data | Files only |
| Folder read failure | Everyone | Failure | List folder / Read data | This folder and subfolders |
Note: The SACL principal remains Everyone because ADAudit Plus must audit file activity performed by all users and processes, not only a selected user or administrative group.
Manual SACL configuration using PowerShell
Use this method when configuring object-level auditing for multiple files or folders through a CSV file.
- Create a CSV file that lists the UNC paths or local paths of all files and folders for which you want to enable File Server Auditing (FA).
- Use the following format:
<file_or_folder>,FA
- Example:
\\SERVERNAME\folder,FA
C:\test folder,FA
E:\test file.txt,FA - Open PowerShell.
- Navigate to the ADAudit Plus bin folder:
<installation_directory>\bin
- Use the ADAP-Set-SACL.ps1 script.
Command format:
.\ADAP-Set-SACL.ps1 -file '.\file_name.csv' -mode add|remove -recurse true|false -username DOMAIN_NAME\username
Examples:
.\ADAP-Set-SACL.ps1 -file '.\shared_folders_list.csv' -mode add
.\ADAP-Set-SACL.ps1 -file '.\shared_folders_list.csv' -mode add -recurse true
.\ADAP-Set-SACL.ps1 -file '.\shared_folders_list.csv' -mode remove
PowerShell parameter reference
| Parameter | Input variable | Mandatory |
|---|---|---|
| -file | Name of the CSV file containing the list of files/folders | Yes |
| -mode | Add to set object-level auditing; omit to remove object-level auditing | Yes |
| -recurse | Setting to true replaces all subfolder object-level auditing settings with inheritable auditing settings applied to the chosen folder; false applies object-level auditing only to the chosen folder. Default is false. | No |
| -username | DOMAIN_NAME\username of a user with privilege over the file or folder to set object-level auditing. No cross-domain support. | No |
Configure Security log settings
Why Security log sizing matters
ADAudit Plus collects File Server audit data from Windows Security logs. If the Security log is too small, older events can be overwritten before ADAudit Plus collects them, causing audit gaps.
Configure Security log retention
- Open Group Policy Management Console (GPMC).
- Edit the ADAuditPlusFSPolicy GPO.
- Navigate to Computer Configuration > Policies > Windows Settings > Security Settings > Event Log
- Configure Retention method for security log as Overwrite Events As Needed.
- Configure Maximum security log size based on Recommended Security log size and your environment's event volume.
Note: Ensure the Security log can hold at least 12 hours of data. For high-volume File Servers, size the log to retain 12–24 hours or more based on operational requirements.
Recommended Security log size
| Role | Operating system | Minimum size |
|---|---|---|
| Windows File Server | Windows Server 2008 and above | 4096MB |
Note: Windows Server 2003 / 2003 R2 is past end-of-life support from Microsoft and should not be used for new deployments. The older 512MB legacy recommendation is not included as an active recommendation.
Tip: Treat 4096MB as a baseline. Increase the Security log size if the log cannot retain at least 12–24 hours of file activity events.
Configure exclusions
Why exclusions are used
Use exclusions to reduce noise and avoid auditing files, folders, file types, processes, or users that are not relevant to your monitoring goals.
Files and folders can be excluded based on:
- File/folder local path
- File type
- Process name
- User name
Configure exclusions in ADAudit Plus
- Log in to the ADAudit Plus web console.
- Go to the File Audit tab.
- In the left pane, click Configuration.
- Click Exclude Configuration.
- Choose an exclusion type:
- File/Folder local path
- File Type
- Process Name
- Users
- Click +.
- Configure the exclusion settings.
- Save the configuration.
Exclusion examples
Example 1: Exclude a folder and all subfolders/files
| Field | Share path example | Local path example |
|---|---|---|
| Share configured | \\SERVER_NAME\share_name | C:\sharefolder |
| Path excluded | C:\sharefolder\excludefolder | C:\sharefolder\excludefolder |
| Pattern type | File/Folder Patterns | File/Folder Patterns |
| Syntax | C:\sharefolder\excludefol | C:\sharefolder\excludefol |
| Excluded | Folder, subfolders, and files under excludefolder | Folder, subfolders, and files under excludefolder |
Example 2: Exclude AppData folder for every user profile
| Field | Value |
|---|---|
| Share and folder path | \\SERVER_NAME\Users, C:\Users |
| Example path | C:\Users\user1\AppData |
| Pattern type | Regex Patterns |
| Syntax | C:\\Users\\[^\\]*\\AppData |
| Excluded | C:\Users\user1\AppData, C:\Users\user2\AppData, and subfolders under those AppData paths |
| Not excluded | Nested AppData paths such as C:\Users\user1\subfolder\AppData |
Example 3: Exclude files from a specific folder but audit subfolders
| Field | Value |
|---|---|
| Share and folder path | \\SERVER_NAME\share_name, C:\sharefolder |
| Path excluded | C:\sharefolder\excludefolder |
| Pattern type | Regex Patterns |
| Syntax | ^c:\\sharefolder\\excludefolder\\[^\\]*\.[^\\]*$ |
| Excluded | Files directly under excludefolder, such as file.txt |
| Not excluded | The folder itself, subfolders, and files inside subfolders |
Verify exclusions
After configuring exclusions, verify that they suppress only the intended activity.
- Perform a controlled test activity that matches the exclusion, such as creating or modifying a test file in an excluded folder.
- Perform a similar activity outside the excluded path or condition.
- Generate the relevant File Audit report.
- Confirm that the excluded activity does not appear in the report.
- Confirm that the non-excluded activity still appears in the report.
Important: Review exclusions carefully before broad rollout. An overly broad path, regex, process, file type, or user exclusion can suppress audit data that may be needed for investigations or compliance reviews.
Verify the configuration
Verify audit policies and Security log settings
Use Group Policy Results to verify audit policy and Security log settings on monitored File Servers:
gpresult /S <monitored_computer> /F /H <file_name>.html
Open the generated HTML file and verify that the required audit policy and Security log settings are applied.
Verify object-level auditing settings
To verify object-level auditing settings:
- Open the configured share or folder.
- Go to Properties > Security > Advanced > Auditing.
- Confirm the required SACL entries from Manual SACL configuration using Windows shares are present.
- In ADAudit Plus, check the object-level auditing status color for configured shares.
Verify events on monitored File Servers
- Open Event Viewer (eventvwr.msc).
- Right-click Event Viewer and connect to the target File Server.
- Open the Security log.
- Confirm that events corresponding to the configured audit policies and SACL entries are generated.