Thanks for showing interest in our product and posting your query here.
Please verify and cross check these settings while configuring the software:
1. Check for the license, make sure it is not expired.
2. Click on Settings Tab of the software and select the domain you are monitoring and click on Modify.
3. In the Domain Settings verify all the credentials used. User Name here must have the administrative rights.
4. Now select Change Collection Settings and choose the Dc’s you want to monitor. Make sure that the DC you want to monitor will not be checked in excluding list.
5. Also make sure that the IP of DC is showing properly in Automatic Resolved IP field. If not then double click on selected DC and enter the correct IP manually.
6. Next steps is to select the OU and Object Classes you want to monitor as per your requirement.
7. Now you need to enter proper SQL Server credentials. If the SQL server is on same machine where the software is installed then use Windows Authentication and
If SQL Server is on remote location then use SQL Authentication with appropriate username and password.
8. Last steps is to create the database. You need to create the database from the software itself by just giving a new name of database here and it will be created on the
SQL Server.
After following these steps you will be able to get the reports and if not then check for the network connectivity.
The DC machine must be reachable from the machine where the software is installed. Let us know if this solves the issue.
If the issue still persist then please follow the steps to check for a group policy status:
1. Open Group Policy Management Editor.
2. Expand the nodes as follows: Computer Configuration -> Policies -> Windows Settings -> Security Settings -> Local Policies -> Security Options.
3. Now click on Security option and check for the status of a Group Policy named: Audit: Force audit policy subcategory settings to override audit policy category settings
4. If this Policy is Enabled then make it in Not-Defined state (or Disabled). After disabling it run the command gpupdate
Hope this will work. Please let us know the status.
In yours scenario <Audit: Force audit policy subcategory settings to override audit policy category settings> Group Policy is disabling the above mentioned audit policies, so disabling it has corrected the issue.