<?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: Upgrading 2.1 patch 1 to 2.2 in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/upgrading-2-1-patch-1-to-2-2/m-p/3484914#M519363</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for reaching out.&lt;/P&gt;&lt;P&gt;It will be good to know what deployment version you are in. &lt;/P&gt;&lt;P&gt;Features that you are using etc.&lt;/P&gt;&lt;P&gt;Also good to know if you are upgrading for a specific reason etc( for eg: looking for new features in ISE 2.2 etc)?&lt;/P&gt;&lt;P&gt;Do you have a timeframe to migrate ? I can make suggestions based on this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;BR /&gt;Krishnan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 05 Dec 2017 02:00:13 GMT</pubDate>
    <dc:creator>kthiruve</dc:creator>
    <dc:date>2017-12-05T02:00:13Z</dc:date>
    <item>
      <title>Upgrading 2.1 patch 1 to 2.2</title>
      <link>https://community.cisco.com/t5/network-access-control/upgrading-2-1-patch-1-to-2-2/m-p/3484912#M519357</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I was wondering if this is a good plan to upgrade 2.1 patch 1 to 2.2&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Patch ISE 2.1 to patch 6&lt;/P&gt;&lt;P&gt;back up items(ISE config, data, certs &amp;amp; private keys)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;upgrade to 2.2&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;apply struts 2 fix&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Install ISE 2.2 patch 4&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just wondering about the struts patch does that need to be done? Or does the 2.2 patch 4 fix the struts 2? After reading the docs it looks like, I need to do the upgrade in the order that I have listed. Just wanted to confirm that I'm reading the docs correctly for upgrading.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance,&lt;/P&gt;&lt;P&gt;john&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Dec 2017 17:33:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/upgrading-2-1-patch-1-to-2-2/m-p/3484912#M519357</guid>
      <dc:creator>hammeljch</dc:creator>
      <dc:date>2017-12-04T17:33:04Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading 2.1 patch 1 to 2.2</title>
      <link>https://community.cisco.com/t5/network-access-control/upgrading-2-1-patch-1-to-2-2/m-p/3484913#M519360</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I would not bother with 2.2 - it's buggy.&amp;nbsp; Although it depends what features you're using.&lt;/P&gt;&lt;P&gt;ISE 2.3 introduced the URT (Upgrade Readiness Tool) that you can run to check the integrity of your data.&amp;nbsp; It's quite handy.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have yet to see an upgrade go through smoothly on the entire deployment.&amp;nbsp; In most cases the Sec PAN upgrades, but then the remaining personas die from various causes.&amp;nbsp; Your mileage may vary ..&lt;/P&gt;&lt;P&gt;I would not upgrade - I would restore config onto a clean build.&amp;nbsp; Makes a small mess with licenses on VM.&amp;nbsp; But that's one advantage to move to Smart Licensing &lt;IMG src="https://community.cisco.com/legacyfs/online/emoticons/happy.png" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Dec 2017 22:02:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/upgrading-2-1-patch-1-to-2-2/m-p/3484913#M519360</guid>
      <dc:creator>Arne Bier</dc:creator>
      <dc:date>2017-12-04T22:02:22Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading 2.1 patch 1 to 2.2</title>
      <link>https://community.cisco.com/t5/network-access-control/upgrading-2-1-patch-1-to-2-2/m-p/3484914#M519363</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for reaching out.&lt;/P&gt;&lt;P&gt;It will be good to know what deployment version you are in. &lt;/P&gt;&lt;P&gt;Features that you are using etc.&lt;/P&gt;&lt;P&gt;Also good to know if you are upgrading for a specific reason etc( for eg: looking for new features in ISE 2.2 etc)?&lt;/P&gt;&lt;P&gt;Do you have a timeframe to migrate ? I can make suggestions based on this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;BR /&gt;Krishnan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 05 Dec 2017 02:00:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/upgrading-2-1-patch-1-to-2-2/m-p/3484914#M519363</guid>
      <dc:creator>kthiruve</dc:creator>
      <dc:date>2017-12-05T02:00:13Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading 2.1 patch 1 to 2.2</title>
      <link>https://community.cisco.com/t5/network-access-control/upgrading-2-1-patch-1-to-2-2/m-p/3484915#M519365</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Well, I'm on 2.1.0.474 patch 1 so I was wondering if I have to patch to latest patch for 2.1 which is patch 6.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Couple of items that we will be implementing which is not currently configured is:&lt;/P&gt;&lt;P&gt;guestaccess&lt;/P&gt;&lt;P&gt;trustsec&lt;/P&gt;&lt;P&gt;client provisioning&lt;/P&gt;&lt;P&gt;MDM&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;From those current functions which is better 2.2 or 2.3?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;John&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 05 Dec 2017 12:13:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/upgrading-2-1-patch-1-to-2-2/m-p/3484915#M519365</guid>
      <dc:creator>hammeljch</dc:creator>
      <dc:date>2017-12-05T12:13:48Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading 2.1 patch 1 to 2.2</title>
      <link>https://community.cisco.com/t5/network-access-control/upgrading-2-1-patch-1-to-2-2/m-p/3484916#M519368</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes you will need to apply latest patch before upgrading.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There are also subtle differences between 2.2 and 2.3 with respect to posture, please reference the release notes for each&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2.3 has Facebook for guest registration&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you’re going to make the move would recommend going to 2.3 so that you don’t have to update later&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Many partners in the community have customers running 2.3&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 05 Dec 2017 12:38:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/upgrading-2-1-patch-1-to-2-2/m-p/3484916#M519368</guid>
      <dc:creator>Jason Kunst</dc:creator>
      <dc:date>2017-12-05T12:38:30Z</dc:date>
    </item>
  </channel>
</rss>

