I wanted to share an experience I had recently while helping a customer with a hardware upgrade. It’s a bit of a frustrating situation that highlights a few potential gaps in Meraki's licensing process, especially when it comes to newer devices. I’m hoping to get some feedback from the community on how others have navigated this, and maybe someone from Meraki can weigh in on the issue. The Scenario: Upgrading from Z1 to Z3 (Then Z4) The customer had two Z1 devices that had failed, (power supplies dying)  and instead of simply logging a support case for a replacement, I suggested they upgrade to the newer Z3 models. The customer still had about two years left on their Z1 licenses, so I was confident we could just transfer those to the Z3s. However, the order for the Z3s was canceled, and I was notified that they were no longer available. The replacement order was automatically upgraded to Z4s. At first, I thought, "Great, no problem!"—especially since the Z4 comes with some really nice features. The Upgrade Process I received the Z4 units, swapped out the Z1 devices, and got the customer up and running. The next step was to make sure their remaining Z1 licenses were updated to cover the new Z4 devices. Here’s where things got tricky. The Licensing Roadblock I logged a case to convert the Z1 licenses to Z4 licenses, but the support agent told me that, according to their Knowledge Base (KB), license conversions like this aren’t allowed. The agent seemed unwilling to escalate the issue or explore other solutions, which left me feeling a bit stuck. I found it odd that a simple hardware upgrade didn’t seem to fit within the licensing framework, especially when the Z3 model (the one I initially ordered) was essentially out of stock and replaced by the Z4. For those who may want more context, the KB on Meraki’s licensing page lays out how license conversions typically work, but it doesn’t mention the Z4. Meraki Licensing Overview Is This a Policy Decision or an Oversight? So, now I’m left wondering: Is this a deliberate policy decision from the Business Unit (BU) to not allow license conversions to the Z4, or is it just an oversight in the Knowledge Base that hasn’t been updated yet? Either way, it feels like a simple upgrade is now stuck in a bit of a loop, with the only solution being to return the Z4s, log a new support case for Z1 replacements, and then wait another two years for the upgrade process to play out. Looking for Community Feedback I’m curious if anyone else has encountered a similar issue with the Z4 or if there’s a workaround that I might have missed. Has anyone been able to successfully convert Z1 licenses to Z4, or is this a case where we’ll need to wait for Meraki to update the KB and/or licensing process? I’d love to hear your thoughts or suggestions on how best to handle this situation. And if anyone from Meraki is reading this, any insight into whether this is something that could be addressed in the near future would be really helpful! ... View more

I am loving the new Wireless option on the Z4 WiFi 6 Wireless....  when I change anything I get this error    what does that mean ???? ... View more

Is meraki going to support the  environmental Sensors ??   Ambient temperature sensor Air quality sensor (Total Volatile Organic Compound [TVOC]) Relative humidity sensor   It may look like a Meraki Sensor ?     Also, do these Catalyst AP support Bluetooth connections to Meraki sensors ??   Any news when we can turn on the 6Ghz support in AUSTRALIA? ... View more

 I have had a few customers reach out to me about the Merkai Email Sent to them.   ===================================================   Hello valued Meraki customer,   Meraki will be discontinuing support for versions 1.0 and 1.1 of the Transport Layer Security (TLS) protocol used by wireless devices to communicate with Meraki Authentication. In order to facilitate the provisioning of enhanced security features, we will be requiring all customers to upgrade, at a minimum, to TLS version 1.2. This change will only affect wireless devices using TLS versions 1.0 and 1.1 when connecting to the Meraki Authentication server.   Timing: Due to security requirements, we do not have the ability to determine which of your devices, if any, are currently using the prior versions of the TLS protocol. In an effort to help you identify these devices, we will be temporarily disabling support for TLS 1.0 and 1.1 as a test. This action will cause a planned disruption of device connectivity, which will begin at 12:00 am PST on April 19, 2023 and end at 12:00 am PST on April 20, 2023. Any devices that experience an issue with connectivity during the test period may be using the prior versions of the TLS protocol.   Final retirement of TLS 1.0 and 1.1 will take place on May 17, 2023.    Required action: Please plan for the 24-hour test period accordingly. If any of your devices experience an issue with connectivity during the planned test period outlined above, you may be required to upgrade to TLS 1.2 or a later version. To help you determine where potentially-affected devices may be located, a list of your organizations with Meraki Authentication enabled   ===================================================     Why can Merkai not flag the clients using the OLD TLS protocols ???   Would make it much easier to know the issues before 19April.   A hospital cannot have wifi devices down for a day for testing.         ... View more