<?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: BYOD &amp;amp; Android Devices in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/byod-amp-android-devices/m-p/3868166#M472471</link>
    <description>Have they tried downloading the agent before they connect to the network? &lt;BR /&gt;Is the issue opening up the internet to get the agent? Have they tried a split flow? Allowing internet access for employees? Disabling the byod on the guest portal and instead calling out a separate&lt;BR /&gt;have they tried on-boarding with cellular turned off? Sometimes redirect will fail to enroll.cisco.com as it goes out the cell route.&lt;BR /&gt;Does Single SSID work? Allow internet and redirect on enroll.cisco.com and internal only?&lt;BR /&gt;Do they have a TAC case?</description>
    <pubDate>Wed, 05 Jun 2019 15:00:40 GMT</pubDate>
    <dc:creator>Jason Kunst</dc:creator>
    <dc:date>2019-06-05T15:00:40Z</dc:date>
    <item>
      <title>BYOD &amp; Android Devices</title>
      <link>https://community.cisco.com/t5/network-access-control/byod-amp-android-devices/m-p/3868095#M472470</link>
      <description>&lt;P&gt;Looking for opinion. Have an ISE 2.3P5 customer that recently tried to turn up a dual SSID BYOD configuration for their Android users.&amp;nbsp; They had a difficult time with the implementation and ultimately pulled it out of service.&amp;nbsp; They stated that different Android devices/OS version had different behaviors when some would fail and some others pass. &amp;nbsp; Windows &amp;amp; IOS worked just fine.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Those of you that have deployed an Android BYOD network. Did you have difficulty deploying Android devices or did all go relatively smooth?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Sam&lt;/P&gt;</description>
      <pubDate>Wed, 05 Jun 2019 13:33:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/byod-amp-android-devices/m-p/3868095#M472470</guid>
      <dc:creator>scamarda</dc:creator>
      <dc:date>2019-06-05T13:33:47Z</dc:date>
    </item>
    <item>
      <title>Re: BYOD &amp; Android Devices</title>
      <link>https://community.cisco.com/t5/network-access-control/byod-amp-android-devices/m-p/3868166#M472471</link>
      <description>Have they tried downloading the agent before they connect to the network? &lt;BR /&gt;Is the issue opening up the internet to get the agent? Have they tried a split flow? Allowing internet access for employees? Disabling the byod on the guest portal and instead calling out a separate&lt;BR /&gt;have they tried on-boarding with cellular turned off? Sometimes redirect will fail to enroll.cisco.com as it goes out the cell route.&lt;BR /&gt;Does Single SSID work? Allow internet and redirect on enroll.cisco.com and internal only?&lt;BR /&gt;Do they have a TAC case?</description>
      <pubDate>Wed, 05 Jun 2019 15:00:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/byod-amp-android-devices/m-p/3868166#M472471</guid>
      <dc:creator>Jason Kunst</dc:creator>
      <dc:date>2019-06-05T15:00:40Z</dc:date>
    </item>
  </channel>
</rss>

