<?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: Changing the hostname on ISE in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/changing-the-hostname-on-ise/m-p/5215660#M592699</link>
    <description>&lt;P&gt;TAC is right! Changing ISE hostname requires the following steps:&lt;/P&gt;
&lt;P&gt;1. Disjoin the ISE nodes from the domain.(If ISE join AD)&lt;/P&gt;
&lt;P&gt;2. Ensure that their computer name is removed from AD.(If ISE join AD)&lt;/P&gt;
&lt;P&gt;3. Update DNS records&lt;/P&gt;
&lt;P&gt;4. Ensure that DNS records have replicated&lt;/P&gt;
&lt;P&gt;5. Change names on ISE(CLI)&lt;/P&gt;
&lt;P&gt;6. Join nodes to the domain&lt;/P&gt;
&lt;P&gt;After&amp;nbsp;Change hostnames on ISE by CLI, you may see the notification as blow:&lt;/P&gt;
&lt;P&gt;Updating the hostname will cause any certificate using the old&lt;BR /&gt;% hostname to become invalid. Therefore, a new self-signed&lt;BR /&gt;% certificate using the new hostname will be generated now for&lt;BR /&gt;% use with HTTPs/EAP. If CA-signed certs were used on this node,&lt;BR /&gt;% please import them with the correct hostname. If Internal-CA&lt;BR /&gt;% signed certs are being used, please regenerate ISE Root CA certificate.&lt;BR /&gt;% In addition, if this ise node will be joining a new Active Directory&lt;BR /&gt;% domain, please leave your current Active Directory domain before&lt;BR /&gt;% proceeding. If this ise node is already joined to&lt;BR /&gt;% an Active Directory domain, then it is strongly advised&lt;BR /&gt;% to rejoin all currently joined join-points in order to&lt;BR /&gt;% avoid possible mismatch between current and previous&lt;BR /&gt;% hostname and joined machine account name.&lt;BR /&gt;% Changing the hostname will cause ise services to restart&lt;BR /&gt;Proceed? [yes,no] &lt;BR /&gt;If you type"yes",&lt;/P&gt;
&lt;P&gt;new hostname will be generated for&amp;nbsp;use with HTTPs/EAP will generate a new&amp;nbsp;certificate, then restart ISE.&lt;/P&gt;
&lt;P&gt;So, need to&amp;nbsp;regenerate ISE Root CA certificate、 disjoin the ISE nodes from the domain.&lt;/P&gt;
&lt;P&gt;You better try it on your Lab before do it on production.&lt;/P&gt;</description>
    <pubDate>Sun, 27 Oct 2024 03:59:41 GMT</pubDate>
    <dc:creator>jonlin2</dc:creator>
    <dc:date>2024-10-27T03:59:41Z</dc:date>
    <item>
      <title>Changing the hostname on ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/changing-the-hostname-on-ise/m-p/3479489#M538122</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Has anyone successfully changed the hostname on an ISE 2.1.0.474 Standalone installation?&amp;nbsp; We looked at doing this awhile back and was basically told it was extremely difficult to do.&amp;nbsp; We are in need of changing it due to a certificate issue.&amp;nbsp; Any help or advice would be appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;Beth&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Jul 2016 22:41:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/changing-the-hostname-on-ise/m-p/3479489#M538122</guid>
      <dc:creator>__Beth__</dc:creator>
      <dc:date>2016-07-28T22:41:39Z</dc:date>
    </item>
    <item>
      <title>Re: Changing the hostname on ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/changing-the-hostname-on-ise/m-p/3479490#M538125</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Did you try and have a problem?  Make sure you backup first.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;http://www.cisco.com/c/en/us/td/docs/security/ise/2-1/cli_ref_guide/b_ise_CLIReferenceGuide_21/b_ise_CLIReferenceGuide_21_chapter_011.html#ID-1364-00000428&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Warning: I either dictated this to my device, or typed it with my thumbs. Erroneous words are a feature, not a typo.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Jul 2016 23:19:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/changing-the-hostname-on-ise/m-p/3479490#M538125</guid>
      <dc:creator>gbekmezi-DD</dc:creator>
      <dc:date>2016-07-28T23:19:53Z</dc:date>
    </item>
    <item>
      <title>Re: Changing the hostname on ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/changing-the-hostname-on-ise/m-p/3479491#M538126</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If you are updating "hostname" only, what George provided is a good option. I've done it a couple of times.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you are updating more than "hostname", then try "reset-config", which is added in ISE 2.0 to reset network and time settings.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Either way, I would also suggest to reload the ISE node once the changes are done.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Jul 2016 04:43:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/changing-the-hostname-on-ise/m-p/3479491#M538126</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2016-07-29T04:43:51Z</dc:date>
    </item>
    <item>
      <title>Re: Changing the hostname on ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/changing-the-hostname-on-ise/m-p/3479492#M538128</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you both.&amp;nbsp; The reason I ask is when we looked at doing this in the past, I contacted TAC and their response was &lt;SPAN style="color: #44546a; font-family: 'Georgia',serif; font-size: 11pt; mso-fareast-font-family: Calibri; mso-fareast-theme-font: minor-latin; mso-bidi-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA;"&gt;“Unfortunately, changing the hostname on ISE is a Herculean task.”&amp;nbsp; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I will definitely do a backup before attempting any changes.&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Jul 2016 13:56:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/changing-the-hostname-on-ise/m-p/3479492#M538128</guid>
      <dc:creator>__Beth__</dc:creator>
      <dc:date>2016-07-29T13:56:24Z</dc:date>
    </item>
    <item>
      <title>Re: Changing the hostname on ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/changing-the-hostname-on-ise/m-p/3479493#M538130</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am not sure why TAC commented so. I've not had much problem with hostname changes for a standalone ISE. Please note that we would need to re-generate the internal CA certificate chain after the hostname change for the ISE internal CA to continue issuing certificates.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you run into any problem, please let us know so we can track it down.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Jul 2016 16:35:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/changing-the-hostname-on-ise/m-p/3479493#M538130</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2016-07-29T16:35:45Z</dc:date>
    </item>
    <item>
      <title>Re: Changing the hostname on ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/changing-the-hostname-on-ise/m-p/3707816#M538133</link>
      <description>&lt;P&gt;Can this be achieved by entering hostname NEWHOSTNAME at global config mode on the ISE, I believe it works on ISE1.2.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards.&lt;/P&gt;</description>
      <pubDate>Sun, 16 Sep 2018 21:15:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/changing-the-hostname-on-ise/m-p/3707816#M538133</guid>
      <dc:creator>adrianbcisco</dc:creator>
      <dc:date>2018-09-16T21:15:33Z</dc:date>
    </item>
    <item>
      <title>Re: Changing the hostname on ISE</title>
      <link>https://community.cisco.com/t5/network-access-control/changing-the-hostname-on-ise/m-p/5215660#M592699</link>
      <description>&lt;P&gt;TAC is right! Changing ISE hostname requires the following steps:&lt;/P&gt;
&lt;P&gt;1. Disjoin the ISE nodes from the domain.(If ISE join AD)&lt;/P&gt;
&lt;P&gt;2. Ensure that their computer name is removed from AD.(If ISE join AD)&lt;/P&gt;
&lt;P&gt;3. Update DNS records&lt;/P&gt;
&lt;P&gt;4. Ensure that DNS records have replicated&lt;/P&gt;
&lt;P&gt;5. Change names on ISE(CLI)&lt;/P&gt;
&lt;P&gt;6. Join nodes to the domain&lt;/P&gt;
&lt;P&gt;After&amp;nbsp;Change hostnames on ISE by CLI, you may see the notification as blow:&lt;/P&gt;
&lt;P&gt;Updating the hostname will cause any certificate using the old&lt;BR /&gt;% hostname to become invalid. Therefore, a new self-signed&lt;BR /&gt;% certificate using the new hostname will be generated now for&lt;BR /&gt;% use with HTTPs/EAP. If CA-signed certs were used on this node,&lt;BR /&gt;% please import them with the correct hostname. If Internal-CA&lt;BR /&gt;% signed certs are being used, please regenerate ISE Root CA certificate.&lt;BR /&gt;% In addition, if this ise node will be joining a new Active Directory&lt;BR /&gt;% domain, please leave your current Active Directory domain before&lt;BR /&gt;% proceeding. If this ise node is already joined to&lt;BR /&gt;% an Active Directory domain, then it is strongly advised&lt;BR /&gt;% to rejoin all currently joined join-points in order to&lt;BR /&gt;% avoid possible mismatch between current and previous&lt;BR /&gt;% hostname and joined machine account name.&lt;BR /&gt;% Changing the hostname will cause ise services to restart&lt;BR /&gt;Proceed? [yes,no] &lt;BR /&gt;If you type"yes",&lt;/P&gt;
&lt;P&gt;new hostname will be generated for&amp;nbsp;use with HTTPs/EAP will generate a new&amp;nbsp;certificate, then restart ISE.&lt;/P&gt;
&lt;P&gt;So, need to&amp;nbsp;regenerate ISE Root CA certificate、 disjoin the ISE nodes from the domain.&lt;/P&gt;
&lt;P&gt;You better try it on your Lab before do it on production.&lt;/P&gt;</description>
      <pubDate>Sun, 27 Oct 2024 03:59:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/changing-the-hostname-on-ise/m-p/5215660#M592699</guid>
      <dc:creator>jonlin2</dc:creator>
      <dc:date>2024-10-27T03:59:41Z</dc:date>
    </item>
  </channel>
</rss>

