<?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 Legacy ISE Device Admin License with ISE 2.4 in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/legacy-ise-device-admin-license-with-ise-2-4/m-p/3767629#M486817</link>
    <description>&lt;P&gt;&lt;A href="https://www.cisco.com/c/dam/en/us/products/collateral/security/identity-services-engine/guide_c07-656177.pdf" target="_blank"&gt;https://www.cisco.com/c/dam/en/us/products/collateral/security/identity-services-engine/guide_c07-656177.pdf&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Table 18 of the ISE Licensing Guide suggests that we can still purchase 1 Legacy Device Admin license.&amp;nbsp; I understand that if I applied the legacy license to a 2.2 deployment, upgraded to 2.4, then it would migrate to 50 node licenses.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;However, if I purchase 1 legacy license, and apply it to a net-new ISE 2.4 deployment, what occurs? Would it error out and apply nothing? Would 50 node licenses appear?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The&amp;nbsp;reason for&amp;nbsp;the question is I am trying to deploy ISE 2.4 in a new environment and they need 2 node licenses, and I would prefer to not install 2.2, apply the license, and then immediately upgrade to 2.4...&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 20 Dec 2018 22:57:46 GMT</pubDate>
    <dc:creator>jorreyno</dc:creator>
    <dc:date>2018-12-20T22:57:46Z</dc:date>
    <item>
      <title>Legacy ISE Device Admin License with ISE 2.4</title>
      <link>https://community.cisco.com/t5/network-access-control/legacy-ise-device-admin-license-with-ise-2-4/m-p/3767629#M486817</link>
      <description>&lt;P&gt;&lt;A href="https://www.cisco.com/c/dam/en/us/products/collateral/security/identity-services-engine/guide_c07-656177.pdf" target="_blank"&gt;https://www.cisco.com/c/dam/en/us/products/collateral/security/identity-services-engine/guide_c07-656177.pdf&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Table 18 of the ISE Licensing Guide suggests that we can still purchase 1 Legacy Device Admin license.&amp;nbsp; I understand that if I applied the legacy license to a 2.2 deployment, upgraded to 2.4, then it would migrate to 50 node licenses.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;However, if I purchase 1 legacy license, and apply it to a net-new ISE 2.4 deployment, what occurs? Would it error out and apply nothing? Would 50 node licenses appear?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The&amp;nbsp;reason for&amp;nbsp;the question is I am trying to deploy ISE 2.4 in a new environment and they need 2 node licenses, and I would prefer to not install 2.2, apply the license, and then immediately upgrade to 2.4...&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 20 Dec 2018 22:57:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/legacy-ise-device-admin-license-with-ise-2-4/m-p/3767629#M486817</guid>
      <dc:creator>jorreyno</dc:creator>
      <dc:date>2018-12-20T22:57:46Z</dc:date>
    </item>
    <item>
      <title>Re: Legacy ISE Device Admin License with ISE 2.4</title>
      <link>https://community.cisco.com/t5/network-access-control/legacy-ise-device-admin-license-with-ise-2-4/m-p/3767648#M486820</link>
      <description>&lt;P&gt;You can still purchase the old Device Admin SKU (goes end of sale Feb 2019) and apply it to a fresh ISE 2.4 install (and it's valid for 50 PSN's).&amp;nbsp; The new SKU costs roughly double as much and only supports 1 PSN.&amp;nbsp; Get it while you can!!!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 20 Dec 2018 23:38:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/legacy-ise-device-admin-license-with-ise-2-4/m-p/3767648#M486820</guid>
      <dc:creator>Arne Bier</dc:creator>
      <dc:date>2018-12-20T23:38:07Z</dc:date>
    </item>
    <item>
      <title>Re: Legacy ISE Device Admin License with ISE 2.4</title>
      <link>https://community.cisco.com/t5/network-access-control/legacy-ise-device-admin-license-with-ise-2-4/m-p/3767657#M486825</link>
      <description>&lt;P&gt;I really want to believe this, but then why would the per-node SKU even be an option? It's more than 2x the price and 1/50 the value...&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This answer suggests that the new SKU would never be sold under any&amp;nbsp;circumstance&amp;nbsp;until the old SKU is retired.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Dec 2018 00:26:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/legacy-ise-device-admin-license-with-ise-2-4/m-p/3767657#M486825</guid>
      <dc:creator>jorreyno</dc:creator>
      <dc:date>2018-12-21T00:26:14Z</dc:date>
    </item>
    <item>
      <title>Re: Legacy ISE Device Admin License with ISE 2.4</title>
      <link>https://community.cisco.com/t5/network-access-control/legacy-ise-device-admin-license-with-ise-2-4/m-p/3767666#M486828</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/174131"&gt;@jorreyno&lt;/a&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This is such a common question.&amp;nbsp; I replied to a similar thread the other day - &lt;A href="https://community.cisco.com/t5/identity-services-engine-ise/ise-2-4-tacacs-license/m-p/3766253#M21965" target="_self"&gt;have a look here&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The answer lies with the ISE Product Management.&amp;nbsp; My theory is that when TACACS was introduced as a feature in ISE 2.0, they needed to make ISE look appealing enough to sway customers from their beloved ACS.&amp;nbsp; And ACS needed to be end of life'd.&amp;nbsp; So the BU made the TACACS pricing attractive.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Now reality has set in &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&amp;nbsp; - your assumption about the availability of the new SKU is wrong - you CAN purchase it.&amp;nbsp; Cisco doesn't make up SKU's that are not available for sale.&amp;nbsp; The question is whether or not you WANT to buy it now.&amp;nbsp; My guess is NO!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It's a lot of money to pay for TACACS feature - I agree.&lt;/P&gt;
&lt;P&gt;The alternative is to use Radius instead.&amp;nbsp; Let's face it - not everyone needs per command authorization. If all you need is to grant a user lvl15 or lvl1 etc - then Radius does the job too.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Dec 2018 01:43:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/legacy-ise-device-admin-license-with-ise-2-4/m-p/3767666#M486828</guid>
      <dc:creator>Arne Bier</dc:creator>
      <dc:date>2018-12-21T01:43:32Z</dc:date>
    </item>
  </channel>
</rss>

