According to support, only Windows Server 2022 is supported going forward in systems manager version 4.0 and higher. Can someone from Meraki comment on this decision? Server 2016 and 2019 are still fully supported operating systems by Microsoft. Even 2012 R2 is in extended life. Not being able to manage 75% of our server environment is not going to make it worthwhile for us to use SME. ... View more

We've been working on an issue with support where a certain SSID would not be broadcast. It was a teleworker VPN SSID. After much troubleshooting, it was determined that if a teleworker VPN has an intermittent connection with the concentrator, it will NOT broadcast the associated SSID. This is NOT displayed anywhere in the dashboard, either by UI or by any kind of error event entry. The only way to verify this behavior is with a packet capture to look at the beacon frames being broadcast (or lack thereof). Support applied a backend patch to address this particular issue (also not available via normal firmware updates).   However, we happened to have an employee staying at one of our locations and reporting that the guest WiFi network was not available. We looked at the AP in question, and it shows broadcasting. Upon doing a packet capture, we again noticed no beacons, just malformed packets. A reboot of the AP does not resolve the issue. This is not using a teleworker VPN, just the straight internal Meraki DHCP option.   If you've had users complaining about WiFi not showing up or weak signal and written it off as user error, you might want to do a packet capture to see if the SSID is actually transmitting, as the dashboard UI does not seem to reflect if it actually is. Pay particular attention if you are using a teleworker VPN/concentrator as well.   Take a look at the screenshots. One shows the correct operation - beacons being broadcast for all appropriate SSIDs. The second one shows no beacons, just bad packets. The second SSID shows in the dashboard as functioning normally, and there are no error logs or event logs we can ascertain.   Has anybody else seen this behavior? Running 30.5. The hotfix applied by support was to the MX, not the MR. ... View more

We've had a ticket open since November where certain devices will not complete the registration in systems manager. The dashboard for the computer will show "Client synchronization is not yet complete.". We've provided all the logs to support, and it's apparently a known issue with no estimated time to resolution. This makes it difficult for us to manage endpoints. Anybody else experienced this with any workaround? We've tried up to the 4.1.1 version. From reading the logs, my guess is that it can't create the tunnel back to Meraki because of a network card configuration issue, or perhaps specific hardware:   2024-03-26 11:21:55.212509 [2296]: service_main: G::lobal().config.m_tun_hosts has changed: (localhost:14) (re)starting tun_clients   The dashboard will show basic information about the endpoint: serial number, BIOS, Windows version, public IP.   Anybody else seen this? ... View more

We have a decent sized org, 200 APs, 10 MXs, 20 or so MS (rest are HPE/Aruba switching). Our co-term licensing for our entire organization is expiring early 2024. With lead times what they are, what are you all doing with planning for upgrades? We are wanting to do a product refresh at that time, but with lead times...we would have to order probably sometime soon.   Anyone else in a similar boat? Obviously we don't want to carry a 6 figure price tag for any longer than we have to. ... View more