Hi SDG, This is based on the HTTP GET from the client device as described in this document. You should obtain a packet capture to confirm that this information is correct. Also, some clients may misidentify themselves when specifying the user agent string field in the HTTP GET request, and enforcement of device type policies is done on a best effort basis depending on the information provided by the client. If you need to enforce security-focused policies based on device type, we recommend that you use a solution such as Meraki Systems Manager or Cisco ISE.   https://documentation.meraki.com/MR/Group_Policies_and_Block_Lists/Applying_Policies_by_Device_Type#Client_Identification ... View more

Hi Richard, Did you get this working?  I'm trying to do this with Jamf as the MDM to connect to the Meraki Wireless using Microsoft SCEP ... View more

disabling AMP might be a workaround, but it should not be the "accepted solution" ... View more

Kudos to you for the update, CarolineS! ... View more

Thank you @Uberseehandel, I had a call with an engineer from Meraki and that is actually that he suggested for the aisles.   @PhilipDAth @BlakeRichardson Yeah, I think I'll go with 10. I always ask for a bit more than expected, as you say.   @MerakiDave When I had that chat with a colleague of yours it was the day that is was announced. However, I’m from South Africa and I am told it will only be approved here in June. We’re moving in to the new place in June so might be too tight. I’ll chat to my account manager to see if there are more exact times. ... View more

Hi,   We experienced this, was a bit of nightmare. We tried factory resetting and upgrading again etc. We eventually got it to stick by calling support and they statically assigned the IP from their side. At the time, it was a beta feature but I think now it's in the Stable Release Candidate. ... View more