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

Index This | What’s a riddle wrapped in an enigma?

September 2025 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with this ...

BORE at .conf25

Boss Of Regular Expression (BORE) was an interactive session run again this year at .conf25 by the brilliant ...

OpenTelemetry for Legacy Apps? Yes, You Can!

This article is a follow-up to my previous article posted on the OpenTelemetry Blog, "Your Critical Legacy App ...