I'd try creating the Network (and maybe claiming) in action batches, see if you have better results.  In the past I noticed some behavior differences between using and not using action batches. ... View more

I think your options are Setup a dedicated domain user as a service account, and setup an email address for that account.  Then use that email in Meraki as your API user. Have an email alias address added to your email account.  Then use that email alias address in Meraki as your API user. Have an email distribution-list created.  Add you and whoever to the distro, then use that email distribution-list address in Meraki as your API user.   From the Meraki perspective, it does not have to be a real person or a real domain account at your company.  It just has to be a valid email address that someone verifies, logs into the Dashboard and creates an API key in that profile.  I've used all three above depending on the use case. ... View more

It's not the last rule, it's the second to last rule.  When you make the call to get the rules from your test network it includes the two bottom Meraki "default" rules. - Wireless clients access LAN - Default rule If you look at the "Wireless client access LAN rule you'll see that the 'destCidr' is a string, 'Local LAN'.  That's your problem.  It's not an acceptable value to pass in.   { 'comment': 'Wireless clients accessing LAN', 'ipVer': 'ipv4', 'policy': 'deny', 'protocol': 'Any', 'destPort': 'Any', 'destCidr': 'Local LAN',     # <--- This one } Neither of those two Meraki "default rules need to be passed in.  They already exist in the destination Network you're configuring (again by default).  So, you'll want to delete those last two rules in the list before making the API call to PUT all the rules in the destination Network.  If you need to adjust the "Wireless clients accessing LAN" rule you don't want to pass the actual rule in with your rules, you need to add the additional API parameter allowLanAccess.  The last rule "Default rule" is not adjustable.  It's always Allow IPv4 Any Any Any. ... View more

It would be nice if the docs gave better examples.  I believe the expected format is  ?serials[]=Q2ED-AAAA-AAAA if you need more than one device it would be ?serials[]=Q2ED-AAAA-AAAA&serials[]=Q2ED-BBBB-BBBB ... View more

Thanks, I'll check that thread! ... View more

Ok cool, thanks.  I was kind of thinking that since on the MR84  the ant ports were dual band that it didn't really matter.  I just couldn't find any documentation to verify. ... View more