<?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: duplicate license in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/duplicate-license/m-p/176914#M6587</link>
    <description>&lt;P&gt;Which version of splunk you are using? Have you checked that you have not added license on your search head?&lt;/P&gt;

&lt;P&gt;Check if this applicable in your case - &lt;A href="http://answers.splunk.com/answers/8475/distributed-search-issue-duplicate-licenses"&gt;http://answers.splunk.com/answers/8475/distributed-search-issue-duplicate-licenses&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Sat, 09 Aug 2014 15:30:19 GMT</pubDate>
    <dc:creator>strive</dc:creator>
    <dc:date>2014-08-09T15:30:19Z</dc:date>
    <item>
      <title>duplicate license</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/duplicate-license/m-p/176913#M6586</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I am building out a new dev environment, and I just created a bunch of new indexers on brand new vm's.  I also setup a search-head, and pointed it at my dev license mgr.  So far, so good.   However, when I setup distributed-searching, I am getting a "duplicate license" on the new search-head.  All the new servers are pointing at my dev license mgr.  I logged into my dev license mgr, and looked at the licensing and the distributed-searching, and I don't see that message anywhere. &lt;/P&gt;

&lt;P&gt;Any suggestions?  &lt;/P&gt;</description>
      <pubDate>Sat, 09 Aug 2014 15:07:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/duplicate-license/m-p/176913#M6586</guid>
      <dc:creator>a212830</dc:creator>
      <dc:date>2014-08-09T15:07:31Z</dc:date>
    </item>
    <item>
      <title>Re: duplicate license</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/duplicate-license/m-p/176914#M6587</link>
      <description>&lt;P&gt;Which version of splunk you are using? Have you checked that you have not added license on your search head?&lt;/P&gt;

&lt;P&gt;Check if this applicable in your case - &lt;A href="http://answers.splunk.com/answers/8475/distributed-search-issue-duplicate-licenses"&gt;http://answers.splunk.com/answers/8475/distributed-search-issue-duplicate-licenses&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 09 Aug 2014 15:30:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/duplicate-license/m-p/176914#M6587</guid>
      <dc:creator>strive</dc:creator>
      <dc:date>2014-08-09T15:30:19Z</dc:date>
    </item>
    <item>
      <title>Re: duplicate license</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/duplicate-license/m-p/176915#M6588</link>
      <description>&lt;P&gt;Never mind - my bad.  License file got moved over by mistake as part of the chef recipe.&lt;/P&gt;</description>
      <pubDate>Sat, 09 Aug 2014 15:59:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/duplicate-license/m-p/176915#M6588</guid>
      <dc:creator>a212830</dc:creator>
      <dc:date>2014-08-09T15:59:20Z</dc:date>
    </item>
    <item>
      <title>Re: duplicate license</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/duplicate-license/m-p/176916#M6589</link>
      <description>&lt;P&gt;Good to know that you found out where it was hiding &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 09 Aug 2014 16:59:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/duplicate-license/m-p/176916#M6589</guid>
      <dc:creator>strive</dc:creator>
      <dc:date>2014-08-09T16:59:21Z</dc:date>
    </item>
  </channel>
</rss>

