<?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: Guest broken after BYOD in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/guest-broken-after-byod/m-p/3442798#M536537</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In ISE 2.2 and perhaps 2.1 Context Visibility &amp;gt; Endpoints&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Other releases&lt;/P&gt;&lt;P&gt;Administration &amp;gt; Identities &amp;gt; Endpoints&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For your use case perhaps they have to handle how to transfer assets as it wouldn’t be registered to the correct person any longer&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 11 Jan 2017 15:06:49 GMT</pubDate>
    <dc:creator>Jason Kunst</dc:creator>
    <dc:date>2017-01-11T15:06:49Z</dc:date>
    <item>
      <title>Guest broken after BYOD</title>
      <link>https://community.cisco.com/t5/network-access-control/guest-broken-after-byod/m-p/3442793#M536532</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;After testing some BYOD options, I was toying around with the guest services deployments.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;I've removed all profiles/certs from the endpoint, removed the client from the BYOD Registered device, however, when the client tries to log in after being sponsor approved, this message is displayed&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;"Endpoint is already registered to another user"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've disabled the "automatically register devices"&amp;nbsp; and that stops the automatic error message, but now clients are not put into the "GuestEndpoints" group.&amp;nbsp; So they are forced to click "enable registration"&amp;nbsp; to get them into that GuestEndpoints group which I use to denote that a client has registered.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Once they click "register device" they see the error ""Endpoint is already registered to another user"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So i'm stuck either way.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ipad, Iphone and Android tested on ISE 2.1 patch 1&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Jan 2017 08:12:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/guest-broken-after-byod/m-p/3442793#M536532</guid>
      <dc:creator>tisnow</dc:creator>
      <dc:date>2017-01-11T08:12:09Z</dc:date>
    </item>
    <item>
      <title>Re: Guest broken after BYOD</title>
      <link>https://community.cisco.com/t5/network-access-control/guest-broken-after-byod/m-p/3442794#M536533</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Its  a guest device so it wouldn't be known when first coming in and certainly wouldn't be going through byod&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Did you delete the endpoint from ise?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Jan 2017 12:55:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/guest-broken-after-byod/m-p/3442794#M536533</guid>
      <dc:creator>Jason Kunst</dc:creator>
      <dc:date>2017-01-11T12:55:25Z</dc:date>
    </item>
    <item>
      <title>Re: Guest broken after BYOD</title>
      <link>https://community.cisco.com/t5/network-access-control/guest-broken-after-byod/m-p/3442795#M536534</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;"After testing some BYOD options, I was toying around with the guest services deployments."&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The client was used for BYOD testing, then we wanted to test some guest options.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I removed it as a registered device group, but when the guest system is set to "automatically register devices" it throws the error about the system.&amp;nbsp;&amp;nbsp; I can indeed add the system MAC manually as a GuestEndpoint and then my guest flow works but my question is if i've hit a bug or why a pre-registered BYOD system, once removed from the Registered Devices is not able to be a guest.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do we expect that we may never see a previously registered (then removed) BYOD device become a guest?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Jan 2017 14:28:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/guest-broken-after-byod/m-p/3442795#M536534</guid>
      <dc:creator>tisnow</dc:creator>
      <dc:date>2017-01-11T14:28:14Z</dc:date>
    </item>
    <item>
      <title>Re: Guest broken after BYOD</title>
      <link>https://community.cisco.com/t5/network-access-control/guest-broken-after-byod/m-p/3442796#M536535</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I understand what you were doing, my only point is that it's still in the endpoint database even though you removed it from the byod group, Did you delete the endpoint completely from ise?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I agree It could happen that a byod device later goes through guest but think the use case is rare&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Jan 2017 14:38:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/guest-broken-after-byod/m-p/3442796#M536535</guid>
      <dc:creator>Jason Kunst</dc:creator>
      <dc:date>2017-01-11T14:38:37Z</dc:date>
    </item>
    <item>
      <title>Re: Guest broken after BYOD</title>
      <link>https://community.cisco.com/t5/network-access-control/guest-broken-after-byod/m-p/3442797#M536536</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Can you advise how to remove it "completely" from ise?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I made the assumption removing it from the RegisteredEndpoints would allow it to be registered. &lt;/P&gt;&lt;P&gt;&lt;BR /&gt;What happens if I have a registered device,&amp;nbsp; that employee leaves and it was provided to someone else to use as a Corporate Device that is registered?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Jan 2017 14:58:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/guest-broken-after-byod/m-p/3442797#M536536</guid>
      <dc:creator>tisnow</dc:creator>
      <dc:date>2017-01-11T14:58:07Z</dc:date>
    </item>
    <item>
      <title>Re: Guest broken after BYOD</title>
      <link>https://community.cisco.com/t5/network-access-control/guest-broken-after-byod/m-p/3442798#M536537</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In ISE 2.2 and perhaps 2.1 Context Visibility &amp;gt; Endpoints&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Other releases&lt;/P&gt;&lt;P&gt;Administration &amp;gt; Identities &amp;gt; Endpoints&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For your use case perhaps they have to handle how to transfer assets as it wouldn’t be registered to the correct person any longer&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Jan 2017 15:06:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/guest-broken-after-byod/m-p/3442798#M536537</guid>
      <dc:creator>Jason Kunst</dc:creator>
      <dc:date>2017-01-11T15:06:49Z</dc:date>
    </item>
    <item>
      <title>Re: Guest broken after BYOD</title>
      <link>https://community.cisco.com/t5/network-access-control/guest-broken-after-byod/m-p/3442799#M536538</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;"Administration &amp;gt; Identities &amp;gt; Endpoints"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This purges the system from the Database whereas removing from the RegisteredDevices does not?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there any other options I need to look at as I'll have time in the morning to test this out.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks Jason.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Jan 2017 15:24:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/guest-broken-after-byod/m-p/3442799#M536538</guid>
      <dc:creator>tisnow</dc:creator>
      <dc:date>2017-01-11T15:24:44Z</dc:date>
    </item>
    <item>
      <title>Re: Guest broken after BYOD</title>
      <link>https://community.cisco.com/t5/network-access-control/guest-broken-after-byod/m-p/3442800#M536539</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Correct, that should be it, make sure you remove the profiles from the endpoint, forget any SSIDs, turn off the wirlesss, clear the wireless session and then delete the endpoint from the database, that would be a clean guest endpoint coming in&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Remove from registered devices just removes it from the group not from ISE database.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Jan 2017 15:48:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/guest-broken-after-byod/m-p/3442800#M536539</guid>
      <dc:creator>Jason Kunst</dc:creator>
      <dc:date>2017-01-11T15:48:13Z</dc:date>
    </item>
    <item>
      <title>Re: Guest broken after BYOD</title>
      <link>https://community.cisco.com/t5/network-access-control/guest-broken-after-byod/m-p/3442801#M536540</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Confirmed the following&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Deleting from the group as RegisteredDevices doesn't fix the problem&lt;/P&gt;&lt;P&gt;Deleting from Context&amp;gt;Endpoint does indeed solve the problem&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks Jason&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 12 Jan 2017 03:23:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/guest-broken-after-byod/m-p/3442801#M536540</guid>
      <dc:creator>tisnow</dc:creator>
      <dc:date>2017-01-12T03:23:29Z</dc:date>
    </item>
    <item>
      <title>Re: Guest broken after BYOD</title>
      <link>https://community.cisco.com/t5/network-access-control/guest-broken-after-byod/m-p/3442802#M536541</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Jason,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; So one device cannot be used on both BYOD and Corp wireless networks?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 Mar 2018 00:18:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/guest-broken-after-byod/m-p/3442802#M536541</guid>
      <dc:creator>TM13</dc:creator>
      <dc:date>2018-03-27T00:18:17Z</dc:date>
    </item>
    <item>
      <title>Re: Guest broken after BYOD</title>
      <link>https://community.cisco.com/t5/network-access-control/guest-broken-after-byod/m-p/3442803#M536542</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Please open a new thread and explain your use case needs&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 Mar 2018 01:57:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/guest-broken-after-byod/m-p/3442803#M536542</guid>
      <dc:creator>Jason Kunst</dc:creator>
      <dc:date>2018-03-27T01:57:48Z</dc:date>
    </item>
  </channel>
</rss>

