<?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: Adding domain controler to AD domain and ISE behaviour in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/adding-domain-controler-to-ad-domain-and-ise-behaviour/m-p/4800044#M580694</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/309358"&gt;@REJR77&lt;/a&gt;&amp;nbsp;, as you are going to remove the 2DC from where ISE has created a join, you will have to remove them from the ISE itself as the ISE will continue attempting to query those although they are not longer there ( ISE will not be aware of the changes done within the 2 DC) ,&amp;nbsp; once you remove them you will have to add the new DC that you are going to implement as replacement , to review more about the ISE-AD operations you can refer to&amp;nbsp;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/ise/2-2/ise_active_directory_integration/b_ISE_AD_integration_2x.html" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/security/ise/2-2/ise_active_directory_integration/b_ISE_AD_integration_2x.html&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Let me know if that helped you .&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 23 Mar 2023 14:38:27 GMT</pubDate>
    <dc:creator>Rodrigo Diaz</dc:creator>
    <dc:date>2023-03-23T14:38:27Z</dc:date>
    <item>
      <title>Adding domain controler to AD domain and ISE behaviour</title>
      <link>https://community.cisco.com/t5/network-access-control/adding-domain-controler-to-ad-domain-and-ise-behaviour/m-p/4799910#M580687</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;We already have an ISE deployment connected to an AD domain with 2 DC&lt;/P&gt;
&lt;P&gt;We are going to add new Domain Controller to the Domain (and remove the old ones later) and would like to know if we need to change things on ISE or if it is transparent since ISE are already joined&lt;/P&gt;
&lt;P&gt;REgards&lt;/P&gt;</description>
      <pubDate>Thu, 23 Mar 2023 11:09:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/adding-domain-controler-to-ad-domain-and-ise-behaviour/m-p/4799910#M580687</guid>
      <dc:creator>REJR77</dc:creator>
      <dc:date>2023-03-23T11:09:26Z</dc:date>
    </item>
    <item>
      <title>Re: Adding domain controler to AD domain and ISE behaviour</title>
      <link>https://community.cisco.com/t5/network-access-control/adding-domain-controler-to-ad-domain-and-ise-behaviour/m-p/4800044#M580694</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/309358"&gt;@REJR77&lt;/a&gt;&amp;nbsp;, as you are going to remove the 2DC from where ISE has created a join, you will have to remove them from the ISE itself as the ISE will continue attempting to query those although they are not longer there ( ISE will not be aware of the changes done within the 2 DC) ,&amp;nbsp; once you remove them you will have to add the new DC that you are going to implement as replacement , to review more about the ISE-AD operations you can refer to&amp;nbsp;&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/ise/2-2/ise_active_directory_integration/b_ISE_AD_integration_2x.html" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/security/ise/2-2/ise_active_directory_integration/b_ISE_AD_integration_2x.html&lt;/A&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Let me know if that helped you .&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 23 Mar 2023 14:38:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/adding-domain-controler-to-ad-domain-and-ise-behaviour/m-p/4800044#M580694</guid>
      <dc:creator>Rodrigo Diaz</dc:creator>
      <dc:date>2023-03-23T14:38:27Z</dc:date>
    </item>
    <item>
      <title>Re: Adding domain controler to AD domain and ISE behaviour</title>
      <link>https://community.cisco.com/t5/network-access-control/adding-domain-controler-to-ad-domain-and-ise-behaviour/m-p/4800099#M580701</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/632778"&gt;@Rodrigo Diaz&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;From what I understand ISE detects domain controllers with DNS requests. Therefore we can not specify on which DC it will connect to join. Am I wrong?&lt;/P&gt;
&lt;P&gt;The use case I am referring to is not clearly detailed in the documentation.HHow can we ask ISE to connect to the new servers since everything looks "automatic" ?&lt;/P&gt;
&lt;P&gt;Thanks for clarification&lt;/P&gt;</description>
      <pubDate>Thu, 23 Mar 2023 15:23:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/adding-domain-controler-to-ad-domain-and-ise-behaviour/m-p/4800099#M580701</guid>
      <dc:creator>REJR77</dc:creator>
      <dc:date>2023-03-23T15:23:38Z</dc:date>
    </item>
    <item>
      <title>Re: Adding domain controler to AD domain and ISE behaviour</title>
      <link>https://community.cisco.com/t5/network-access-control/adding-domain-controler-to-ad-domain-and-ise-behaviour/m-p/4800256#M580716</link>
      <description>&lt;P&gt;Add the new DC then reboot each of the two older DCs one at a time until ISE picks up the new one.&amp;nbsp; I'm pretty sure it will find it but I would test before you decom the old ones.&amp;nbsp; You can see what DC ISE is attached to Administration --&amp;gt; External Identity Sources --&amp;gt; Active Directory --&amp;gt; and then click your deployment.&amp;nbsp; There will be a "Domain Controller" column that lists the DC each node is attached to.&amp;nbsp; ISE is built to join the domain like any computer or server, not to a specific domain controller so I would be surprised if you have to do anything other than making sure you are attached to new one before killing the old ones.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 23 Mar 2023 17:48:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/adding-domain-controler-to-ad-domain-and-ise-behaviour/m-p/4800256#M580716</guid>
      <dc:creator>Christopher Bell</dc:creator>
      <dc:date>2023-03-23T17:48:20Z</dc:date>
    </item>
    <item>
      <title>Re: Adding domain controler to AD domain and ISE behaviour</title>
      <link>https://community.cisco.com/t5/network-access-control/adding-domain-controler-to-ad-domain-and-ise-behaviour/m-p/4800363#M580725</link>
      <description>&lt;P&gt;Like other computers and member servers in Active Directory, ISE learns which Domain Controller it should communicate with from &lt;A href="https://www.windows-active-directory.com/active-directory-sites.html" target="_blank" rel="noopener"&gt;AD Sites and Services&lt;/A&gt;. You would need to ensure that the subnet used by ISE is associated with the appropriate Site and DC and ISE will automatically learn this information.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 23 Mar 2023 21:50:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/adding-domain-controler-to-ad-domain-and-ise-behaviour/m-p/4800363#M580725</guid>
      <dc:creator>Greg Gibbs</dc:creator>
      <dc:date>2023-03-23T21:50:25Z</dc:date>
    </item>
  </channel>
</rss>

