How can I disable Splunk Universals Forwarder input after installing Splunk TA_windows via deployment?

[jjacksonVirtus]

I currently have a Splunk Universal Forwarder installed on all my servers. It was recommended by Splunk to install the TA_windows plug-in on top of the Universal Forwarder. I built out a deployment from the Search Head to deploy TA_windows add-on to my servers but I noticed the regular Universal forwarder input.conf is still active/enabled along with the TA_windows add-on.
How can I disable the regular Universal Forwarder app automatically when using the TA_windows add-on.

[ddrillic]

Keep in mind that multiple input.conf is a feature and not a distraction. Meaning, each input.confbrings its needs to the table and all of them are being aggregated together. So, as long as they don't conflict each other they can coexist according to the beloved - live and let live idea.

[tiagofbmm · Accepted solution]

Can you change that inputs.conf in the app in the deployment server and then do a splunk reload deploy server?

That will get you the fresh version of the app with the input disabled.

[tiagofbmm]

Please let me know if the answer was useful for you. If it was, accept it and upvote. If not, give us more input so we can help you with that