Download and configure the Splunk Add-on for Windows
This topic discusses downloading and configuring the Splunk Add-on for Windows and deploying it to the deployment clients to gather Windows data and send it to the Splunk App for Windows Infrastructure indexers.
About the Splunk Add-on for Windows
The Splunk Add-on for Windows collects Windows data from Windows hosts. In the context of the Splunk App for Windows Infrastructure, the add-on collects Windows data and provides knowledge objects for the app. You should deploy the Splunk Add-on for Windows to:
- All hosts that run Active Directory Domain Services (including domain controllers and DNS servers).
- All Windows hosts from which you want Windows data.
- All indexers.
- All search heads.
- Basically, everywhere.
Download the Splunk Add-on for Windows
- Download the Splunk Add-on for Windows from Splunkbase and save it to an accessible place on the deployment server. You might need to sign in with your Splunk account before the download starts.
- When prompted, choose an accessible location on your deployment server to save the download. Do not attempt to run the download.
- Use an archive utility such as WinZip to unarchive the file to an accessible location.
Configure the Splunk Add-on for Windows
Before the add-on can collect Windows data, you must configure it.
Microsoft Windows event logs that are rendered in XML format will not populate in the Splunk App for Windows Infrastructure
- In the location where you unarchived the download file, locate the
- Inside this directory, make a subdirectory
- Copy the
inputs.conffile in the
defaultsubdirectory to the
- Open the
localsubdirectory with a text editor, such as Notepad.
- Enable the Windows inputs you want to get data for. Do this by changing the value of the
disabledattribute in each input stanza from 1 to 0.
At a minimum, enable the following sets of inputs. The
[admon]input should only be enabled on one domain controller in a single domain. The
[admon]input directly queries the Active Directory domain controllers. Enabling this input on multiple Splunk instances can disrupt your Active Directory servers and eventually make them unresponsive, preventing users from accessing needed services.
Input: Supported page(s):
[perfmon://FreeDiskSpace], [perfmon://Memory], [perfmon://LocalNetwork], [perfmon://CPUTime]
[WinHostMon://Computer], [WinHostMon://Process], [WinHostMon://Processor], [WinHostMon://NetworkAdapter], [WinHostMon://Service], [WinHostMon://OperatingSystem], [WinHostMon://Disk], [WinHostMon://Driver], [WinHostMon://Roles](Host Monitoring inputs)
[WinPrintMon://printer], [WinPrintMon://driver], [WinPrintMon://port](Print Monitoring inputs)
[WinNetMon://inbound], [WinNetMon://outbound](Network Monitoring inputs)
- Save the
inputs.conffile in the
You have downloaded and configured the Splunk Add-on for Windows.
Next, you will deploy it to the deployment clients. Once they receive the add-on, they will use the configuration in the "send to indexer" app to send Windows data to the indexer.
Add the universal forwarder to the server class
Deploy the Splunk Add-on for Windows
This documentation applies to the following versions of Splunk® App for Windows Infrastructure (Legacy): 1.4.1, 1.4.2, 1.4.3, 1.4.4