<?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: Meraki Early Access Program: AP Zero Touch Deployment in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/meraki-early-access-program-ap-zero-touch-deployment/m-p/5531032#M311832</link>
    <description>&lt;P&gt;I really love the idea , but I'm afraid the limitations might kill the hype.&lt;/P&gt;&lt;P&gt;1- Does it work with SecurePort ? SecurePort requires that the AP is in the same network as the switches&lt;/P&gt;&lt;P&gt;2- Can it support a more complexe naming scheme ?  Our APs do not end with the SEQ number. AP + Unique LOC ( 3 letters ) + Floor ( 2 Chars ) + SEQ ( 2 Chars ) + ZZ&lt;/P&gt;</description>
    <pubDate>Wed, 12 Nov 2025 18:18:39 GMT</pubDate>
    <dc:creator>Raphael_L</dc:creator>
    <dc:date>2025-11-12T18:18:39Z</dc:date>
    <item>
      <title>Meraki Early Access Program: AP Zero Touch Deployment</title>
      <link>https://community.cisco.com/t5/wireless/meraki-early-access-program-ap-zero-touch-deployment/m-p/5531029#M311829</link>
      <description>&lt;H3&gt;&lt;A title="AP Zero Touch Deployment" href="https://documentation.meraki.com/MR/Design_and_Configure/Deployment_Guides/AP_Zero_Touch_Deployment" target="_self" rel="nofollow noopener noreferrer"&gt;AP Zero Touch Deployment&lt;/A&gt;&lt;/H3&gt;&lt;P class=""&gt;Simplify AP deployments with automated, one-click provisioning.&lt;/P&gt;</description>
      <pubDate>Wed, 12 Nov 2025 04:15:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/meraki-early-access-program-ap-zero-touch-deployment/m-p/5531029#M311829</guid>
      <dc:creator>RWelch-USA</dc:creator>
      <dc:date>2025-11-12T04:15:18Z</dc:date>
    </item>
    <item>
      <title>Re: Meraki Early Access Program: AP Zero Touch Deployment</title>
      <link>https://community.cisco.com/t5/wireless/meraki-early-access-program-ap-zero-touch-deployment/m-p/5531030#M311830</link>
      <description>&lt;P&gt;Never convinced by zero touch deployments.  Pre-staging has been ingrained in me. Equipment may be more reliable and robust nowadays but I like the assurance that the eqpt I’m deploying works and I’ve witnessed that.&lt;/P&gt;</description>
      <pubDate>Wed, 12 Nov 2025 08:41:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/meraki-early-access-program-ap-zero-touch-deployment/m-p/5531030#M311830</guid>
      <dc:creator>MerakiGnome</dc:creator>
      <dc:date>2025-11-12T08:41:43Z</dc:date>
    </item>
    <item>
      <title>Re: Meraki Early Access Program: AP Zero Touch Deployment</title>
      <link>https://community.cisco.com/t5/wireless/meraki-early-access-program-ap-zero-touch-deployment/m-p/5531031#M311831</link>
      <description>&lt;P&gt;I remember hearing about this at either Cisco Live or a partner training, It appears you have to load the new aps and then match them up, which is fine, but I'd prefer to  have them pre-loaded and just rely on matching up serials as an option, then things could happen automatically as soon as they are plugged in.&lt;BR /&gt;&lt;BR /&gt;I can see why you might want the other way, but having both would be ideal imo.&lt;/P&gt;</description>
      <pubDate>Wed, 12 Nov 2025 14:39:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/meraki-early-access-program-ap-zero-touch-deployment/m-p/5531031#M311831</guid>
      <dc:creator>mloraditch</dc:creator>
      <dc:date>2025-11-12T14:39:20Z</dc:date>
    </item>
    <item>
      <title>Re: Meraki Early Access Program: AP Zero Touch Deployment</title>
      <link>https://community.cisco.com/t5/wireless/meraki-early-access-program-ap-zero-touch-deployment/m-p/5531032#M311832</link>
      <description>&lt;P&gt;I really love the idea , but I'm afraid the limitations might kill the hype.&lt;/P&gt;&lt;P&gt;1- Does it work with SecurePort ? SecurePort requires that the AP is in the same network as the switches&lt;/P&gt;&lt;P&gt;2- Can it support a more complexe naming scheme ?  Our APs do not end with the SEQ number. AP + Unique LOC ( 3 letters ) + Floor ( 2 Chars ) + SEQ ( 2 Chars ) + ZZ&lt;/P&gt;</description>
      <pubDate>Wed, 12 Nov 2025 18:18:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/meraki-early-access-program-ap-zero-touch-deployment/m-p/5531032#M311832</guid>
      <dc:creator>Raphael_L</dc:creator>
      <dc:date>2025-11-12T18:18:39Z</dc:date>
    </item>
    <item>
      <title>Re: Meraki Early Access Program: AP Zero Touch Deployment</title>
      <link>https://community.cisco.com/t5/wireless/meraki-early-access-program-ap-zero-touch-deployment/m-p/5531033#M311833</link>
      <description>&lt;P&gt;Interesting.&lt;/P&gt;&lt;P&gt;For the environments where I have the C9800, I use regular expressions to apply tags to the Access Points. This way, the only work I have to do is rename the APs, and as soon as it returns to the controller, the correct tags are already applied.&lt;/P&gt;&lt;P&gt;It's not zero-touch, but it saves a lot of time. &lt;SPAN class="lia-unicode-emoji" title=":grinning_face_with_smiling_eyes:"&gt;&lt;span class="lia-unicode-emoji" title=":grinning_face_with_smiling_eyes:"&gt;😄&lt;/span&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 12 Nov 2025 18:37:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/meraki-early-access-program-ap-zero-touch-deployment/m-p/5531033#M311833</guid>
      <dc:creator>aleabrahao</dc:creator>
      <dc:date>2025-11-12T18:37:17Z</dc:date>
    </item>
    <item>
      <title>Re: Meraki Early Access Program: AP Zero Touch Deployment</title>
      <link>https://community.cisco.com/t5/wireless/meraki-early-access-program-ap-zero-touch-deployment/m-p/5531034#M311834</link>
      <description>&lt;P&gt;IMO, this feature will have a big positive impact to make AP RMA and new deployment more seamless. Will it solve for every possible corner case like SecurePort? Of course not! However, we can always make MVP+ additional later.&lt;/P&gt;&lt;P&gt;Free free to submit enhancement requests via &lt;A href="https://ciscospinfra.ideas.aha.io/" target="_blank" rel="nofollow noopener noreferrer"&gt;https://ciscospinfra.ideas.aha.io/&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 12 Nov 2025 22:58:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/meraki-early-access-program-ap-zero-touch-deployment/m-p/5531034#M311834</guid>
      <dc:creator>aneduzhk</dc:creator>
      <dc:date>2025-11-12T22:58:09Z</dc:date>
    </item>
    <item>
      <title>Re: Meraki Early Access Program: AP Zero Touch Deployment</title>
      <link>https://community.cisco.com/t5/wireless/meraki-early-access-program-ap-zero-touch-deployment/m-p/5531035#M311835</link>
      <description>&lt;P&gt;Thanks &lt;A href="https://community.meraki.com/t5/user/viewprofilepage/user-id/13291"&gt;@Raphletourn&lt;/A&gt; for feedbacks! definitely we can add SecurePort scenario support in next iterations. ther e are even more exciting list of features being discussed on AP ZTD solution and looking forward to support broader deployment scenarios!&lt;BR /&gt;in terms of AP naming support, yes I think there are huge room for improvements. Adding RegX expression is one of topic that we've been tinking but it also comes with some complexity too.  one idea to overcome that is using API!  AP ZTD operations are fully &lt;A href="https://developer.cisco.com/meraki/api-v1/get-organization-wireless-devices-provisioning-deployments/" target="_self" rel="nofollow noopener noreferrer"&gt;API ready&lt;/A&gt; and customer can add more complex rule in AP naming &lt;/P&gt;</description>
      <pubDate>Wed, 26 Nov 2025 19:36:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/meraki-early-access-program-ap-zero-touch-deployment/m-p/5531035#M311835</guid>
      <dc:creator>minse</dc:creator>
      <dc:date>2025-11-26T19:36:18Z</dc:date>
    </item>
    <item>
      <title>Re: Meraki Early Access Program: AP Zero Touch Deployment</title>
      <link>https://community.cisco.com/t5/wireless/meraki-early-access-program-ap-zero-touch-deployment/m-p/5531036#M311836</link>
      <description>&lt;P&gt;Wow that would be perfect ! &lt;/P&gt;&lt;P&gt;Naming the AP via API sounds excellent too. Thanks for the follow up !&lt;/P&gt;</description>
      <pubDate>Wed, 26 Nov 2025 19:53:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/meraki-early-access-program-ap-zero-touch-deployment/m-p/5531036#M311836</guid>
      <dc:creator>Raphael_L</dc:creator>
      <dc:date>2025-11-26T19:53:29Z</dc:date>
    </item>
    <item>
      <title>Re: Meraki Early Access Program: AP Zero Touch Deployment</title>
      <link>https://community.cisco.com/t5/wireless/meraki-early-access-program-ap-zero-touch-deployment/m-p/5531037#M311837</link>
      <description>&lt;P&gt;Bulk AP Naming changes are one of topics that we are trying to tackle and Catalyst Center offer similar services as part of AP Config workflow. &lt;/P&gt;</description>
      <pubDate>Wed, 26 Nov 2025 20:13:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/meraki-early-access-program-ap-zero-touch-deployment/m-p/5531037#M311837</guid>
      <dc:creator>minse</dc:creator>
      <dc:date>2025-11-26T20:13:07Z</dc:date>
    </item>
  </channel>
</rss>

