Deployment Architecture

Syntax for upgrading Windows-based Universal Forwarders through WSUS?

eblackburn
Path Finder

Have any of you upgraded Windows-based Universal Forwarders using WSUS? If so, what kind of syntax did you use when deploying it? I've tried this once in the past and don't believe it was totally successful:

msiexec.exe /i <file path><file name>.msi AGREETOLICENSE=Yes DEPLOYMENT_SERVER=<our_deployment_server>:8089 /quiet

Is there anything wrong in this syntax, or anything that I may have missed that should be corrected for next time?

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!

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...

Laser Bananas and Edge Hubs: Exploring Operational Technology (OT) Data Through a ...

  OT is a different environment to traditional IT and can have interesting challenges when interfacing the ...

Event Series: Mastering AI Tokenomics and Splunk Agent Observability

Beyond the Black Box: Correlating AI Performance and Tokenomics with Splunk Agent Observability   As ...