Getting Data In

How to install a Splunk universal forwarder via command line in low-privilege mode?

email2vamsi
Explorer

I am Installing a Splunk universal forwarder using the command line with the following command in "low-privilege" mode.
I want to use a local client account that is created prior to installation.
This command works fine if LOGON_USERNAME="ClientHostName\user_name" or LOGON_USERNAME="domain\user_name".
I cannot use a generic approach like LOGON_USERNAME=".\user_name". This way, it fails to install.
I want to use this generic approach, so that I can run this on a bunch of Windows clients.

msiexec /I splunkforwarder-6.1.9-272667-x64-release.msi /qn ALLUSERS=1 REBOOT=ReallySuppress DEPLOYMENT_SERVER="host:8089" /l*v c:\temp\splunk_install.log LOGON_USERNAME="ClientHostName\user_name" LOGON_PASSWORD="password" AGREETOLICENSE=Yes SET_ADMIN_USER=0 /quiet
0 Karma

muebel
SplunkTrust
SplunkTrust

Hi email2vamsi, you can utilize shell variable to include the hostname in the command, i.e.

#batch %computername%
msiexec /I splunkforwarder-6.1.9-272667-x64-release.msi /qn ALLUSERS=1 REBOOT=ReallySuppress DEPLOYMENT_SERVER="host:8089" /l*v c:\temp\splunk_install.log LOGON_USERNAME="%computername%\user_name" LOGON_PASSWORD="password" AGREETOLICENSE=Yes SET_ADMIN_USER=0 /quiet

#powershell $env:computername
msiexec /I splunkforwarder-6.1.9-272667-x64-release.msi /qn ALLUSERS=1 REBOOT=ReallySuppress DEPLOYMENT_SERVER="host:8089" /l*v c:\temp\splunk_install.log LOGON_USERNAME="$env:computername\user_name" LOGON_PASSWORD="password" AGREETOLICENSE=Yes SET_ADMIN_USER=0 /quiet

Please let me know if this answers your question! 😄

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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...