Confirm and troubleshoot AD data collection

This topic discusses how to confirm and troubleshoot data collection from the Splunk Add-ons for Active Directory.

Check the indexer for data

After you configure and deploy the Splunk Add-ons for Active Directory into your domain controller deployment client, you should check the deployment server to see that data has arrived. The fastest way to do that is to load the Search and Reporting app and view the Data Summary:

1. In the system bar, click Apps > Search & Reporting. Splunk Enterprise loads the Search & Reporting app.

2. Click Data Summary. Splunk brings up the data summary page with the "Hosts" tab active.

3. Scan through the list of host names for the name of your domain controller deployment client.

• If you do not see the deployment client host name, then there is a problem occurring between the client at the indexer. Confirm that:
  • You have properly configured receiving on the indexer.
  • You have properly configured the "send to indexer" app to forward data to the indexer.
  • No network issue exists between the deployment client and the indexer.

4. Click the host name in the list. Splunk Enterprise brings up a search window that displays all events associated with the deployment client host name.

5. Search through the data to see that all of the events you configured in the Splunk Add-on for Windows have been sent to the indexer. See "Sample Active Directory searches and dashboards."

• If you do not see the events you expect, try these steps:
  • Confirm that you have placed the add-on in the deployment apps directory and reloaded the deployment server.
  • Confirm that the deployment client does not have errors attempting to collect the data.
  • More troubleshooting steps are available in the Splunk Troubleshooting manual.

What's next?

You have configured and deployed the Splunk Add-ons for Active Directory to your domain controller deployment clients. This now means that Active Directory data is present on your Splunk App for Microsoft Exchange indexer.

The next step is to get DNS data onto the indexer.