Hello @Kanika_Bhatia,   To completely remove a iOS device from management, the steps in the Uninstalling Systems Manager and Removing Managed Devices documentation for iOS/iPadOS should be performed. The steps required will vary depending on whether or not the device was ADE enrolled.   If the device is no longer seen as managed within the dashboard, you could follow the general steps to completely erase the device as seen in the Unenrolling from a MDM Provider - iOS documentation. If these steps are not working, it is recommended to reach out to Apple Support in order to discover the steps to put the device in the DFU or recovery mode in order to completely wipe it.   Best, Feli ... View more

Hello @jimvad, Shared iPad with Apple Business Manager offers a variety of options for a single device to be shared amongst several users, depending on your company's specific needs and use case (i.e. using Managed Apple IDs, federated auth, temporary guest sessions)   To help determine which options may be best for your business, please feel free to check out this Meraki documentation and video on Apple Shared Device Mode and Guest Temporary Sessions.   Additionally, Apple's recommendations for Shared iPad are provided in the following Apple documentations:   Supporting Shared iPad — Deployment and Management Tutorials   Prepare Shared iPad   Shared iPad sign in options    Shared iPad overview   Best, Feli ... View more

Ah, always that local status page disablement that will do it each time. 🙂  Glad @Marcel_Smal suggested looking here! @Adrian4, can always check the Organization > Monitor > Change Log page and filter for "Local device status page disabled" to find the culprit 😉     ... View more

Hi @Brash,   It would be very interesting to see what factors may be causing Splash page hits discrepancies between the networks; (i.e. Do the networks displaying summary Splash Page statistics have a MX device while the affected networks do not?, For the networks not displaying any Splash data, how many, if any, clients are seen connecting to the SSID when viewing Network-wide > Monitor > Clients, etc.).   If you have not already done so, I would highly suggest opening a Meraki support case, so that an agent could look into your specific network configurations and verify the backend reporting between the networks and Summary report. To open a support case via the dashboard, please navigate to (?) > Get Help & Cases > Pick a Tile to Contact Support > Submit a case or by following the steps provided in the Contact Cisco Meraki Support document here. Best, Feli   ... View more

Hi @Bartounet, Linked below is the official firmware FAQ documentation referencing the inquiry and solutions provided by @rhbirkelund and @Ryan_Miles; Managing Firmware Upgrades: "Why does the Firmware upgrades page shows networks that do not have corresponding device types?"  The main benefit I find in keeping all of the product types updated in the combined network (even if a device is not currently within a network) is that if a device of that type is added in the future, it will automatically pull the latest stable firmware once it makes its initial contact to the Meraki Cloud. Best, Feli ... View more

Hello @Malimber, @MartinLL and @DarrenOC are correct. The device move process between organizations can take up to an hour or so to fully sync on the backend (and potentially even several hours if the device move is between organizations in different regions.. i.e. moving a device from a .com org to a .ca org)  If you are still receiving the already claimed message after waiting this time period, please open a support case (detailing the serial number of the device in question), so that the backend sync can be looked into at a deeper level. To open a support case via the dashboard, please navigate to (?) > Get Help & Cases > Pick a Tile to Contact Support > Submit a case or by following the steps provided in the Contact Cisco Meraki Support document here. Best, Feli ... View more

Good day @RaphaelL, Thank you for your patience with this matter. It's been confirmed that the Called-Station-ID value is indeed sent in the format of AP MAC:SSID and not BSSID:SSID. These corrections have been completed in the Configuring RADIUS Authentication with WPA2-Enterprise documentation as well. Thank you so much for your awesome feedback and helping to keep the documentation at its best! Best,  Feli  ... View more

Hello @AlanD,   These great follow up questions posed by @cmr will certainly be helpful in scoping this issue. However, since you are noticing this issue with other URLs and a review of your network's specific configurations will help to resolve the issue in a quicker manner, I highly recommend opening a support case directly with Meraki Support. A support engineer will be able to take a look at your dashboard network configurations, assist with packet captures if required,  and check any errors on the backend. Additionally, if you are Configuring VPN Exclusion Rules by DNS Hostname, the MX will need to see a DNS query match for the hostname (i.e. latamairlines.com) over UDP port 53 each time after expiry for the exclusion to work.   To open a support case via the dashboard, please navigate to (?) > Get Help & Cases > Pick a Tile to Contact Support > Submit a case or by following the steps provided in the Contact Cisco Meraki Support document here. Best, Feli ... View more

Hello @Andrea_Hopkins, As a general rule, it is normally recommended to make any dashboard configuration changes during downtime or in a maintenance window. If any unanticipated issues arise as a result of the change, it will not affect live production and can be reverted without significant impact. Additionally, if the changes are being made on a specific model device like the MX84, it is a known unresolved issue that a brief period of packet loss may occur when a configuration change is made on the appliance, as seen in the firmware change log below: Best, Feli ... View more

Hi @Dunky, Awesome, glad to hear that the direct streaming issue was resolved!   Best,  Feli ... View more

Hi @Dunky, Is direct streaming on the LAN failing when testing with different browsers and/or different devices? Here are a few additional things to check to help troubleshoot this issue; Ensure the client can reach/ping the private IP of the camera Remove any ACLs blocking interVLAN or intraVLAN communication between the MV and client Check and verify DNS resolution   -If using custom or internal DNS servers, ensure '*.devices.meraki.direct' is allowed Check that TCP port 443 traffic is allowed for the TLS handshake Make sure cameras are running the latest stable MV firmware release   The following two documentations provide information and troubleshooting tips for direct streaming: 1. Cloud proxy vs. direct streaming 2. MV LAN Streaming Troubleshooting If you continue to run into the LAN streaming issue, please feel free to open a case with Meraki Support to have an engineer review dashboard settings specific to your network. A support case can be opened in the dashboard by navigating to (?) help > Get Help & Cases > Pick a Tile to Contact Support > Submit a case or by following the steps provided in the Contact Cisco Meraki Support document here. Best, Feli ... View more

Good day @RaphaelL, The feedback is greatly appreciated! You are correct, those three points require correction in the MR Meraki RADIUS 2.0 article. I will let you know once those updates have been completed. And for the second article, Configuring RADIUS Authentication with WPA2-Enterprise, this information has been forwarded to the appropriate team for review. Once the investigations are complete, the article will be updated accordingly.   Thank you! Best, Feli ... View more

Greetings @Jyrki_Halonen, @cmr is correct. Both models support PoE+. The MS210 Overview and Specifications documentation provides a breakdown of PoE capabilities by model, along with other model-specific details:   Have a great day! Best, Feli ... View more

Hello @alemabrahao,   Thank you for providing this information. There are some DHCP option limitations regarding the MS390 and Catalyst 9300 models. Since this initial post, the unsupported DHCP options have been updated in the Setting Custom DHCP Options documentation under the section 'Unsupported DHCP options on MS390 and Meraki-managed C9300'.   Please let me know if this addition to the documentation is acceptable and helps to address the matter.   Best, Feli ... View more

Hello @timmy-zhou,   As PhilipDAth mentioned, this message regarding APNS certificate renewal can be safely disregarded if you no longer have need of this feature and no longer have any iOS or macOS devices enrolled in Systems Manager. However, if these devices are still enrolled and are required to be managed in Systems Manager, you will need to follow the steps in the documentation below to properly renew the APNS cert every 365 days: https://documentation.meraki.com/SM/Device_Enrollment/Apple_MDM_Push_Certificate#Renewing_an_Apple_MDM_Push_Certificate ... View more

Hello @Warren65,   As kYutobi mentioned, please ensure that the value of the roles match.  The "Assertion contains no role" error is reported when the role assertion is either completely missing in the POST or when the role assertion name is invalid. For the user that is experiencing the error, you can click on their login event and click Full XML to view the assertion information. An example of viewing and verifying the assertion passed in the XML is provided in the following SAML Login History Events documentation: https://documentation.meraki.com/General_Administration/Managing_Dashboard_Access/SAML_Login_History_Events#Assertion_contains_no_role Best, Feli ... View more

Hi @Richard-Tapp, Brash and cmr pretty much covered it! This Product End-of-Life (EOL) Policy page is another great reference 🙂   A product's EOL (End-of-Life) and EOST (End-of-Support) date are basically equivalents and reference the same date. When the device reaches EOL/EOST, the product's lifetime warranty period also ends (if it's a product covered by a lifetime warranty, which MS switches are.) Additionally, the device is no longer affirmatively supported by Cisco Meraki (please still feel free to open a Meraki Technical Support case on these devices if needed, but please be aware that this support will be on a best case effort basis and not guaranteed.) After the EOL/ EOST date, the changes that may occur will include the following: Cisco Meraki cannot guarantee that legacy hardware products will be able to connect to the management software indefinitely following the EOST Date; Cisco Meraki Technical Support may no longer troubleshoot the legacy hardware products; Cisco Meraki may no longer issue firmware updates or patches for the legacy products; and New software features available for the management software may not be compatible with the legacy hardware functionality or with the firmware running on the legacy hardware.   Best,  Feli   ... View more

Hello @Knowledge_gainr, What PhilipDAth said is correct - it's not supported to specify specific people/sponsors to receive the email within the domain (as any user with an email from the domain will be able to grant access to guests). However, the following workaround is suggested in this documentation and is recommended: If an organization requires only specific users to grant access to guests, these specific users will need to have their emails on a isolated domain that is only for these users. Then, you must specify this domain as the "sponsor email domain", which is a domain that contains only these few specific user email addresses. The below example is provided: "For example, if the specified domain is meraki.net, any employee with a username@meraki.net email will be able to sponsor the guests. If the administrators want only specific emails to have the authority, then the specified domain has to be a different domain; for example "@merakiguestsponsor.net" with only a few emails on that domain like username@merakiguestsponsor.net that can be specified by guests to grant access to them." Best, Feli ... View more

Hola @MarioOG, Por favor perdona mi español. ¿Los AP MR56 informan en el tablero que están funcionando en modo de bajo consumo (802.3at)? ¿Está habilitado LLDP en los puertos del switch Catalyst 9407 que suministran energía a los AP?   Varios puntos de acceso Meraki requieren que LLDP esté habilitado mientras negocian una potencia superior a 15,4 W, y algunos conmutadores Catalyst tienen CDP habilitado pero LLDP deshabilitado.   Consulte la siguiente documentación para asegurarse de que LLDP esté habilitado y disponible en el conmutador y puerto al que está conectado el AP: https://documentation.meraki.com/MR/Other_Topics/Low_Power_Mode_on_Cisco_Switches ... View more

Hello @Carlo99, This scenario will require a password reset. However, please note that password resets for MSP accounts will generally take some time to propagate and sync across the organizations. If after 30 minutes to 1 hour you've noticed the password hasn't yet synced across the organizations, please feel free to reach out to Meraki Support by creating an email case (or calling in to support as Darren mentioned). Best, Feli ... View more