Configuration

Configure Active Directory domains and domain controllers

Automatic discovery

After installation, ADAudit Plus automatically discovers the local domain and the domain controllers running in it.

To review the automatically discovered domain controllers:

  • Log in to the ADAudit Plus web console.
  • Navigate to Domain Settings.
  • Review the discovered local domain.
  • Select the domain controllers that must be audited by enabling the check boxes for the required domain controllers.
  • Save the configuration.

Manual domain configuration

Use manual configuration when the required domain is not discovered automatically or when you need to add another domain.

  • Log in to the ADAudit Plus web console.
  • Navigate to Domain Settings.
  • Click Add Domain.
  • Enter the required domain details.
  • Provide the domain credential or data collection identity required to add and manage the domain.
  • Select or provide a reachable domain controller for the domain.
  • Save the configuration.

Note The account used during domain addition must have the required privileges for the domain operations you want ADAudit Plus to perform. For details, see Domain Data Collection Account.

Select domain controllers for auditing

Select every domain controller that processes authentication or directory changes for the domain. This is important because Windows logs events on the domain controller that processed the operation.

Scenario Recommendation
Multiple domain controllers in one site Select all domain controllers in the site.
Multiple Active Directory sites Select domain controllers across all relevant sites.
Read-only domain controllers Include them if they process authentication or generate events relevant to your audit scope.
Retired or offline domain controllers Remove or disable them from the auditing list after confirming they no longer process events.

Verify domain configuration

After adding or selecting domain controllers:

  • Confirm the domain appears in ADAudit Plus.
  • Confirm the required domain controllers are selected.
  • Confirm the domain data collection identity is configured and valid.
  • Confirm the ADAudit Plus server can reach the selected domain controllers over the required Windows management and directory protocols.

Note Detailed protocol and privilege requirements are maintained in agentless privileges for Active Directory and GPO auditing.

Synchronize Active Directory objects

After a domain is configured, ADAudit Plus synchronizes Active Directory objects so reports, filters, alerts, and object selection screens use the latest domain object information.

ADAudit Plus supports both scheduled and on-demand synchronization:

Sync type Description
Automatic daily sync ADAudit Plus automatically synchronizes AD objects every day at 12am.
On-demand sync Administrators can manually run object synchronization from Domain Settings after domain configuration.

To run an on-demand object sync:

  • Log in to the ADAudit Plus web console.
  • Navigate to Domain Settings.
  • Select the configured domain.
  • Click Update Domain Objects.
  • Select the object categories to synchronize, such as:
    • Audit Policy
    • OUs (Organizational Units)
    • Container
    • Groups
    • Users
    • Computers
    • Group Policy Objects
    • Object Attributes
    • Managed Service Accounts
  • Click Save to start synchronization for the selected object categories.

Configure audit policies

Why audit policies are required

ADAudit Plus reports depend on events generated in Windows event logs. Audit policies must be configured on domain controllers so that Windows logs the required events whenever relevant Active Directory activity occurs.

If the required audit policies are not enabled, ADAudit Plus cannot report those activities even if the product is configured correctly.

Automatic audit policy configuration

ADAudit Plus can automatically configure the required audit policies for Active Directory auditing.

  • Log in to the ADAudit Plus web console.
  • Navigate to Domain Settings.
  • Locate the Audit Policy for the configured domain.
  • Click Configure.
  • Review the policies that ADAudit Plus will configure.
  • Confirm the action.

Note ADAudit Plus does not configure audit policies automatically without user consent.

Important Automatic audit policy configuration requires the domain data collection identity to have the necessary GPO edit permission.

Manual advanced audit policy configuration

Advanced audit policies provide granular control over which activities are logged and help reduce unnecessary event noise. Use advanced audit policies for domain controllers running Windows Server 2008 and later.

To configure advanced audit policies manually:

  • Log in to a computer that has the Group Policy Management Console installed, using an account with permissions to edit the domain controller audit policy GPO.
  • Open Group Policy Management.
  • Right-click Default Domain Controllers Policy.
  • Click Edit.
  • In Group Policy Management Editor, navigate to:

    Computer Configuration > Policies > Windows Settings > Security Settings > Advanced Audit Policy Configuration > Audit Policies

  • Open the relevant audit policy category and subcategory.
  • Configure Success, Failure, or both, as specified in Recommended advanced audit policy settings.

Enforce advanced audit policy settings

When using advanced audit policies, ensure that advanced audit policy subcategory settings are forced over legacy audit policy settings.

  • Open Group Policy Management.
  • Right-click Default Domain Controllers Policy.
  • Click Edit.
  • Navigate to:

    Computer Configuration > Policies > Windows Settings > Security Settings > Local Policies > Security Options

  • Open Audit: Force audit policy subcategory settings.
  • Set the policy to Enabled.

Manual legacy audit policy configuration

Legacy audit policy configuration applies only to older environments where advanced audit policies are not available.

Important Windows Server 2003 / 2003 R2 has reached EOL from Microsoft. This section is retained only as legacy reference material and should not be treated as a recommendation for new deployments.

To configure legacy audit policies manually:

  • Log in to a computer that has the Group Policy Management Console installed, using an account with permissions to edit the domain controller audit policy GPO.
  • Open Group Policy Management.
  • Right-click Default Domain Controllers Policy.
  • Click Edit.
  • In Group Policy Management Editor, navigate to:

    Computer Configuration > Policies > Windows Settings > Security Settings > Local Policies > Audit Policy

  • Open the relevant policy.
  • Configure Success, Failure, or both, as specified in Recommended legacy audit policy settings.

Configure the following advanced audit policy settings on domain controllers.

Category Subcategory Audit events
Account Logon Audit Kerberos Authentication Service Success and Failure
Account Management Audit Computer Account Management Success
Account Management Audit Distribution Group Management Success
Account Management Audit Security Group Management Success
Account Management Audit User Account Management Success and Failure
Detailed Tracking Audit Process Creation Success
Detailed Tracking Audit Process Termination Success
DS Access Audit Directory Service Changes Success
DS Access Audit Directory Service Access Success
Logon / Logoff Audit Logon Success and Failure
Logon / Logoff Audit Network Policy Server Success and Failure
Logon / Logoff Audit Other Logon/Logoff Events Success
Logon / Logoff Audit Logoff Success
Object Access Audit Other Object Access Events Success
Policy Change Audit Authentication Policy Change Success
Policy Change Audit Authorization Policy Change Success
System Audit Security State Change Success

Configure the following legacy audit policy settings only for older environments where advanced audit policies are not available.

Category Audit events
Account Logon Success and Failure
Audit Logon / Logoff Success and Failure
Account Management Success
Directory Service Access Success
Process Tracking Success
Object Access Success
System Events Success

Configure object-level auditing (SACL)

Why object-level auditing is required

Audit policies control whether Windows logs a category of activity. Object-level auditing controls which Active Directory objects and operations generate audit events. This is done by configuring SACL entries on the required Active Directory naming contexts and objects.

Without the required SACL entries, some Active Directory object changes may not generate the events ADAudit Plus needs for reports, such as GPO history, permission changes, DNS changes, and object life cycle changes.

Automatic object-level auditing configuration

ADAudit Plus can automatically configure the required object-level auditing settings.

  • Log in to the ADAudit Plus web console.
  • Navigate to Reports > GPO Management > GPO History.
  • If object-level auditing is not configured, ADAudit Plus displays the following message: Object level auditing needs to be configured for getting proper reports.
  • Click Configure.
  • Review and confirm the configuration.

Note ADAudit Plus does not configure object-level auditing automatically without user consent.

Manual SACL configuration prerequisites

When configuring SACL entries manually:

  • Use an account with sufficient rights to edit auditing entries on the relevant Active Directory objects.
  • Use Active Directory Users and Computers for domain object SACLs.
  • Use ADSI Edit for container, password setting, configuration, schema, and DNS object SACLs.
  • In each Auditing Entry window, set:
    • Principal: Everyone
    • Type: Success
  • Use Clear all before selecting the specific permissions listed in the relevant table.

Note The SACL principal remains Everyone because ADAudit Plus must audit changes made by all accounts, not only a selected user or administrative group.

Important Apply SACL entries carefully and validate them in a test or controlled environment before broad production rollout.

SACL entries for OU, GPO, user, group, computer, and contact objects

Use Active Directory Users and Computers:

  • Open Active Directory Users and Computers.
  • Click View and enable Advanced Features.
  • Right-click the domain object.
  • Navigate to Properties > Security > Advanced > Auditing > Add.
  • Add the following auditing entries.

Note All 12 auditing entries in this table must be enabled.

Auditing entry number Auditing entry for Access Apply onto: Windows Server 2003 Apply onto: Windows Server 2008/2012 and later
1 & 2 OU Create Organizational Unit objects; Delete Organizational Unit objects This object and all child objects This object and all descendant objects
1 & 2 OU Write All Properties; Delete; Modify Permissions Organizational Unit objects Descendant Organizational Unit objects
3 & 4 GPO Create groupPolicyContainer objects; Delete groupPolicyContainer objects This object and all child objects This object and all descendant objects
3 & 4 GPO Write All Properties; Delete; Modify Permissions groupPolicyContainer objects Descendant groupPolicyContainer objects
5 & 6 User Create User objects; Delete User objects This object and all child objects This object and all descendant objects
5 & 6 User Write All Properties; Delete; Modify Permissions; All Extended Rights User objects Descendant User objects
7 & 8 Group Create Group objects; Delete Group objects This object and all child objects This object and all descendant objects
7 & 8 Group Write All Properties; Delete; Modify Permissions; All Extended Rights Group objects Descendant Group objects
9 & 10 Computer Create Computer objects; Delete Computer objects This object and all child objects This object and all descendant objects
9 & 10 Computer Write All Properties; Delete; Modify Permissions; All Extended Rights Computer objects Descendant Computer objects
11 & 12 Contact Create Contact objects; Delete Contact objects This object and all child objects This object and all descendant objects
11 & 12 Contact Write All Properties; Delete; Modify Permissions; All Extended Rights Contact objects Descendant Contact objects

SACL entry for container objects

Use ADSI Edit:

  • Open ADSI Edit.
  • Right-click ADSI Edit and click Connect to.
  • Under Select a well known Naming Context, select Default naming context.
  • Navigate to the domain distinguished name.
  • Right-click the domain distinguished name and select Properties.
  • Navigate to Security > Advanced > Auditing > Add.
  • Add the following auditing entry.
Auditing entry Access Apply onto — Windows Server 2003 Apply onto — Windows Server 2008/2012 and later
Container Write All Properties; Delete; Modify Permissions Container objects Descendant Container objects

SACL entries for password setting objects

Use ADSI Edit:

  • Open ADSI Edit.
  • Connect to the Default naming context.
  • Expand the domain.
  • Expand the System container.
  • Right-click Password Settings Container.
  • Navigate to Properties > Security > Advanced > Auditing > Add.
  • Add the following auditing entries.

Note Both auditing entries in this table must be enabled.

Auditing entry number Auditing entry for Access Apply onto: Windows Server 2003 Apply onto: Windows Server 2008/2012 and later
1 & 2 Password Settings Container Create msDS-PasswordSettings objects; Delete msDS-PasswordSettings objects Not applicable This object and all descendant objects
1 & 2 Password Settings Container Write All Properties; Delete; Modify Permissions Not applicable Descendant msDS-PasswordSettings objects

SACL entry for configuration objects

Use ADSI Edit:

  • Open ADSI Edit.
  • Connect to the Configuration naming context.
  • Right-click the Configuration naming context.
  • Navigate to Properties > Security > Advanced > Auditing > Add.
  • Add the following auditing entry.
Auditing entry for Access Apply onto — Windows Server 2003 Apply onto — Windows Server 2008/2012 and later
Configuration Create All Child objects; Write All Properties; Delete All child objects; Delete; Modify Permissions; All Extended Rights This object and all child objects This object and all descendant objects

SACL entry for schema objects

Use ADSI Edit:

  • Open ADSI Edit.
  • Connect to the Schema naming context.
  • Right-click the Schema naming context.
  • Navigate to Properties > Security > Advanced > Auditing > Add.
  • Add the following auditing entry.
Auditing entry for Access Apply onto — Windows Server 2003 Apply onto — Windows Server 2008/2012 and later
Schema Create All Child objects; Write All Properties; Delete All child objects; Delete; Modify Permissions; All Extended Rights This object and all child objects This object and all descendant objects

SACL entries for DNS objects

Use ADSI Edit:

  • Open ADSI Edit.
  • Right-click ADSI Edit and click Connect to.
  • Enter the distinguished name for the partition where the DNS zone is stored:
    • Default domain partition example: DC=adap,DC=internal,DC=com
    • DomainDNSZones partition example: DC=DomainDNSZones,DC=adap,DC=internal,DC=com
    • ForestDNSZones partition example: DC=ForestDNSZones,DC=adap,DC=internal,DC=com
  • Navigate to the relevant DNS naming context.
  • Right-click the naming context and select Properties.
  • Navigate to Security > Advanced > Auditing > Add.
  • Add the following auditing entries.

Note All DNS auditing entries in this table must be enabled for the relevant DNS partitions.

Auditing entry number Auditing entries for Access Apply onto — Windows Server 2003 Apply onto — Windows Server 2008/2012 and later
1 & 2 DNS Zones Create DNS Zones objects; Delete DNS Zones objects This object and all child objects This object and all descendant objects
1 & 2 DNS Zones Write All Properties; Delete; Modify Permissions DNS Zone objects Descendant DNS Zone objects
3 & 4 DNS Nodes Create DNS Nodes objects; Delete DNS Nodes objects This object and all child objects This object and all descendant objects
3 & 4 DNS Nodes Write All Properties; Delete; Modify Permissions DNS Node objects Descendant DNS Node objects

Configure event log settings

Why event log sizing matters

ADAudit Plus collects audit data from domain controller event logs. If the Security log is too small or configured incorrectly, older events can be overwritten before ADAudit Plus collects them, causing permanent audit gaps.

Configure Security log retention

  • Log in to a computer that has the Group Policy Management Console installed, using an account with permissions to edit the domain controller policy.
  • Open Group Policy Management.
  • Right-click Default Domain Controllers Policy.
  • Click Edit.
  • Navigate to:

    Computer Configuration > Policies > Windows Settings > Security Settings > Event Log

  • Open Retention method for security log.
  • Set it to Overwrite events as needed.
  • Open Maximum security log size.
  • Define the size based on the recommended Security log size or your organization's retention requirements.

Note Ensure that the Security event log holds a minimum of 12 hours of data. For better resilience during high-volume periods or temporary collection delays, size the log to retain 12–24 hours of data.

The Security log must be large enough to retain at least 12–24 hours of audit data. Increase the log size based on domain controller event volume, authentication traffic, ADAudit Plus collection frequency, and your outage tolerance.

Use the following minimum Security log size recommendation for currently documented Windows Server domain controller versions:

Role Operating system Size
Domain controller Windows Server 2008 and above 1024MB

Tip Treat 1024MB as a baseline, not a maximum. If the Security log cannot hold at least 12–24 hours of data, increase the log size until the required retention window is met.

Configure GPO settings change auditing

Note This section is required only if you want to audit detailed GPO settings changes with old and new values. GPO management auditing (creation, deletion, link changes) is already covered by the Active Directory audit policies and SACL entries configured in the previous sections.

GPO auditing components

ADAudit Plus provides two related GPO auditing capabilities:

  • GPO management auditing — tracks GPO creation, deletion, link changes, and modification events. Configured through Active Directory audit policies and SACL entries.
  • GPO settings change auditing — captures detailed changes to settings inside a GPO, including old and new values. Only the PDC must be configured; GPMC must be installed on the ADAudit Plus server.

How GPO settings change auditing works:

  1. ADAudit Plus monitors the SYSVOL folder on the PDC for changes to Group Policy templates and policy files. When a GPO is modified, the change is detected in SYSVOL.
  2. ADAudit Plus then generates a report for the modified GPO and compares the current version with the previous version stored in the ADAudit Plus database.
  3. To identify who made the change, ADAudit Plus queries the PDC Security log for event ID 5136.
  4. The detected changes, along with the previous and new values, are stored in the database for reporting and real-time alerting.

Identify the Primary Domain Controller

GPO settings change auditing requires the PDC to be configured in ADAudit Plus.

Step 1: Find the PDC name

  • Log in to any machine with Active Directory Users and Computers installed.
  • Go to Start > Windows Administrative Tools > Active Directory Users and Computers.
  • Right-click your domain and select Operations Masters.
  • Click the PDC tab.
  • Note the server name shown under Operations master.
  • Click Close.

Step 2: Add the PDC in ADAudit Plus

  • Log in to the ADAudit Plus web console.
  • Navigate to Configuration > Domains and Controllers.
  • Select your domain from the list.
  • Click Add Domain Controller and enter the PDC name noted in Step 1.
  • Click Save.

Note: If the PDC is already listed under the domain, no action is needed here. Proceed to the next section.

Install the Group Policy Management Console

The GPMC must be installed on the machine running ADAudit Plus for GPO settings change reports.

Install GPMC on Windows Server 2012 and later

  • Go to Start > Control Panel > Turn Windows features on and off under Programs.
  • In the Add Roles and Features Wizard, select Features.
  • Check Group Policy Management.
  • Click Next, then click Install.

Install GPMC on Windows Server 2008 and 2008 R2

  • Go to Start > Control Panel > Turn Windows features on and off under Programs.
  • In Server Manager, select Features > Add Features.
  • Check Group Policy Management.
  • Click Next, then click Install.

Enable GPO settings change auditing

  • Log in to the ADAudit Plus web console.
  • Navigate to Configuration > Monitoring and Analysis > GPO change Monitoring.
  • Select your domain from the Domain drop-down.
  • Enable GPO change Monitoring. The Primary Domain Controller Name is populated automatically. If the PDC is not shown, click Discover PDC.
  • Choose your auditing mode:
  • With agent — recommended; avoids network access errors and SYSVOL connectivity issues.
  • Without agent — requires the ADAudit Plus server to have read access to the PDC SYSVOL share.
  • Click Save.

Verify SYSVOL accessibility

If auditing without an agent, verify that the ADAudit Plus server can access the PDC SYSVOL share. Before running this check, ensure the required firewall ports are open as described in Agentless SYSVOL access ports under Data collection, ports, and privilege planning.

  • On the ADAudit Plus server, open File Explorer.
  • Enter the PDC SYSVOL path (for example, the PDC name followed by sysvol) and press Enter.
  • Confirm the SYSVOL folder opens without errors.

Tip: Use agent-based auditing to avoid SYSVOL and RPC-related network errors.