<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Scripted install thrown by upgrade prompt in Installation</title>
    <link>https://community.splunk.com/t5/Installation/Scripted-install-thrown-by-upgrade-prompt/m-p/46594#M9272</link>
    <description>&lt;P&gt;Have you tried using the /quiet flag? 
&lt;A href="http://www.splunk.com/base/Documentation/latest/installation/installonWindowsviathecommandline" rel="nofollow"&gt;http://www.splunk.com/base/Documentation/latest/installation/installonWindowsviathecommandline&lt;/A&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;Alternatively, I would try with this. Not sure if it works on Windows like it does on Linux, though:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;%SPLUNK_HOME%/bin/splunk start --accept-license --answer-yes
&lt;/CODE&gt;&lt;/PRE&gt;</description>
    <pubDate>Fri, 18 Feb 2011 02:55:24 GMT</pubDate>
    <dc:creator>David</dc:creator>
    <dc:date>2011-02-18T02:55:24Z</dc:date>
    <item>
      <title>Scripted install thrown by upgrade prompt</title>
      <link>https://community.splunk.com/t5/Installation/Scripted-install-thrown-by-upgrade-prompt/m-p/46593#M9271</link>
      <description>&lt;P&gt;I am using a powershell script to deploy Splunk to many servers (circa 150).&lt;/P&gt;

&lt;P&gt;Works a treat UNTIL I try to do an upgrade to a new version at which point my install command fails.&lt;/P&gt;

&lt;P&gt;Splunk is basically detecting the upgrade and prompting me for a y/n.  Can I suppress this prompt and force the upgrade through?&lt;/P&gt;

&lt;P&gt;The output I get is as follows:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;    Splunk has detected an older version of Splunk installed on this machine. 
To finish upgrading to the new version, Splunk's installer will automatically
update and alter your current configuration files. Deprecated configuration
files will be renamed with a .deprecated extension.

You can choose to preview the changes that will be made to your configuration
files before proceeding with the migration and upgrade:

If you want to migrate and upgrade without previewing the changes that will be
made to your existing configuration files, choose 'y'.

If you want to see what changes will be made before you proceed with the
upgrade, choose 'n'. 

Perform migration and upgrade without previewing configuration changes? [y/n] 
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Fri, 18 Feb 2011 01:49:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Scripted-install-thrown-by-upgrade-prompt/m-p/46593#M9271</guid>
      <dc:creator>stuartamurray</dc:creator>
      <dc:date>2011-02-18T01:49:50Z</dc:date>
    </item>
    <item>
      <title>Re: Scripted install thrown by upgrade prompt</title>
      <link>https://community.splunk.com/t5/Installation/Scripted-install-thrown-by-upgrade-prompt/m-p/46594#M9272</link>
      <description>&lt;P&gt;Have you tried using the /quiet flag? 
&lt;A href="http://www.splunk.com/base/Documentation/latest/installation/installonWindowsviathecommandline" rel="nofollow"&gt;http://www.splunk.com/base/Documentation/latest/installation/installonWindowsviathecommandline&lt;/A&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;Alternatively, I would try with this. Not sure if it works on Windows like it does on Linux, though:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;%SPLUNK_HOME%/bin/splunk start --accept-license --answer-yes
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Fri, 18 Feb 2011 02:55:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Scripted-install-thrown-by-upgrade-prompt/m-p/46594#M9272</guid>
      <dc:creator>David</dc:creator>
      <dc:date>2011-02-18T02:55:24Z</dc:date>
    </item>
    <item>
      <title>Re: Scripted install thrown by upgrade prompt</title>
      <link>https://community.splunk.com/t5/Installation/Scripted-install-thrown-by-upgrade-prompt/m-p/46595#M9273</link>
      <description>&lt;P&gt;That output comes when you use a CLI start, I believe, so the &lt;CODE&gt;--accept-license --answer-yes --no-prompt&lt;/CODE&gt; flags will work as they do in the linux version. You may want to look at &lt;A href="http://www.splunk.com/wiki/Deploying_Splunk_Light_Forwarders"&gt;http://www.splunk.com/wiki/Deploying_Splunk_Light_Forwarders&lt;/A&gt; for a (not PowerShell but CMD.exe) script that has suggested commands and methods.&lt;/P&gt;</description>
      <pubDate>Fri, 18 Feb 2011 08:45:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Scripted-install-thrown-by-upgrade-prompt/m-p/46595#M9273</guid>
      <dc:creator>gkanapathy</dc:creator>
      <dc:date>2011-02-18T08:45:39Z</dc:date>
    </item>
    <item>
      <title>Re: Scripted install thrown by upgrade prompt</title>
      <link>https://community.splunk.com/t5/Installation/Scripted-install-thrown-by-upgrade-prompt/m-p/46596#M9274</link>
      <description>&lt;P&gt;Thanks a lot guys.  Much appreciated.  That will teach me to RTFM &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 18 Feb 2011 17:19:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Scripted-install-thrown-by-upgrade-prompt/m-p/46596#M9274</guid>
      <dc:creator>stuartamurray</dc:creator>
      <dc:date>2011-02-18T17:19:15Z</dc:date>
    </item>
  </channel>
</rss>

