https://community.splunk.com/t5/Getting-Data-In/How-to-troubleshoot-why-our-command-to-install-a-Splunk/m-p/244214#M47255 <P>OK, Try this to see if it writes a log.:</P> <PRE><CODE>msiexec.exe /i "splunkforwarder-x.x.x-xxxxx-x64-release.msi" ALLUSERS=1 /qn /norestart /log output.log AGREETOLICENSE=Yes </CODE></PRE> <P>I had issues with several machines when using an auto-deployer like SCCM or PDQ Deply. I got back messages saying the product was already deployed, when it really wasn't.</P> Tue, 10 May 2016 17:21:41 GMT bsachitano 2016-05-10T17:21:41Z https://community.splunk.com/t5/Getting-Data-In/How-to-troubleshoot-why-our-command-to-install-a-Splunk/m-p/244211#M47252 <P>We have been running <CODE>msiexec.exe /i "c:\SFTPRoot\splunkforwarder-x.x.x-xxxx-x64-release.msi" AGREETOLICENSE=Yes /quiet</CODE> to install a Splunk forwarder on our firewall servers that do not have RDP access; However, of recent, we are running into an issue where this command is not working anymore and we are not receiving any indication as to why it fails. </P> <P>Does anyone have experience with doing this type of restricted install and/or Windows command line ideas?</P> <P>Thank you in advance.</P> Tue, 10 May 2016 14:00:41 GMT https://community.splunk.com/t5/Getting-Data-In/How-to-troubleshoot-why-our-command-to-install-a-Splunk/m-p/244211#M47252 CaptainHook 2016-05-10T14:00:41Z https://community.splunk.com/t5/Getting-Data-In/How-to-troubleshoot-why-our-command-to-install-a-Splunk/m-p/244212#M47253 <P>Add logging to your command to see why it's failing. </P> <P>Try running:</P> <PRE><CODE>msiexec.exe /i "c:\SFTPRoot\splunkforwarder-x.x.x-xxxx-x64-release.msi" /L C:\logfile.txt </CODE></PRE> <P>Then evaluate the file.</P> Tue, 10 May 2016 14:23:48 GMT https://community.splunk.com/t5/Getting-Data-In/How-to-troubleshoot-why-our-command-to-install-a-Splunk/m-p/244212#M47253 bsachitano 2016-05-10T14:23:48Z https://community.splunk.com/t5/Getting-Data-In/How-to-troubleshoot-why-our-command-to-install-a-Splunk/m-p/244213#M47254 <P>I had since tried that by running this:</P> <PRE><CODE>msiexec.exe /i "C:\Users\srvHPOM\Downloads\ splunkforwarder-x.x.x-xxxx-x64-release.msi" /L*V C:\Users\srvHPOM\Downloads\myinstall.log" AGREETOLICENSE=Yes </CODE></PRE> <P>It was unsuccessful and wrote a log with 0b.</P> Tue, 10 May 2016 16:50:02 GMT https://community.splunk.com/t5/Getting-Data-In/How-to-troubleshoot-why-our-command-to-install-a-Splunk/m-p/244213#M47254 CaptainHook 2016-05-10T16:50:02Z https://community.splunk.com/t5/Getting-Data-In/How-to-troubleshoot-why-our-command-to-install-a-Splunk/m-p/244214#M47255 <P>OK, Try this to see if it writes a log.:</P> <PRE><CODE>msiexec.exe /i "splunkforwarder-x.x.x-xxxxx-x64-release.msi" ALLUSERS=1 /qn /norestart /log output.log AGREETOLICENSE=Yes </CODE></PRE> <P>I had issues with several machines when using an auto-deployer like SCCM or PDQ Deply. I got back messages saying the product was already deployed, when it really wasn't.</P> Tue, 10 May 2016 17:21:41 GMT https://community.splunk.com/t5/Getting-Data-In/How-to-troubleshoot-why-our-command-to-install-a-Splunk/m-p/244214#M47255 bsachitano 2016-05-10T17:21:41Z https://community.splunk.com/t5/Getting-Data-In/How-to-troubleshoot-why-our-command-to-install-a-Splunk/m-p/244215#M47256 <P>Thank you very much. I will try this when I get a moment today and let you know.</P> Tue, 10 May 2016 18:10:33 GMT https://community.splunk.com/t5/Getting-Data-In/How-to-troubleshoot-why-our-command-to-install-a-Splunk/m-p/244215#M47256 CaptainHook 2016-05-10T18:10:33Z https://community.splunk.com/t5/Getting-Data-In/How-to-troubleshoot-why-our-command-to-install-a-Splunk/m-p/244216#M47257 <P>Any luck? </P> Mon, 13 Jun 2016 20:28:22 GMT https://community.splunk.com/t5/Getting-Data-In/How-to-troubleshoot-why-our-command-to-install-a-Splunk/m-p/244216#M47257 sloshburch 2016-06-13T20:28:22Z