<?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: Way to latch the ISE to a specific domain controller. in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/way-to-latch-the-ise-to-a-specific-domain-controller/m-p/4822299#M581392</link>
    <description>&lt;P&gt;Agree with Greg. Use the AD Sites and Services. However, If there is very specific requirement to connect to specific DC in a domain, then open a TAC case. TAC may help with Advanced Tuning of Active Directory Connection.&lt;/P&gt;</description>
    <pubDate>Wed, 26 Apr 2023 15:16:05 GMT</pubDate>
    <dc:creator>poongarg</dc:creator>
    <dc:date>2023-04-26T15:16:05Z</dc:date>
    <item>
      <title>Way to latch the ISE to a specific domain controller.</title>
      <link>https://community.cisco.com/t5/network-access-control/way-to-latch-the-ise-to-a-specific-domain-controller/m-p/4821343#M581366</link>
      <description>&lt;P&gt;We have ISE 2.6 in our environment and are testing some stuff with AD connection.&lt;/P&gt;&lt;P&gt;Is there a way to connect to a specific AD Domain controller?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;TIA&lt;/P&gt;&lt;P&gt;Shubham&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 25 Apr 2023 13:53:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/way-to-latch-the-ise-to-a-specific-domain-controller/m-p/4821343#M581366</guid>
      <dc:creator>shubham patki</dc:creator>
      <dc:date>2023-04-25T13:53:19Z</dc:date>
    </item>
    <item>
      <title>Re: Way to latch the ISE to a specific domain controller.</title>
      <link>https://community.cisco.com/t5/network-access-control/way-to-latch-the-ise-to-a-specific-domain-controller/m-p/4821392#M581368</link>
      <description>&lt;P&gt;You can leverage the feature of Whitelisted Domains in Active Directory page of ISE.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="NancySaini_0-1682434329675.png" style="width: 735px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/182833i82D535CD73285AD4/image-dimensions/735x313?v=v2" width="735" height="313" role="button" title="NancySaini_0-1682434329675.png" alt="NancySaini_0-1682434329675.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 25 Apr 2023 14:52:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/way-to-latch-the-ise-to-a-specific-domain-controller/m-p/4821392#M581368</guid>
      <dc:creator>Nancy Saini</dc:creator>
      <dc:date>2023-04-25T14:52:25Z</dc:date>
    </item>
    <item>
      <title>Re: Way to latch the ISE to a specific domain controller.</title>
      <link>https://community.cisco.com/t5/network-access-control/way-to-latch-the-ise-to-a-specific-domain-controller/m-p/4821434#M581370</link>
      <description>&lt;P&gt;If I understand your question correctly.&amp;nbsp; AD Sites and Services is what you are looking for.&lt;A href="https://www.cisco.com/c/en/us/products/collateral/security/identity-services-engine/bulletin-c25-2503911.html" target="_blank"&gt;https://www.cisco.com/c/en/us/products/collateral/security/identity-services-engine/bulletin-c25-2503911.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 25 Apr 2023 15:28:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/way-to-latch-the-ise-to-a-specific-domain-controller/m-p/4821434#M581370</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2023-04-25T15:28:59Z</dc:date>
    </item>
    <item>
      <title>Re: Way to latch the ISE to a specific domain controller.</title>
      <link>https://community.cisco.com/t5/network-access-control/way-to-latch-the-ise-to-a-specific-domain-controller/m-p/4821461#M581371</link>
      <description>&lt;P&gt;I think so too. I read somewhere that using AD Sites and services can be helpful. But that's it, no more details on how can we leverage that to force ISE/PSN to connect to a specific Domain Controller.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 25 Apr 2023 16:01:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/way-to-latch-the-ise-to-a-specific-domain-controller/m-p/4821461#M581371</guid>
      <dc:creator>shubham patki</dc:creator>
      <dc:date>2023-04-25T16:01:09Z</dc:date>
    </item>
    <item>
      <title>Re: Way to latch the ISE to a specific domain controller.</title>
      <link>https://community.cisco.com/t5/network-access-control/way-to-latch-the-ise-to-a-specific-domain-controller/m-p/4821622#M581379</link>
      <description>&lt;P&gt;See a similar discussion here:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.cisco.com/t5/network-access-control/ise-ad-sites-and-services/td-p/3335406" target="_blank"&gt;https://community.cisco.com/t5/network-access-control/ise-ad-sites-and-services/td-p/3335406&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;ISE joins the domain as a computer account, so it leverages standard AD functions for determining which Domain Controller(s) it should communicate with and in which order. With properly configured AD Sites and the IP/subnet of the ISE node(s) mapped to the correct Site in AD, the ISE nodes will automatically communicate with the DC associated with that Site.&lt;/P&gt;
&lt;P&gt;You can read more about AD Sites here:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.windows-active-directory.com/active-directory-sites.html" target="_blank"&gt;https://www.windows-active-directory.com/active-directory-sites.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 25 Apr 2023 22:52:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/way-to-latch-the-ise-to-a-specific-domain-controller/m-p/4821622#M581379</guid>
      <dc:creator>Greg Gibbs</dc:creator>
      <dc:date>2023-04-25T22:52:09Z</dc:date>
    </item>
    <item>
      <title>Re: Way to latch the ISE to a specific domain controller.</title>
      <link>https://community.cisco.com/t5/network-access-control/way-to-latch-the-ise-to-a-specific-domain-controller/m-p/4822299#M581392</link>
      <description>&lt;P&gt;Agree with Greg. Use the AD Sites and Services. However, If there is very specific requirement to connect to specific DC in a domain, then open a TAC case. TAC may help with Advanced Tuning of Active Directory Connection.&lt;/P&gt;</description>
      <pubDate>Wed, 26 Apr 2023 15:16:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/way-to-latch-the-ise-to-a-specific-domain-controller/m-p/4822299#M581392</guid>
      <dc:creator>poongarg</dc:creator>
      <dc:date>2023-04-26T15:16:05Z</dc:date>
    </item>
  </channel>
</rss>

