<?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 Profiling not working for ad joined wireless devices....sometimes. in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/profiling-not-working-for-ad-joined-wireless-devices-sometimes/m-p/3217141#M555342</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have created a custom profile policy in our ISE 2.2 deployment.&amp;nbsp; I have set it up to profile an AD joined computer.&amp;nbsp; It appears that this custom profile is working for all wired devices.&amp;nbsp; However profiling for wireless AD joined devices seems to be very inconsistent.&amp;nbsp; Most of the time the system will not match the custom profile and instead just match the default Windows 10 Workstation profile.&amp;nbsp; But sometimes it will work correctly.....&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any ideas?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Dan.&lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 18:39:10 GMT</pubDate>
    <dc:creator>dan.letkeman</dc:creator>
    <dc:date>2020-02-21T18:39:10Z</dc:date>
    <item>
      <title>Profiling not working for ad joined wireless devices....sometimes.</title>
      <link>https://community.cisco.com/t5/network-access-control/profiling-not-working-for-ad-joined-wireless-devices-sometimes/m-p/3217141#M555342</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have created a custom profile policy in our ISE 2.2 deployment.&amp;nbsp; I have set it up to profile an AD joined computer.&amp;nbsp; It appears that this custom profile is working for all wired devices.&amp;nbsp; However profiling for wireless AD joined devices seems to be very inconsistent.&amp;nbsp; Most of the time the system will not match the custom profile and instead just match the default Windows 10 Workstation profile.&amp;nbsp; But sometimes it will work correctly.....&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any ideas?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Dan.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 18:39:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/profiling-not-working-for-ad-joined-wireless-devices-sometimes/m-p/3217141#M555342</guid>
      <dc:creator>dan.letkeman</dc:creator>
      <dc:date>2020-02-21T18:39:10Z</dc:date>
    </item>
    <item>
      <title>Re: Profiling not working for ad joined wireless devices....sometimes.</title>
      <link>https://community.cisco.com/t5/network-access-control/profiling-not-working-for-ad-joined-wireless-devices-sometimes/m-p/3222286#M555343</link>
      <description>Hi&lt;BR /&gt;The first thing to do is make sure that radius profiling is enabled on the SSID, for both http and dhcp.&lt;BR /&gt;Also please share the profiling policy configuration which you'd expect the devices to match aswell as screenshots showing the client details from "context visibility &amp;gt;&amp;gt; endpoints" for one "working" wired client and one "non-working" wireless client.&lt;BR /&gt;</description>
      <pubDate>Fri, 24 Nov 2017 23:02:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/profiling-not-working-for-ad-joined-wireless-devices-sometimes/m-p/3222286#M555343</guid>
      <dc:creator>davidgranathkarlsson</dc:creator>
      <dc:date>2017-11-24T23:02:32Z</dc:date>
    </item>
  </channel>
</rss>

