Thank you @sbohmer, your confirmation about the 2.0+ URL pointed me to the solution. Previously I had only changed the value of the URL, but had not created a new server. I realised, that there was a certificate of ios.meraki.com in the properties of my old server config, which did not change when I put in a different URL. By creating a new server with the 2.0+ URL, I saw the certificate *.meraki.com in the properties. Afterwards it worked immediately. So my fault was to rewrite the registration url of an existing server, not creating a new server with registration url. Hope this helps! ... View more

I guess so. I solved it by adding a dummy wifi network. Called it "dummy-wifi" and set a random password. ... View more

The other big issue is the iPad Touch doesn't have a GPS chip - so it can't report its real location.   It uses a simulated system of which SSID it is connected to and which public IP it is connecting to the cloud from to "guess" its location, but this is not something you could rely on down to a single building. ... View more

Hi @alexnilsson,   Narrowing this down a bit further; a single device enrolled 15th February was fine (assuming this device was not reset). So, between 15th February and 18th February this appears to have fallen over.   I would be than happy to share the device links, but I am sure the Meraki Support Team would be fully aware of the changes taking place. Quote this post and ask them to PM if required.   Whilst I appreciate this will be causing frustration, our business case does not use this feature; we do not allow people to put Apple ID's on to the devices. Whilst I agree this is a bug and should be fixed, it would very improper of me to raise a case as it is not causing me an issue.   But we are a community and others here might not be aware of this bug and be very grateful you have raised this publicly. Hopefully they can get it fixed soon! ... View more

I will take a small polo if there's any left!! 😄  ... View more