<?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: Trying to copy license in Installation</title>
    <link>https://community.splunk.com/t5/Installation/Would-it-be-possible-to-obtain-a-copy-of-the-license-in-order-to/m-p/641236#M12812</link>
    <description>&lt;P&gt;OK. There are two things here.&lt;/P&gt;&lt;P&gt;The License itself is a legal document. And it's out of scope of this forum. It's up to you and your Splunk representative (which is kinda funny since your account says "Splunk Employee" ;-)) to discuss whether or not you'd be in violation of license agreement terms and provisions in "mid-migration" (for example if you doubled your ingestion rate because you were sending data to both old and new environments, Splunk might not be happy about that; but then again if it's only for a short time, maybe it would be OK; I don't know I never dug that deep into that).&lt;/P&gt;&lt;P&gt;The license key/license file/however you call that, is a piece of digitally signed XML which - after you upload it - is stored on your license manager in $SPLUNK_HOME/etc/licenses and is easily transferable between hosts.&lt;/P&gt;&lt;P&gt;So technically - yes, you can copy the file over. Legally - it depends if you should/can do so.&lt;/P&gt;&lt;P&gt;In the simplest case - if you just want to move the LM to another machine while keeping all other components intact, just spin up a new LM, copy the config from the old one (adjusting the server names, certificates and IPs if necessary), point your license peers to a new LM (easy to do if you have config managed with apps, more manual work if you have the config in system/local), after a day or two retire the old LM and you're done.&lt;/P&gt;</description>
    <pubDate>Tue, 25 Apr 2023 08:37:43 GMT</pubDate>
    <dc:creator>PickleRick</dc:creator>
    <dc:date>2023-04-25T08:37:43Z</dc:date>
    <item>
      <title>Would it be possible to obtain a copy of the license, in order to transfer it to the new License Manager?</title>
      <link>https://community.splunk.com/t5/Installation/Would-it-be-possible-to-obtain-a-copy-of-the-license-in-order-to/m-p/641235#M12811</link>
      <description>&lt;P&gt;&lt;SPAN&gt;As part of the migration of the Splunk infrastructure, would it be possible to obtain a copy of the license, in order to transfer it to the new License Manager&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 25 Apr 2023 15:15:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Would-it-be-possible-to-obtain-a-copy-of-the-license-in-order-to/m-p/641235#M12811</guid>
      <dc:creator>thashmi</dc:creator>
      <dc:date>2023-04-25T15:15:14Z</dc:date>
    </item>
    <item>
      <title>Re: Trying to copy license</title>
      <link>https://community.splunk.com/t5/Installation/Would-it-be-possible-to-obtain-a-copy-of-the-license-in-order-to/m-p/641236#M12812</link>
      <description>&lt;P&gt;OK. There are two things here.&lt;/P&gt;&lt;P&gt;The License itself is a legal document. And it's out of scope of this forum. It's up to you and your Splunk representative (which is kinda funny since your account says "Splunk Employee" ;-)) to discuss whether or not you'd be in violation of license agreement terms and provisions in "mid-migration" (for example if you doubled your ingestion rate because you were sending data to both old and new environments, Splunk might not be happy about that; but then again if it's only for a short time, maybe it would be OK; I don't know I never dug that deep into that).&lt;/P&gt;&lt;P&gt;The license key/license file/however you call that, is a piece of digitally signed XML which - after you upload it - is stored on your license manager in $SPLUNK_HOME/etc/licenses and is easily transferable between hosts.&lt;/P&gt;&lt;P&gt;So technically - yes, you can copy the file over. Legally - it depends if you should/can do so.&lt;/P&gt;&lt;P&gt;In the simplest case - if you just want to move the LM to another machine while keeping all other components intact, just spin up a new LM, copy the config from the old one (adjusting the server names, certificates and IPs if necessary), point your license peers to a new LM (easy to do if you have config managed with apps, more manual work if you have the config in system/local), after a day or two retire the old LM and you're done.&lt;/P&gt;</description>
      <pubDate>Tue, 25 Apr 2023 08:37:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Would-it-be-possible-to-obtain-a-copy-of-the-license-in-order-to/m-p/641236#M12812</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2023-04-25T08:37:43Z</dc:date>
    </item>
  </channel>
</rss>

