<?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: DEPLOYING ISE 2.3 in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/deploying-ise-2-3/m-p/3421553#M519948</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have been deploying 2.3 since it came out and have converted 8-10 customers to it.&amp;nbsp; I wouldn't do anything but 2.3 at this point.&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 13 Nov 2017 13:22:45 GMT</pubDate>
    <dc:creator>paul</dc:creator>
    <dc:date>2017-11-13T13:22:45Z</dc:date>
    <item>
      <title>DEPLOYING ISE 2.3</title>
      <link>https://community.cisco.com/t5/network-access-control/deploying-ise-2-3/m-p/3421552#M519944</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am planning to deploy ISE 2.3 for a customer.&lt;/P&gt;&lt;P&gt;I have a colleague that discourage going for ISE 2.3 now due to his own experience with 2.3. &lt;SPAN style="font-size: 13.3333px;"&gt;Any advise from anyone who has deployed or has information about 2.3?&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 13 Nov 2017 07:24:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/deploying-ise-2-3/m-p/3421552#M519944</guid>
      <dc:creator>kajibola</dc:creator>
      <dc:date>2017-11-13T07:24:22Z</dc:date>
    </item>
    <item>
      <title>Re: DEPLOYING ISE 2.3</title>
      <link>https://community.cisco.com/t5/network-access-control/deploying-ise-2-3/m-p/3421553#M519948</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have been deploying 2.3 since it came out and have converted 8-10 customers to it.&amp;nbsp; I wouldn't do anything but 2.3 at this point.&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 13 Nov 2017 13:22:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/deploying-ise-2-3/m-p/3421553#M519948</guid>
      <dc:creator>paul</dc:creator>
      <dc:date>2017-11-13T13:22:45Z</dc:date>
    </item>
    <item>
      <title>Re: DEPLOYING ISE 2.3</title>
      <link>https://community.cisco.com/t5/network-access-control/deploying-ise-2-3/m-p/3421554#M519955</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;To answer the question factually we'd need some means of representing ISE versions and feature sets in a matrix, combined with TAC cases, bugs raised and general customer sentiment.&amp;nbsp; I don't think that information exists (perhaps partially inside Cisco, bug trending etc.) , so we're left with sharing our own opinions - good and bad. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My 2c worth about ISE 2.2 and Sponsored Guest features and TACACS - stay away from it.&amp;nbsp; I &lt;SPAN style="text-decoration: line-through;"&gt;upgraded&lt;/SPAN&gt; rebuilt to 2.3 the other day and I have not had a chance to see if it's any better.&amp;nbsp; Some folks might deploy two nodes and use it for 802.1X wireless and that's it.&amp;nbsp; No issues most probably.&amp;nbsp; My advice would be to test the product in the lab as much as possible (which itself can be a costly exercise). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Maybe ISE 2.3 will be the first decent release in the 2.x train.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Nov 2017 00:40:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/deploying-ise-2-3/m-p/3421554#M519955</guid>
      <dc:creator>Arne Bier</dc:creator>
      <dc:date>2017-11-14T00:40:36Z</dc:date>
    </item>
    <item>
      <title>Re: DEPLOYING ISE 2.3</title>
      <link>https://community.cisco.com/t5/network-access-control/deploying-ise-2-3/m-p/3421555#M519958</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Arne,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You experience is way different than mine.  Just going back to the start of 2016 I have done roughly 30 ISE installs all 2.x.  I have deployed 2.1 when it first came out, 2.2 when first came out and 2.3 when it first came out.  Deployment sizes from 2-20 nodes.  Active endpoints from several 1000 to 100,000+.  Every feature accept client provisioning (stay away from that like the plague) including all guest scenarios you can think of.  No major issues on any of my installs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have a different deployment methodology than the Cisco literature that has been honed since ISE 1.0.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now, I am not saying there haven’t been annoying bugs along the way, but none were show stoppers.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Nov 2017 03:56:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/deploying-ise-2-3/m-p/3421555#M519958</guid>
      <dc:creator>paul</dc:creator>
      <dc:date>2017-11-14T03:56:20Z</dc:date>
    </item>
    <item>
      <title>Re: DEPLOYING ISE 2.3</title>
      <link>https://community.cisco.com/t5/network-access-control/deploying-ise-2-3/m-p/3421556#M519962</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have now deployed my first ISE 2.3. It's kind of cool.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks all for your contribution.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 24 Nov 2017 10:32:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/deploying-ise-2-3/m-p/3421556#M519962</guid>
      <dc:creator>kajibola</dc:creator>
      <dc:date>2017-11-24T10:32:35Z</dc:date>
    </item>
  </channel>
</rss>

