<?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 Meraki BYOD solution component in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/meraki-byod-solution-component/m-p/5471479#M292648</link>
    <description>&lt;P&gt;Hi Merakian,&lt;/P&gt;&lt;P&gt;Just wonder is there any Meraki BYOD solution design guide, configuration guide documentation around?&lt;/P&gt;&lt;P&gt;I intend to create the BQ but i have no idea what need to be include?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Noel&lt;/P&gt;</description>
    <pubDate>Tue, 01 Jun 2021 06:38:59 GMT</pubDate>
    <dc:creator>yong khang NG</dc:creator>
    <dc:date>2021-06-01T06:38:59Z</dc:date>
    <item>
      <title>Meraki BYOD solution component</title>
      <link>https://community.cisco.com/t5/wireless/meraki-byod-solution-component/m-p/5471479#M292648</link>
      <description>&lt;P&gt;Hi Merakian,&lt;/P&gt;&lt;P&gt;Just wonder is there any Meraki BYOD solution design guide, configuration guide documentation around?&lt;/P&gt;&lt;P&gt;I intend to create the BQ but i have no idea what need to be include?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Noel&lt;/P&gt;</description>
      <pubDate>Tue, 01 Jun 2021 06:38:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/meraki-byod-solution-component/m-p/5471479#M292648</guid>
      <dc:creator>yong khang NG</dc:creator>
      <dc:date>2021-06-01T06:38:59Z</dc:date>
    </item>
    <item>
      <title>Re: Meraki BYOD solution component</title>
      <link>https://community.cisco.com/t5/wireless/meraki-byod-solution-component/m-p/5471480#M292649</link>
      <description>&lt;P&gt;You are a reseller, I guess?  You may want to start at &lt;A href="https://salesconnect.cisco.com" target="_blank" rel="nofollow noopener noreferrer"&gt;https://salesconnect.cisco.com &lt;/A&gt;and read up on Meraki a bit.  BYOD is a pretty vague marketing term and does not correlate exactly with specific products or SKUs.  What exactly have you been asked to quote?&lt;/P&gt;</description>
      <pubDate>Tue, 01 Jun 2021 15:58:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/meraki-byod-solution-component/m-p/5471480#M292649</guid>
      <dc:creator>Brandon Svec</dc:creator>
      <dc:date>2021-06-01T15:58:38Z</dc:date>
    </item>
    <item>
      <title>Re: Meraki BYOD solution component</title>
      <link>https://community.cisco.com/t5/wireless/meraki-byod-solution-component/m-p/5471481#M292650</link>
      <description>&lt;P&gt;Hi Brandon, &lt;/P&gt;&lt;P&gt;First of all, thanks for reply, &lt;/P&gt;&lt;P&gt;Eventually i looking at Cisco BYOD solution, particular wireless access method, and try with no ISE involve maybe.&lt;/P&gt;&lt;P&gt;So i wonder if meraki can do &lt;/P&gt;&lt;P&gt;1. Guest Access Management&lt;/P&gt;&lt;P&gt;2. 802.1x &lt;/P&gt;&lt;P&gt;3. device onboarding&lt;/P&gt;&lt;P&gt;What component do i need to invest MX, SM , yet MR, MS as access media&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Noel&lt;/P&gt;</description>
      <pubDate>Wed, 02 Jun 2021 06:00:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/meraki-byod-solution-component/m-p/5471481#M292650</guid>
      <dc:creator>yong khang NG</dc:creator>
      <dc:date>2021-06-02T06:00:25Z</dc:date>
    </item>
    <item>
      <title>Re: Meraki BYOD solution component</title>
      <link>https://community.cisco.com/t5/wireless/meraki-byod-solution-component/m-p/5471482#M292651</link>
      <description>&lt;P&gt;The MX typically does not play any significant role in the BYOD solution. The onboarding runs through manual enrolment or through the MR access-points and provisions the client into the SM Mobile Device Management.&lt;/P&gt;&lt;P&gt;Best to build a test-system for all your intended devices as there are some gotchas that make it less usable compared to an ISE. For example, the BYOD users can automatically get a certificate for WLAN access. But this is not an intended use case for your domain-users which need a different authentication. And these certificates can not be used on all switch ports. &lt;/P&gt;&lt;P&gt;If you have an all-wireless, all BYOD environment, then it will be great. But if there are a significant amount of legacy devices you need "something else" for these. And the ISE could give you all at the same time. &lt;/P&gt;</description>
      <pubDate>Wed, 02 Jun 2021 09:40:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/meraki-byod-solution-component/m-p/5471482#M292651</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2021-06-02T09:40:57Z</dc:date>
    </item>
    <item>
      <title>Re: Meraki BYOD solution component</title>
      <link>https://community.cisco.com/t5/wireless/meraki-byod-solution-component/m-p/5471483#M292652</link>
      <description>&lt;P&gt;It sounds like three basic SKUs you are after if I understand correctly:&lt;/P&gt;&lt;P&gt;1. Choose the model(s) of MR you like.&lt;/P&gt;&lt;P&gt;2. Choose license term 1-10 years and include one license per MR.&lt;/P&gt;&lt;P&gt;3. Choose number of Systems Manager licenses required. &lt;/P&gt;&lt;P&gt;I encourage you to do Meraki Fit training if you are a reseller with a Cisco login: &lt;A href="http://community.meraki.com/merakifit" target="_blank"&gt;http://community.meraki.com/merakifit&lt;/A&gt; and/or watch some webinars/content on Meraki's YouTube channel to get a firm grasp of how it all works and fits together.&lt;/P&gt;&lt;P&gt;Best.&lt;/P&gt;</description>
      <pubDate>Wed, 02 Jun 2021 16:40:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/meraki-byod-solution-component/m-p/5471483#M292652</guid>
      <dc:creator>Brandon Svec</dc:creator>
      <dc:date>2021-06-02T16:40:41Z</dc:date>
    </item>
    <item>
      <title>Re: Meraki BYOD solution component</title>
      <link>https://community.cisco.com/t5/wireless/meraki-byod-solution-component/m-p/5471484#M292653</link>
      <description>&lt;P&gt;And are you a Cisco reseller and do you work in the CCW tool?  If so, you can order NFR (not for resale) gear for an incredibly low price to have some lab gear and play around with if you like.  You can also do a free 2 week trial, but then you have to send it back or be charged.&lt;/P&gt;</description>
      <pubDate>Wed, 02 Jun 2021 16:44:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/meraki-byod-solution-component/m-p/5471484#M292653</guid>
      <dc:creator>Brandon Svec</dc:creator>
      <dc:date>2021-06-02T16:44:12Z</dc:date>
    </item>
    <item>
      <title>Re: Meraki BYOD solution component</title>
      <link>https://community.cisco.com/t5/wireless/meraki-byod-solution-component/m-p/5471485#M292654</link>
      <description>&lt;P&gt;Hi Karstenl,&lt;/P&gt;&lt;P&gt;Thanks for the reply.&lt;/P&gt;&lt;P&gt;Yup, all endpoint is wireless. Just want to get rid of Cisco ISE anyway.&lt;/P&gt;&lt;P&gt;I believe what you trying to say is leveraging the ISE profiling feature to recognize endpoint OS, in this case, i just try minimize the usage on device onboarding.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Thu, 03 Jun 2021 09:19:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/meraki-byod-solution-component/m-p/5471485#M292654</guid>
      <dc:creator>yong khang NG</dc:creator>
      <dc:date>2021-06-03T09:19:09Z</dc:date>
    </item>
    <item>
      <title>Re: Meraki BYOD solution component</title>
      <link>https://community.cisco.com/t5/wireless/meraki-byod-solution-component/m-p/5471486#M292655</link>
      <description>&lt;P&gt;No, that's not what I tried to say ... &lt;SPAN class="lia-unicode-emoji" title=":winking_face:"&gt;&lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;I was talking about how to authenticate your endpoints when entering the network. Your BYOD devices typically get a certificate enrolled and use the Meraki authentication (That is IMO one of the best features of SM). But the domain-PCs do not have a certificate from the Meraki Dashboard like the BYOD devices and have to be authenticated in a different way, for example through your Microsoft NPS.&lt;/P&gt;&lt;P&gt;The ISE could authenticate both your BYOD- and domain systems.&lt;/P&gt;</description>
      <pubDate>Thu, 03 Jun 2021 10:14:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/meraki-byod-solution-component/m-p/5471486#M292655</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2021-06-03T10:14:47Z</dc:date>
    </item>
  </channel>
</rss>

