<?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: How to distribute splunk.secret to Windows Heavy Forwarders in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-to-distribute-splunk-secret-to-Windows-Heavy-Forwarders/m-p/252532#M48564</link>
    <description>&lt;P&gt;I got it to work but took a little digging.  My command was:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;msiexec.exe /i splunk-6.5.1-f74036626f0c-x64-release.msi AGREETOLICENSE=Yes DEPLOYMENT_SERVER="server:8089" LAUNCHSPLUNK=0 INSTALL_SHORTCUT=0 INSTALLDIR="D:\Program Files\Splunk"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;When the install completed, Splunk was not started but as you mention there was a splunk.secret that encrypted a single entry for sslPassword in the server.conf.  I sync'd that entry with the system where my splunk.secret came from and I now have it working.&lt;/P&gt;

&lt;P&gt;Hope this helps.&lt;/P&gt;</description>
    <pubDate>Wed, 04 Jan 2017 21:48:05 GMT</pubDate>
    <dc:creator>cmutt78</dc:creator>
    <dc:date>2017-01-04T21:48:05Z</dc:date>
    <item>
      <title>How to distribute splunk.secret to Windows Heavy Forwarders</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-distribute-splunk-secret-to-Windows-Heavy-Forwarders/m-p/252531#M48563</link>
      <description>&lt;P&gt;Hello guys,&lt;/P&gt;

&lt;P&gt;We are going to install two Heavy Forwarders on Windows 2012 R2 servers. The remaining instances of Splunk, which build up our distributed architecture, are running on SLES.&lt;/P&gt;

&lt;P&gt;As usual, according to &lt;A href="http://wiki.splunk.com/Things_I_wish_I_knew_then"&gt;best practices&lt;/A&gt;, I was trying to distribute our "master" splunk.secret file to new Heavy Forwarders hosted on Windows servers.&lt;/P&gt;

&lt;P&gt;I tried to install Splunk using the following command line:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;msiexec.exe /i splunk-&amp;lt;...&amp;gt;-x64-release.msi AGREETOLICENSE=Yes WEB_PORT= DEPLOYMENT_SERVER="" LAUNCHSPLUNK=0 INSTALL_SHORTCUT=0
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;As expected the "splunkd" service did not start when installation finished, but unluckily a new splunk.secret was automatically created and contents where encrypted using it.&lt;/P&gt;

&lt;P&gt;So I tried an interactive installation with only the "LAUNCHSPLUNK=0" flag and I monitored the file system: I noticed that the splunk.secret and the encrypted files are created at the same exact time, before the service is started.&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;QUESTION: is it possible to install Splunk on Windows without the creation of a new splunk.secret and the subsequent encryption of data with it, in the same way it is possible in Linux?&lt;/STRONG&gt;&lt;/P&gt;

&lt;P&gt;Thank you!&lt;/P&gt;</description>
      <pubDate>Thu, 01 Dec 2016 12:44:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-distribute-splunk-secret-to-Windows-Heavy-Forwarders/m-p/252531#M48563</guid>
      <dc:creator>mas</dc:creator>
      <dc:date>2016-12-01T12:44:48Z</dc:date>
    </item>
    <item>
      <title>Re: How to distribute splunk.secret to Windows Heavy Forwarders</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-distribute-splunk-secret-to-Windows-Heavy-Forwarders/m-p/252532#M48564</link>
      <description>&lt;P&gt;I got it to work but took a little digging.  My command was:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;msiexec.exe /i splunk-6.5.1-f74036626f0c-x64-release.msi AGREETOLICENSE=Yes DEPLOYMENT_SERVER="server:8089" LAUNCHSPLUNK=0 INSTALL_SHORTCUT=0 INSTALLDIR="D:\Program Files\Splunk"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;When the install completed, Splunk was not started but as you mention there was a splunk.secret that encrypted a single entry for sslPassword in the server.conf.  I sync'd that entry with the system where my splunk.secret came from and I now have it working.&lt;/P&gt;

&lt;P&gt;Hope this helps.&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jan 2017 21:48:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-distribute-splunk-secret-to-Windows-Heavy-Forwarders/m-p/252532#M48564</guid>
      <dc:creator>cmutt78</dc:creator>
      <dc:date>2017-01-04T21:48:05Z</dc:date>
    </item>
    <item>
      <title>Re: How to distribute splunk.secret to Windows Heavy Forwarders</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-distribute-splunk-secret-to-Windows-Heavy-Forwarders/m-p/252533#M48565</link>
      <description>&lt;P&gt;Thank you cmutt78, your solution is working.&lt;/P&gt;

&lt;P&gt;By the way: there is some additional, useful information at this link: &lt;A href="https://wiki.splunk.com/Community:Run_multiple_Splunks_on_one_machine"&gt;https://wiki.splunk.com/Community:Run_multiple_Splunks_on_one_machine&lt;/A&gt; (this is specific for multiple Splunk instances on the same box).&lt;/P&gt;</description>
      <pubDate>Mon, 20 Mar 2017 21:43:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-distribute-splunk-secret-to-Windows-Heavy-Forwarders/m-p/252533#M48565</guid>
      <dc:creator>mas</dc:creator>
      <dc:date>2017-03-20T21:43:28Z</dc:date>
    </item>
  </channel>
</rss>

