Installation

Universal Forwarder managed with Powershell

willadams
Contributor

We currently have a deployment server which manages our infrastructure quiye well. A change in our environment is coming where the requirement is to (due to minimal change) make the universal forwarders (these are Windows) unmanaged and for any future changes to be done via a powershell script. My obvious response is no but I wanted to see what other peoples experiences are with not using a deployment server to manage anywhere between 30-40 machines usong scripts such as Powershell. What cons have you found doing it this way when compared to a tried and trusted approach with DS? I can't see any pros with it but I will ask that to. 

Labels (2)
0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

From Data to Insight: Announcing the Winners of the Splunk Dashboard Contest

Hi Splunkers, First off, thank you to everyone who participated in our very first From Data to Insight: The ...

Splunk Developers: Construct Your Future at the .conf26 Builder Bar

Calling all Splunk architects, platform admins, and app developers: the site is open, and the blueprints are ...

Quick connection discovery mode for forwarders

When a Splunk forwarder loses connectivity to its indexers, it does not always reconnect immediately. In many ...