<?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: Client Provisioning behavior with both wired and wireless profiles in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/client-provisioning-behavior-with-both-wired-and-wireless/m-p/3575843#M537836</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If the client endpoint is running Windows OS, I believe it's expected behavior that NSA only configures the connected wired interface.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 27 Aug 2016 17:21:38 GMT</pubDate>
    <dc:creator>hslai</dc:creator>
    <dc:date>2016-08-27T17:21:38Z</dc:date>
    <item>
      <title>Client Provisioning behavior with both wired and wireless profiles</title>
      <link>https://community.cisco.com/t5/network-access-control/client-provisioning-behavior-with-both-wired-and-wireless/m-p/3575840#M537823</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Experts,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When using a wired BYOD policy rule referencing a Native Supplicant Profile that has both wired and wireless profiles configured why the wireless profile doesn't get configured on the endpoint as well. Is this normal behavior ? Should I be separating wired and wireless profiles ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Ed&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 23 Aug 2016 12:10:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/client-provisioning-behavior-with-both-wired-and-wireless/m-p/3575840#M537823</guid>
      <dc:creator>erajca</dc:creator>
      <dc:date>2016-08-23T12:10:20Z</dc:date>
    </item>
    <item>
      <title>Re: Client Provisioning behavior with both wired and wireless profiles</title>
      <link>https://community.cisco.com/t5/network-access-control/client-provisioning-behavior-with-both-wired-and-wireless/m-p/3575841#M537826</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Currently on-boarding requires the Network adapters connect to network separately. If both NICs are connected to the network together, then on-boarding happens at the same time. Did you check if the supplicant is provisioned when connected to wireless network?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 23 Aug 2016 23:53:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/client-provisioning-behavior-with-both-wired-and-wireless/m-p/3575841#M537826</guid>
      <dc:creator>hariholla</dc:creator>
      <dc:date>2016-08-23T23:53:12Z</dc:date>
    </item>
    <item>
      <title>Re: Client Provisioning behavior with both wired and wireless profiles</title>
      <link>https://community.cisco.com/t5/network-access-control/client-provisioning-behavior-with-both-wired-and-wireless/m-p/3575842#M537832</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We have only tested separately with wired and wireless NICs successfully by disabling one while testing with the other however when enabling both NICs and onboarding with wired, the wireless SSID profile doesn't get pushed out to the client.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Aug 2016 12:29:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/client-provisioning-behavior-with-both-wired-and-wireless/m-p/3575842#M537832</guid>
      <dc:creator>erajca</dc:creator>
      <dc:date>2016-08-24T12:29:41Z</dc:date>
    </item>
    <item>
      <title>Re: Client Provisioning behavior with both wired and wireless profiles</title>
      <link>https://community.cisco.com/t5/network-access-control/client-provisioning-behavior-with-both-wired-and-wireless/m-p/3575843#M537836</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If the client endpoint is running Windows OS, I believe it's expected behavior that NSA only configures the connected wired interface.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 27 Aug 2016 17:21:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/client-provisioning-behavior-with-both-wired-and-wireless/m-p/3575843#M537836</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2016-08-27T17:21:38Z</dc:date>
    </item>
  </channel>
</rss>

