Domain controllers have a forwarder with the TA-Windows deployed via server class. Splunk App for Windows Infrastruture on the search head. We get wineventlog, some AD user record changes, logins, etc. However, Things like domain controller health and OU, nor domain drop downs in some dashboards are not populating. During the detect features configuration, Domains, Domain Controllers, and DNS do not get detected.
Splunk App for Windows Infrastructure needs the Splunk Supporting Add-on for Active Directory to get the domain specific data. Please refer to Configure the Splunk App for Windows Infrastructure for more details.
Were the prerequisite checks bypassed when the app was installed?
No prerequisites were skipped. The splunk supporting add-on for active directory is installed on the search head
Does the forwarder have SA-ldapsearch installed? It was not clear to me whether it was installed on the forwarder.
Domain controllers have a forwarder with the TA-Windows deployed via server class
The universal forwarder on the domain controller does not have SA-ldapsearch, only app deployed is TA-windows. SA-ldapsearch is only on the search head.
Yes, Currently, looking into the inputs.conf file from the TA-WIndows, As there are monitors that are disabled such as Directory service and File Replication service. If enabled, would that fix the problem?
Possibly. However, since the deployment has an indexer, if the indexer is used by the search head as search peer, SA-ldapsearch needs to be installed there as well if it is not already installed.