Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
During the last several years we have found the need to restart our Meraki Access Points weekly. These restarts appear to clear the cached entries and allow a more optimal connectivity during the work week. We are attempting to review regularly that ...
Early last week we found that AD authentication was not working with a local network server and the Meraki Agent (ver. 3.1.1). We also attempted to create a case through our Meraki Dashboard and found we are unable to do so. We have placed numerous c...
Thank you for the ideas, I don’t believe a 30 minute down window is ideal but your second idea provides a much better approach (nice out of the box thinking). In the end I’ve found we don’t have the “Device Boot” Feature yet…imagine 3 months from rol...
Yes, in large deployments where many shop floor devices (iPhones, tablets, kiosks, handheld barcode scanners, equipment monitoring, etc.) are moving around from AP to AP they build up the cache table which begins making them get a little flaky after ...
Doing some further research, it appears we have a mix of Meraki Access points running two different firmware versions. The latest APs are operating at version 30.6, whereas the older APs are operating at version 26.8.3. The new "Device Boot" feature ...
Unfortunately, a script running only logs if the script ran and is not able to track the physical power cycle of the AP. I do already have a script which tells me if my batch file was successful, but CMMC compliance requires an audit trail such as a ...
I believe "ww" responded similarly, but we do not have the "Device Boot" choice within our filters. Even if we try to type it in manually, it will not take since there is not choice available. It is possible this new feature has not yet been deployed...