This is typically a problem in larger companies where the larger Security Group operates independently (for monitoring purposes) of the smaller Dev groups,so most other people would ask "Why do you need a second Forwarder on the same machine?" Ideally, we'd (Devs) get access to the repository that the Security Group manages, and we'd be able to use the same instance of the Windows Splunk Forwarder. Since that's not a reality here at this point, and Splunk has not (officially) enabled multiple instances the Windows Splunk Forwarder, I'll have to look at other means of getting the Windows (WMI) metrics I need, possibly using tools from SolarWinds or Dynatrace, if I don't end up writing my own code to get at that data. ... View more