I eventually brought in my Meraki sales representative.   In my situation, Meraki believes the antenna is at fault, indicating to the AP the wrong antenna model. They intend to replace all 20 of the F6 antennas. I will hold off on forming an opinion until I try this solution, but I'll defer to their expertise for now.   I expect these replacements to arrive in a couple of weeks, and I will provide an update on the status after testing and installation. ... View more

Its your device most likely. There are some client devices in the wild that quite frankly should be replaced with more modern chipsets and drivers. Some 2.4GHz devices are intolerant of SSIDs that are being broadcast on 2.4 and 5GHz simultaneously, have also seen some that intolerant of pruning older data rates.   If you can upgrade the firmware/driver on your device   I would suggest get your instrument requirements and tailor your SSID and data rates to match it.   If you can join the SSID with another item it is your device. ... View more

Reflecting on @Bruce's comment, you might be better off using content rules rather than L3 rules.  You block "*" and then just allow added sites. https://documentation.meraki.com/MX/Firewall_and_Traffic_Shaping/Blocking_Websites_with_Content_Filtering_and_Layer_7_Firewall_Rules    But it can be painful.  When you create rules this way they don't kick in immediately.  This is because of caching.  So you can make a change, and really need to reboot to make sure.   Also note that a simple web site can load components from lots of web sites, and you have to allow all of those as well for it to work.  If you are in Chrome, go CTRL-SHIFT-I to enabled developer mode, click on the sources tab, load your web site, and then look at all of the sources referenced.  You need to allow all of them.   For example, to allow access to meraki.com, you need to allow about 30 (guestimate) additional URLs.  There are so many they don't even fit on one page in the developer tools.     ... View more

>Do I need to create a policy Object and include all the FQDN's for Office 365 (The lengthy list)   You could do that.  You could use do contenting filtering, block "*" and then whitelist the URLs allowed.   Another less accurate approach but easier to configure is to use content filtering categories on the VLAN, and filter pretty much every category except for the one used by Office 365 (probably business something). ... View more