Hello! I see that SM supports the new iOS/iPadOS 17 feature "Return to Service", which allows you to wipe a device but send a WiFi profile to have it set itself up after the wipe. You can find this feature on the new SM interface when you check the box of a device and then under command, erase devices. I've tried it a few times but it only unenrolls the device and wont wipe it. I don't see any documentation on Meraki's site, only on Apple's site. I have a case in but has anyone else tried this feature?
Can you raise a case for this please? And Direct Message me the case number when done?
I have yet to try this but I will try and test this myself with a device today if I can.
Tried this feature several times now, but it always just tells "Management profile removed" on the dashboard.
On the device itself seems like nothing has changed.
I can still find all apps and the management profile under the device settings.
I didn't file a case yet
Engineering are working on this. Stay tuned.
Hi, is there any update on this? We would like to use it too.
Meraki have a case open with Apple on this currently, so no update as of yet. As soon as we have an update, we'll update this thread
Meraki SM and Apple are still working together on this, but no ETA for resolution at this time.
Okay, thank you for the update. I was eager to try this in preparation for our summer iPad resets, so I wanted to check in and see if anyone had heard anything.
Any word a fix? It would be really great for us school districts to have this option in the summer.
With the new 17.5 I noticed a new error when trying to do a "return to service" erase.
No, I have not yet heard any communication around this. I have been patiently waiting. We have 1500 iPads to reset this summer and this would really make things go a lot faster if they had a solution or fixed whatever the issue is with the re turn to service option.
From what I can tell, it seems like a bug or maybe something missing in the Meraki end of things. Haven’t seen any official fix yet, but I’m following that Apple doc too.
I tried again and am still running into the same issue, I assume there is no fix yet.