<?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: ISE 2.2 recommended version in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-2-2-recommended-version/m-p/3770118#M486682</link>
    <description>&lt;P&gt;ISE 2.2 is a long term support release, as 2.4 will also be.&amp;nbsp; The BU has&amp;nbsp;recently added recommendations to the ISE software download page, 2.4 is now the "gold star" release when used with patch 5.&amp;nbsp;&amp;nbsp;Your customer should start planning an upgrade to 2.4, but they can stay on 2.2 for the foreseeable future (until EOS is announced at least) if they do not require any new features.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;2.2 patch 11 and 2.4 patch 4 were deferred, both releases had an AD bug regression that you either hit or didn't.&amp;nbsp; 2.2 Patch 12 or 2.4 patch 5 are both considered stable and I would run either in production.&amp;nbsp; The release notes for each release will cover the resolved bugs per patch level, the most recent&amp;nbsp;patch including all previous patch fixes as well.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Resolved caveats&lt;BR /&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/ise/2-2/release_notes/ise22_rn.html#pgfId-810214" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/security/ise/2-2/release_notes/ise22_rn.html#pgfId-810214&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;2.2 open caveats&lt;BR /&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/ise/2-2/release_notes/ise22_rn.html#pgfId-747245" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/security/ise/2-2/release_notes/ise22_rn.html#pgfId-747245&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;As with any ISE upgrade/patch, review the release notes, review the bug tracker, test in a QA environment if available.&amp;nbsp; At least with ISE patching, if you encounter any show stopping bug, rolling back is relatively painless.&amp;nbsp;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="ise-rec.JPG" style="width: 706px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/26796i233CC48C06CF7C58/image-dimensions/706x305?v=v2" width="706" height="305" role="button" title="ise-rec.JPG" alt="ise-rec.JPG" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 28 Dec 2018 19:01:21 GMT</pubDate>
    <dc:creator>Damien Miller</dc:creator>
    <dc:date>2018-12-28T19:01:21Z</dc:date>
    <item>
      <title>ISE 2.2 recommended version</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-2-recommended-version/m-p/3770089#M486677</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;we have a customer that has ISE 2.2 Patch 7 in production. What is the TAC recommended version right now (Dez 2019) ? ISE 2.2 patch X or already 2.4 ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If 2.2 with a certain patch level =&amp;gt; did anybody face problems when upgrading ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 28 Dec 2018 17:59:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-2-recommended-version/m-p/3770089#M486677</guid>
      <dc:creator>Is101008</dc:creator>
      <dc:date>2018-12-28T17:59:16Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.2 recommended version</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-2-recommended-version/m-p/3770101#M486680</link>
      <description>I suggest to move from 2.2 because it wasn't' a stable release. There are&lt;BR /&gt;many patches released for it which is a good thing but further versions&lt;BR /&gt;uses policy-sets instead of policies for authentication and authorization&lt;BR /&gt;which might be a significant change for future. Hence I suggest to move&lt;BR /&gt;asap.&lt;BR /&gt;</description>
      <pubDate>Fri, 28 Dec 2018 18:17:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-2-recommended-version/m-p/3770101#M486680</guid>
      <dc:creator>Mohammed al Baqari</dc:creator>
      <dc:date>2018-12-28T18:17:13Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.2 recommended version</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-2-recommended-version/m-p/3770118#M486682</link>
      <description>&lt;P&gt;ISE 2.2 is a long term support release, as 2.4 will also be.&amp;nbsp; The BU has&amp;nbsp;recently added recommendations to the ISE software download page, 2.4 is now the "gold star" release when used with patch 5.&amp;nbsp;&amp;nbsp;Your customer should start planning an upgrade to 2.4, but they can stay on 2.2 for the foreseeable future (until EOS is announced at least) if they do not require any new features.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;2.2 patch 11 and 2.4 patch 4 were deferred, both releases had an AD bug regression that you either hit or didn't.&amp;nbsp; 2.2 Patch 12 or 2.4 patch 5 are both considered stable and I would run either in production.&amp;nbsp; The release notes for each release will cover the resolved bugs per patch level, the most recent&amp;nbsp;patch including all previous patch fixes as well.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Resolved caveats&lt;BR /&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/ise/2-2/release_notes/ise22_rn.html#pgfId-810214" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/security/ise/2-2/release_notes/ise22_rn.html#pgfId-810214&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;2.2 open caveats&lt;BR /&gt;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/ise/2-2/release_notes/ise22_rn.html#pgfId-747245" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/security/ise/2-2/release_notes/ise22_rn.html#pgfId-747245&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;As with any ISE upgrade/patch, review the release notes, review the bug tracker, test in a QA environment if available.&amp;nbsp; At least with ISE patching, if you encounter any show stopping bug, rolling back is relatively painless.&amp;nbsp;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="ise-rec.JPG" style="width: 706px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/26796i233CC48C06CF7C58/image-dimensions/706x305?v=v2" width="706" height="305" role="button" title="ise-rec.JPG" alt="ise-rec.JPG" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 28 Dec 2018 19:01:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-2-recommended-version/m-p/3770118#M486682</guid>
      <dc:creator>Damien Miller</dc:creator>
      <dc:date>2018-12-28T19:01:21Z</dc:date>
    </item>
  </channel>
</rss>

