<?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 ISE - Upgrade from 1.2.0.899 Patch 17 to 1.4 in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-upgrade-from-1-2-0-899-patch-17-to-1-4/m-p/2791315#M56336</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I am tasked with upgrading ISE to 1.4.&amp;nbsp; Part of the instruction state the following:&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;"If you are upgrading a Cisco ISE node on a virtual machine (VM) from Release 1.2 or 1.2.1, after you upgrade, ensure that you power down the VM and change the Guest Operating System to Red Hat Enterprise Linux 6 (64-bit), and power the VM on after the change.&lt;/EM&gt; "&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Is this something that can be done when I shut the machine down for the snapshot?&amp;nbsp; I have to bring another person in for the VM side of things and would like to get everything done sooner rather than later.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;After this, I will then be looking at going to 2.0.&amp;nbsp; If anyone has any tips, tricks or other advice they would like to offer, I would love to hear them. &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks you!&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 06:25:27 GMT</pubDate>
    <dc:creator>__Beth__</dc:creator>
    <dc:date>2019-03-11T06:25:27Z</dc:date>
    <item>
      <title>ISE - Upgrade from 1.2.0.899 Patch 17 to 1.4</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-upgrade-from-1-2-0-899-patch-17-to-1-4/m-p/2791315#M56336</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I am tasked with upgrading ISE to 1.4.&amp;nbsp; Part of the instruction state the following:&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;"If you are upgrading a Cisco ISE node on a virtual machine (VM) from Release 1.2 or 1.2.1, after you upgrade, ensure that you power down the VM and change the Guest Operating System to Red Hat Enterprise Linux 6 (64-bit), and power the VM on after the change.&lt;/EM&gt; "&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Is this something that can be done when I shut the machine down for the snapshot?&amp;nbsp; I have to bring another person in for the VM side of things and would like to get everything done sooner rather than later.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;After this, I will then be looking at going to 2.0.&amp;nbsp; If anyone has any tips, tricks or other advice they would like to offer, I would love to hear them. &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks you!&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 06:25:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-upgrade-from-1-2-0-899-patch-17-to-1-4/m-p/2791315#M56336</guid>
      <dc:creator>__Beth__</dc:creator>
      <dc:date>2019-03-11T06:25:27Z</dc:date>
    </item>
    <item>
      <title>Beth,</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-upgrade-from-1-2-0-899-patch-17-to-1-4/m-p/2791316#M56337</link>
      <description>&lt;P&gt;Beth,&lt;/P&gt;
&lt;P&gt;This comes under post-upgrade tasks so need to be performed once upgrade is finished. If you have plans to take a snapshot after the upgrade then yes you can do it.&lt;/P&gt;
&lt;P&gt;~ Jatin&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 25 Jan 2016 23:11:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-upgrade-from-1-2-0-899-patch-17-to-1-4/m-p/2791316#M56337</guid>
      <dc:creator>Jatin Katyal</dc:creator>
      <dc:date>2016-01-25T23:11:43Z</dc:date>
    </item>
    <item>
      <title>Thank you for your help.</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-upgrade-from-1-2-0-899-patch-17-to-1-4/m-p/2791317#M56338</link>
      <description>&lt;P&gt;Thank you for your help.&lt;/P&gt;</description>
      <pubDate>Tue, 26 Jan 2016 20:05:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-upgrade-from-1-2-0-899-patch-17-to-1-4/m-p/2791317#M56338</guid>
      <dc:creator>__Beth__</dc:creator>
      <dc:date>2016-01-26T20:05:33Z</dc:date>
    </item>
    <item>
      <title>Your welcome Beth !!</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-upgrade-from-1-2-0-899-patch-17-to-1-4/m-p/2791318#M56339</link>
      <description>&lt;P&gt;Your welcome Beth !!&lt;/P&gt;</description>
      <pubDate>Tue, 26 Jan 2016 20:13:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-upgrade-from-1-2-0-899-patch-17-to-1-4/m-p/2791318#M56339</guid>
      <dc:creator>Jatin Katyal</dc:creator>
      <dc:date>2016-01-26T20:13:16Z</dc:date>
    </item>
  </channel>
</rss>

