<?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: deploymentclient.conf in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/deploymentclient-conf/m-p/70002#M2436</link>
    <description>&lt;P&gt;Why would you want to have two sources of configurations?&lt;/P&gt;</description>
    <pubDate>Thu, 22 Aug 2013 05:02:50 GMT</pubDate>
    <dc:creator>rturk</dc:creator>
    <dc:date>2013-08-22T05:02:50Z</dc:date>
    <item>
      <title>deploymentclient.conf</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/deploymentclient-conf/m-p/70001#M2435</link>
      <description>&lt;P&gt;Is it possibble to have two TargetUri's ?  Will it work?&lt;/P&gt;</description>
      <pubDate>Tue, 25 Sep 2012 15:22:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/deploymentclient-conf/m-p/70001#M2435</guid>
      <dc:creator>mzemcik</dc:creator>
      <dc:date>2012-09-25T15:22:14Z</dc:date>
    </item>
    <item>
      <title>Re: deploymentclient.conf</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/deploymentclient-conf/m-p/70002#M2436</link>
      <description>&lt;P&gt;Why would you want to have two sources of configurations?&lt;/P&gt;</description>
      <pubDate>Thu, 22 Aug 2013 05:02:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/deploymentclient-conf/m-p/70002#M2436</guid>
      <dc:creator>rturk</dc:creator>
      <dc:date>2013-08-22T05:02:50Z</dc:date>
    </item>
    <item>
      <title>Re: deploymentclient.conf</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/deploymentclient-conf/m-p/70003#M2437</link>
      <description>&lt;P&gt;No.  I say no, because deployment servers just don't work that way.&lt;BR /&gt;
You can have multiple deployment servers, but the secondary server is a client of the primary, and clients only communicate with either the primary or secondary, but not both.&lt;/P&gt;

&lt;P&gt;Here are a couple of links that you might find helpful:&lt;/P&gt;

&lt;P&gt;&lt;A href="http://wiki.splunk.com/Deploy:DeploymentServer"&gt;http://wiki.splunk.com/Deploy:DeploymentServer&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;&lt;A href="http://answers.splunk.com/answers/37649/multiple-deployment-servers-configuration"&gt;http://answers.splunk.com/answers/37649/multiple-deployment-servers-configuration&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 22 Aug 2013 14:29:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/deploymentclient-conf/m-p/70003#M2437</guid>
      <dc:creator>lukejadamec</dc:creator>
      <dc:date>2013-08-22T14:29:51Z</dc:date>
    </item>
  </channel>
</rss>

