<?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: Best practice for staff BYOD devices in Aerohive Migrated Content</title>
    <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/best-practice-for-staff-byod-devices/m-p/91838#M13162</link>
    <description>&lt;P&gt;Hi Dennis, what is not working on the op-prem? Our visititor registration solution is also working with the on-prem version&lt;/P&gt;</description>
    <pubDate>Mon, 03 Jun 2019 14:09:00 GMT</pubDate>
    <dc:creator>JonasD_Complit</dc:creator>
    <dc:date>2019-06-03T14:09:00Z</dc:date>
    <item>
      <title>Best practice for staff BYOD devices</title>
      <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/best-practice-for-staff-byod-devices/m-p/91831#M13155</link>
      <description>&lt;P&gt;We currently have a setup where guests access the WLAN using 802.11x Radius authentication. We are having multiple issues with users AD accounts getting locked out when their passwords need updating and a BYOD device that they have forgotten about attempts to connect with their old credentials. Im looking for a way of preventing this from happening. Maybe a captive portal staff members connect to initially which then sends them a password to their work email address to connect them to the network. Any ideas if this is possible? or a better idea?&lt;/P&gt;</description>
      <pubDate>Wed, 22 May 2019 22:00:54 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/aerohive-migrated-content/best-practice-for-staff-byod-devices/m-p/91831#M13155</guid>
      <dc:creator>robert_davies</dc:creator>
      <dc:date>2019-05-22T22:00:54Z</dc:date>
    </item>
    <item>
      <title>Re: Best practice for staff BYOD devices</title>
      <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/best-practice-for-staff-byod-devices/m-p/91832#M13156</link>
      <description>&lt;P&gt;We generally don't recommend Radius for BYOD, I might recommend a PPSK option instead. You can lock the PPSK credentials to certain MAC addresses, or a certain number of devices allowed to use the same PPSK credentials if you'd like. &lt;/P&gt;</description>
      <pubDate>Thu, 23 May 2019 20:09:57 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/aerohive-migrated-content/best-practice-for-staff-byod-devices/m-p/91832#M13156</guid>
      <dc:creator>samantha_lynn</dc:creator>
      <dc:date>2019-05-23T20:09:57Z</dc:date>
    </item>
    <item>
      <title>Re: Best practice for staff BYOD devices</title>
      <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/best-practice-for-staff-byod-devices/m-p/91833#M13157</link>
      <description>Hi Sam&lt;BR /&gt;
&lt;BR /&gt;
Thanks for the response. What we were hopefully looking to do was allow staff to connect to a captive portal and add their work email address. They can then get the ppsk from their work email address and use that to connect to the office wifi. Does this sound plausible?&lt;BR /&gt;
&lt;BR /&gt;
Regards&lt;BR /&gt;
&lt;BR /&gt;
Robert Davies | Infrastructure Engineer&lt;BR /&gt;
for and on behalf of Charles Russell Speechlys LLP&lt;BR /&gt;
&lt;BR /&gt;
T: +44 (0)20 7438 2266&lt;BR /&gt;
F: +44 (0)20 7203 0200&lt;BR /&gt;
charlesrussellspeechlys.com&lt;WWW.CHARLESRUSSELLSPEECHLYS.COM&gt;&lt;/WWW.CHARLESRUSSELLSPEECHLYS.COM&gt;</description>
      <pubDate>Thu, 23 May 2019 20:20:18 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/aerohive-migrated-content/best-practice-for-staff-byod-devices/m-p/91833#M13157</guid>
      <dc:creator>robert_davies</dc:creator>
      <dc:date>2019-05-23T20:20:18Z</dc:date>
    </item>
    <item>
      <title>Re: Best practice for staff BYOD devices</title>
      <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/best-practice-for-staff-byod-devices/m-p/91834#M13158</link>
      <description>&lt;P&gt;You could set up a self registration SSID, and instruct them to use their work email addresses, and then they'd get the password sent to their inbox. However, we can't limit the self registration CWP to a particular domain, so it would be possible for non-employees to also register via the self registration CWP. &lt;/P&gt;</description>
      <pubDate>Thu, 23 May 2019 20:25:41 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/aerohive-migrated-content/best-practice-for-staff-byod-devices/m-p/91834#M13158</guid>
      <dc:creator>samantha_lynn</dc:creator>
      <dc:date>2019-05-23T20:25:41Z</dc:date>
    </item>
    <item>
      <title>Re: Best practice for staff BYOD devices</title>
      <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/best-practice-for-staff-byod-devices/m-p/91835#M13159</link>
      <description>&lt;P&gt;What version of HiveManager are you using? Depending on the version you are using you could potentially make use of the Aerohive API. My organization has employee on-boarding/off-boarding automated and part of the process is to provision/de-provision accounts for BYOD. We also have an internal support portal where employees can go and do BYOD self-service. The API is super simple to use - just go to developer.aerohive.com and sign up for an account so you can get access to the documentation. NOTE: The API does NOT work for Hivemanager NG on-prem so you must either be using Classic with the online ID Manager or using HiveManager Select. &lt;/P&gt;</description>
      <pubDate>Thu, 23 May 2019 20:43:21 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/aerohive-migrated-content/best-practice-for-staff-byod-devices/m-p/91835#M13159</guid>
      <dc:creator>dennis_tobias</dc:creator>
      <dc:date>2019-05-23T20:43:21Z</dc:date>
    </item>
    <item>
      <title>Re: Best practice for staff BYOD devices</title>
      <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/best-practice-for-staff-byod-devices/m-p/91836#M13160</link>
      <description>&lt;P&gt;Hi Dennis&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are using cloud based Aerohive NG. Ive just created an account and am looking through the documentation. What you are doing at your organisation sounds very interesting. Hopefully i can make sense of the information on the website.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Fri, 24 May 2019 16:50:11 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/aerohive-migrated-content/best-practice-for-staff-byod-devices/m-p/91836#M13160</guid>
      <dc:creator>robert_davies</dc:creator>
      <dc:date>2019-05-24T16:50:11Z</dc:date>
    </item>
    <item>
      <title>Re: Best practice for staff BYOD devices</title>
      <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/best-practice-for-staff-byod-devices/m-p/91837#M13161</link>
      <description>&lt;P&gt;We are creating a solution where users can login with Azure/office365 credentials and than they get a ppsk back. If the employee leaves the company we delete the ppsk. We also link the user to a user profile based on Azure/Office365 groups.  Probably we will make a product from this solution.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But indeed if you know api's you can create this by your own. &lt;/P&gt;</description>
      <pubDate>Mon, 03 Jun 2019 14:08:08 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/aerohive-migrated-content/best-practice-for-staff-byod-devices/m-p/91837#M13161</guid>
      <dc:creator>JonasD_Complit</dc:creator>
      <dc:date>2019-06-03T14:08:08Z</dc:date>
    </item>
    <item>
      <title>Re: Best practice for staff BYOD devices</title>
      <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/best-practice-for-staff-byod-devices/m-p/91838#M13162</link>
      <description>&lt;P&gt;Hi Dennis, what is not working on the op-prem? Our visititor registration solution is also working with the on-prem version&lt;/P&gt;</description>
      <pubDate>Mon, 03 Jun 2019 14:09:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/aerohive-migrated-content/best-practice-for-staff-byod-devices/m-p/91838#M13162</guid>
      <dc:creator>JonasD_Complit</dc:creator>
      <dc:date>2019-06-03T14:09:00Z</dc:date>
    </item>
    <item>
      <title>Re: Best practice for staff BYOD devices</title>
      <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/best-practice-for-staff-byod-devices/m-p/91839#M13163</link>
      <description>&lt;P&gt;@Jonas Dekkers​&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;That sounds like a great feature. What is the progress. We would be very interested.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best Regards,&lt;/P&gt;</description>
      <pubDate>Thu, 10 Oct 2019 16:55:04 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/aerohive-migrated-content/best-practice-for-staff-byod-devices/m-p/91839#M13163</guid>
      <dc:creator>systeembeheer6</dc:creator>
      <dc:date>2019-10-10T16:55:04Z</dc:date>
    </item>
    <item>
      <title>Re: Best practice for staff BYOD devices</title>
      <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/best-practice-for-staff-byod-devices/m-p/91840#M13164</link>
      <description>&lt;P&gt;Dear, the first version is in beta. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can you send an email to info@wiflex.eu? We can setup a demo account for you.&lt;/P&gt;</description>
      <pubDate>Thu, 10 Oct 2019 19:36:29 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/aerohive-migrated-content/best-practice-for-staff-byod-devices/m-p/91840#M13164</guid>
      <dc:creator>JonasD_Complit</dc:creator>
      <dc:date>2019-10-10T19:36:29Z</dc:date>
    </item>
  </channel>
</rss>

