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
Get Updates on the Splunk Community!

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

More Control Over Your Monitoring Costs with Archived Metrics!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...

New in Observability Cloud - Explicit Bucket Histograms

Splunk introduces native support for histograms as a metric data type within Observability Cloud with Explicit ...