<?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: Set the tcpout server via the CLI at installation in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Set-the-tcpout-server-via-the-CLI-at-installation/m-p/186367#M37338</link>
    <description>&lt;P&gt;If you have a lot of forwarders best to push configs with a deployment server.  This approach let's you keep all your configs in one place.  I even use the DS to manage multiple indexers.&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.2.1/Updating/Aboutdeploymentserver"&gt;http://docs.splunk.com/Documentation/Splunk/6.2.1/Updating/Aboutdeploymentserver&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 19 Jan 2015 14:23:17 GMT</pubDate>
    <dc:creator>thomrs</dc:creator>
    <dc:date>2015-01-19T14:23:17Z</dc:date>
    <item>
      <title>Set the tcpout server via the CLI at installation</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Set-the-tcpout-server-via-the-CLI-at-installation/m-p/186364#M37335</link>
      <description>&lt;P&gt;Im using powershell to install universal forwarders on the new machines that im spinning up using the following command:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;cmd /c "msiexec.exe /i splunkforwarder-6.2.1-245427-x64-release.msi AGREETOLICENSE=Yes RECEIVING_INDEXER='simdc01:9997' MONITOR_PATH='c:\logs' PERFMON=cpu,memory,network,diskspace /quiet"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;But this does not create an outputs.conf file containing the tcp settings so im doing this in powershell to manually create the file needed&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;$outputsConfString = @"
[tcpout]
defaultGroup = indexers

[tcpout:indexers]
server = simdc01:9997
"@

New-Item "C:\Program Files\SplunkUniversalForwarder\etc\system\local\outputs.conf" -type file -force -value $outputsConfString
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;My question is, is there a way to do this via the CLI or am i stuck with this hack?&lt;BR /&gt;
It feels wrong to have to hack files in this way when there is tooling provided to automate things.&lt;/P&gt;</description>
      <pubDate>Mon, 19 Jan 2015 13:42:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Set-the-tcpout-server-via-the-CLI-at-installation/m-p/186364#M37335</guid>
      <dc:creator>damian_ingenie_</dc:creator>
      <dc:date>2015-01-19T13:42:35Z</dc:date>
    </item>
    <item>
      <title>Re: Set the tcpout server via the CLI at installation</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Set-the-tcpout-server-via-the-CLI-at-installation/m-p/186365#M37336</link>
      <description>&lt;P&gt;This should do the trick.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;./splunk add forward-server &amp;lt;indexer&amp;gt;:port -auth admin:password
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.2.1/Admin/CLIadmincommands"&gt;http://docs.splunk.com/Documentation/Splunk/6.2.1/Admin/CLIadmincommands&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 19 Jan 2015 13:58:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Set-the-tcpout-server-via-the-CLI-at-installation/m-p/186365#M37336</guid>
      <dc:creator>trsavela</dc:creator>
      <dc:date>2015-01-19T13:58:08Z</dc:date>
    </item>
    <item>
      <title>Re: Set the tcpout server via the CLI at installation</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Set-the-tcpout-server-via-the-CLI-at-installation/m-p/186366#M37337</link>
      <description>&lt;P&gt;you should be able just to provide the &lt;CODE&gt;RECEIVING_INDEXER&lt;/CODE&gt; &lt;A href="http://docs.splunk.com/Documentation/Splunk/6.2.1/Forwarding/RemotelydeployaWindowsdfwithastaticconfiguration"&gt;http://docs.splunk.com/Documentation/Splunk/6.2.1/Forwarding/RemotelydeployaWindowsdfwithastaticconfiguration&lt;/A&gt; during initial install as well ... but it is not honored in this case....&lt;/P&gt;</description>
      <pubDate>Mon, 19 Jan 2015 14:03:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Set-the-tcpout-server-via-the-CLI-at-installation/m-p/186366#M37337</guid>
      <dc:creator>MuS</dc:creator>
      <dc:date>2015-01-19T14:03:28Z</dc:date>
    </item>
    <item>
      <title>Re: Set the tcpout server via the CLI at installation</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Set-the-tcpout-server-via-the-CLI-at-installation/m-p/186367#M37338</link>
      <description>&lt;P&gt;If you have a lot of forwarders best to push configs with a deployment server.  This approach let's you keep all your configs in one place.  I even use the DS to manage multiple indexers.&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.2.1/Updating/Aboutdeploymentserver"&gt;http://docs.splunk.com/Documentation/Splunk/6.2.1/Updating/Aboutdeploymentserver&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 19 Jan 2015 14:23:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Set-the-tcpout-server-via-the-CLI-at-installation/m-p/186367#M37338</guid>
      <dc:creator>thomrs</dc:creator>
      <dc:date>2015-01-19T14:23:17Z</dc:date>
    </item>
    <item>
      <title>Re: Set the tcpout server via the CLI at installation</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Set-the-tcpout-server-via-the-CLI-at-installation/m-p/186368#M37339</link>
      <description>&lt;P&gt;Spot on, thanks&lt;/P&gt;</description>
      <pubDate>Mon, 19 Jan 2015 15:30:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Set-the-tcpout-server-via-the-CLI-at-installation/m-p/186368#M37339</guid>
      <dc:creator>damian_ingenie_</dc:creator>
      <dc:date>2015-01-19T15:30:53Z</dc:date>
    </item>
    <item>
      <title>Re: Set the tcpout server via the CLI at installation</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Set-the-tcpout-server-via-the-CLI-at-installation/m-p/186369#M37340</link>
      <description>&lt;P&gt;as you can see from my example command line in the question RECEIVING_INDEXER is there, but it does not work... none of the outputs.conf files are modified with that switch. which is what has lead me to ask this question.&lt;/P&gt;</description>
      <pubDate>Mon, 19 Jan 2015 15:48:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Set-the-tcpout-server-via-the-CLI-at-installation/m-p/186369#M37340</guid>
      <dc:creator>damian_ingenie_</dc:creator>
      <dc:date>2015-01-19T15:48:28Z</dc:date>
    </item>
    <item>
      <title>Re: Set the tcpout server via the CLI at installation</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Set-the-tcpout-server-via-the-CLI-at-installation/m-p/186370#M37341</link>
      <description>&lt;P&gt;Ok tried it myself with the file &lt;CODE&gt;splunkforwarder-6.2.1-245427-x64-release.msi&lt;/CODE&gt; and the following command:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;msiexec.exe /i splunkforwarder-6.2.1-245427-x64-release.msi RECEIVING_INDEXER="foo:9997" WINEVENTLOG_SEC_ENABLE=1 WINEVENTLOG_SYS_ENABLE=1 AGREETOLICENSE=Yes /quiet
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;this adds in &lt;CODE&gt;$SPLUNK_HOME/etc/system/local/outputs.conf&lt;/CODE&gt; this entry:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[tcpout]
defaultGroup = default-autolb-group

[tcpout:default-autolb-group]
server = foo:9997

[tcpout-server://foo:9997]
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Maybe you need to download a fresh copy of the msi or you found a bug &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 20 Jan 2015 07:38:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Set-the-tcpout-server-via-the-CLI-at-installation/m-p/186370#M37341</guid>
      <dc:creator>MuS</dc:creator>
      <dc:date>2015-01-20T07:38:52Z</dc:date>
    </item>
  </channel>
</rss>

