<?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: ISE Profiler and applying only the downloaded OUI Package... in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-profiler-and-applying-only-the-downloaded-oui-package/m-p/5192372#M591729</link>
    <description>&lt;P&gt;So, we can conclude that the mentioned Cisco's document is not correct. Right?&lt;/P&gt;</description>
    <pubDate>Tue, 10 Sep 2024 04:10:17 GMT</pubDate>
    <dc:creator>rezaalikhani</dc:creator>
    <dc:date>2024-09-10T04:10:17Z</dc:date>
    <item>
      <title>ISE Profiler and applying only the downloaded OUI Package...</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-profiler-and-applying-only-the-downloaded-oui-package/m-p/5171107#M591640</link>
      <description>&lt;P&gt;Hi all;&lt;/P&gt;&lt;P&gt;We see in the ISE 2.7 release notes, the following statement:&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;STRONG&gt;If you have customized your profiler conditions and do not want the profiler feed to replace those conditions, you can manually download OUI updates without downloading the policy updates.&lt;/STRONG&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;Now my question is that how is it possible updating profiler feed replace an "&lt;STRONG&gt;administrator-created&lt;/STRONG&gt;" or "&lt;STRONG&gt;administrator-modified&lt;/STRONG&gt;" profiling policy?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Sep 2024 16:38:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-profiler-and-applying-only-the-downloaded-oui-package/m-p/5171107#M591640</guid>
      <dc:creator>rezaalikhani</dc:creator>
      <dc:date>2024-09-04T16:38:42Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Profiler and applying only the downloaded OUI Package...</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-profiler-and-applying-only-the-downloaded-oui-package/m-p/5171614#M591657</link>
      <description>&lt;P&gt;It's not.&amp;nbsp; I read this as if/when you use provided conditions nested with administrator custom profiling policies.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/products/collateral/security/identity-services-engine/bulletin-c25-2943876.html" target="_blank"&gt;https://www.cisco.com/c/en/us/products/collateral/security/identity-services-engine/bulletin-c25-2943876.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 05 Sep 2024 11:00:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-profiler-and-applying-only-the-downloaded-oui-package/m-p/5171614#M591657</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2024-09-05T11:00:31Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Profiler and applying only the downloaded OUI Package...</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-profiler-and-applying-only-the-downloaded-oui-package/m-p/5192295#M591725</link>
      <description>&lt;P&gt;Profiler Feed update will never update your administrator-created profiles.&amp;nbsp; The administrator-modified profiles won't be updated either, because that is the case when a cisco-created profile is modified. This puts an update lock on that profile, which can be bad news. E.g. if you modify the Cisco provided Windows-Workstation, then it will prevent downloading updates for future versions of Windows that rely on that profile. I had a customer who modified a bunch of Cisco profiles and that killed the update process. The solution was to delete all the admin-modified profiles - when you do that, ISE will replace that profile with the original cisco-provided profile.&lt;/P&gt;
&lt;P&gt;Not sure if that helps.&lt;/P&gt;</description>
      <pubDate>Mon, 09 Sep 2024 22:09:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-profiler-and-applying-only-the-downloaded-oui-package/m-p/5192295#M591725</guid>
      <dc:creator>Arne Bier</dc:creator>
      <dc:date>2024-09-09T22:09:01Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Profiler and applying only the downloaded OUI Package...</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-profiler-and-applying-only-the-downloaded-oui-package/m-p/5192372#M591729</link>
      <description>&lt;P&gt;So, we can conclude that the mentioned Cisco's document is not correct. Right?&lt;/P&gt;</description>
      <pubDate>Tue, 10 Sep 2024 04:10:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-profiler-and-applying-only-the-downloaded-oui-package/m-p/5192372#M591729</guid>
      <dc:creator>rezaalikhani</dc:creator>
      <dc:date>2024-09-10T04:10:17Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Profiler and applying only the downloaded OUI Package...</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-profiler-and-applying-only-the-downloaded-oui-package/m-p/5192441#M591740</link>
      <description>&lt;P&gt;What the documentation is saying, is that you can (or could ... since I have failed and now given up trying) download two separate files from ise.cisco.com/partner (or whatever the URL is/was) - one contains only the MAC OUI prefix mappings. And the other file contains the MAC OUI prefix mappings AND the Profiler Policy updates.&lt;/P&gt;
&lt;P&gt;Document doesn't say what should/might happen to the administrator-* profiles.&lt;/P&gt;</description>
      <pubDate>Tue, 10 Sep 2024 07:05:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-profiler-and-applying-only-the-downloaded-oui-package/m-p/5192441#M591740</guid>
      <dc:creator>Arne Bier</dc:creator>
      <dc:date>2024-09-10T07:05:40Z</dc:date>
    </item>
  </channel>
</rss>

