<?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 Set up Splunk Enterprise- Forwarders and Receivers? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-to-Set-up-Splunk-Enterprise-Forwarders-and-Receivers/m-p/501669#M85481</link>
    <description>&lt;P&gt;You have the general idea.  Allow me to add some tips.&lt;/P&gt;

&lt;P&gt;1) Run Splunk Enterprise on a Linux server if you can.  You'll be much happier if you do.&lt;BR /&gt;
2) If you run Splunk on Windows, don't use a domain account.&lt;BR /&gt;
3) The Universal Forwarders should get their configuration files from a Splunk Deployment Server (DS).  Using a DS means you don't need to sign in to each server/workstation to update the UF configs.&lt;BR /&gt;
4) You don't say how many users will be using Splunk or what hardware Splunk will be on, but I expect you will quickly outgrow a standalone Splunk server.  If this is not just a sandbox, consider setting up a distributed environment with separate search head and indexer servers.&lt;/P&gt;</description>
    <pubDate>Fri, 27 Mar 2020 15:26:46 GMT</pubDate>
    <dc:creator>richgalloway</dc:creator>
    <dc:date>2020-03-27T15:26:46Z</dc:date>
    <item>
      <title>How to Set up Splunk Enterprise- Forwarders and Receivers?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-Set-up-Splunk-Enterprise-Forwarders-and-Receivers/m-p/501668#M85480</link>
      <description>&lt;P&gt;I am trying to understand how to set up Splunk for the first time. I have several Server VMs (exchange, DC, SCCM, Splunk) and about 70 workstations. &lt;/P&gt;

&lt;P&gt;I want to use Splunk to audit my workstations' event logs. This is a high level overview on how I understand that to occur:&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;Install Splunk Enterprise on my Splunk Server (set up permissions as a domain user, etc)&lt;/LI&gt;
&lt;LI&gt;Configure Splunk Server as a Receiver&lt;/LI&gt;
&lt;LI&gt;Install a Universal Forwarder on every workstation and all of the other servers.&lt;/LI&gt;
&lt;LI&gt;Configure each Universal Forwarder- define inputs on the universal forwarder with configuration files&lt;/LI&gt;
&lt;/OL&gt;

&lt;P&gt;Am I understanding this correctly?&lt;/P&gt;</description>
      <pubDate>Fri, 27 Mar 2020 13:36:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-Set-up-Splunk-Enterprise-Forwarders-and-Receivers/m-p/501668#M85480</guid>
      <dc:creator>danielleedgingt</dc:creator>
      <dc:date>2020-03-27T13:36:35Z</dc:date>
    </item>
    <item>
      <title>Re: How to Set up Splunk Enterprise- Forwarders and Receivers?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-Set-up-Splunk-Enterprise-Forwarders-and-Receivers/m-p/501669#M85481</link>
      <description>&lt;P&gt;You have the general idea.  Allow me to add some tips.&lt;/P&gt;

&lt;P&gt;1) Run Splunk Enterprise on a Linux server if you can.  You'll be much happier if you do.&lt;BR /&gt;
2) If you run Splunk on Windows, don't use a domain account.&lt;BR /&gt;
3) The Universal Forwarders should get their configuration files from a Splunk Deployment Server (DS).  Using a DS means you don't need to sign in to each server/workstation to update the UF configs.&lt;BR /&gt;
4) You don't say how many users will be using Splunk or what hardware Splunk will be on, but I expect you will quickly outgrow a standalone Splunk server.  If this is not just a sandbox, consider setting up a distributed environment with separate search head and indexer servers.&lt;/P&gt;</description>
      <pubDate>Fri, 27 Mar 2020 15:26:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-Set-up-Splunk-Enterprise-Forwarders-and-Receivers/m-p/501669#M85481</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2020-03-27T15:26:46Z</dc:date>
    </item>
    <item>
      <title>Re: How to Set up Splunk Enterprise- Forwarders and Receivers?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-Set-up-Splunk-Enterprise-Forwarders-and-Receivers/m-p/501670#M85482</link>
      <description>&lt;P&gt;Hi @danielleedgington92,&lt;BR /&gt;
in addition to all the hints of @richgalloway , I suggest to create a Technical Add-on (called e.f. TA_Forwarders): it's an app  containing only two files:&lt;/P&gt;

&lt;UL&gt;
&lt;LI&gt;deploymentclient.conf&lt;/LI&gt;
&lt;LI&gt;outputs.conf&lt;/LI&gt;
&lt;/UL&gt;

&lt;P&gt;The first one contains the address of the Deployment Server (remember that if you have to manage more than 50 target servers you must have a dedicated server for this role!).&lt;BR /&gt;
The second one contains the addresses of the indexers.&lt;/P&gt;

&lt;P&gt;In this way you can manage all the configurations by Deployment Server.&lt;BR /&gt;
The problem is how to rich the Deployment Server for the first time: for this reason, I usually copy this app (TA_Forwarders) on each target server (and I restart Splunk on UF), so it's connected with the Deployment Server and I can deploy to all the UFs the TAs I need.&lt;/P&gt;

&lt;P&gt;Ciao.&lt;BR /&gt;
Giuseppe&lt;/P&gt;</description>
      <pubDate>Fri, 27 Mar 2020 15:34:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-Set-up-Splunk-Enterprise-Forwarders-and-Receivers/m-p/501670#M85482</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2020-03-27T15:34:52Z</dc:date>
    </item>
  </channel>
</rss>

