- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Meraki failing to clear passcode on iPad
Solved! Go to solution.
- Labels:
-
iOS
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
That you got the "MCPasscodeErrorDomain" response shows the Meraki SM sent the command successfully to the device, and that the device received it, but couldn't action it.
Getting the inability to do any further commands against the device would imply that there was a deeper issue with the device itself. Whilst brutal, resetting it appears to have been the only resolution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@BishopM : Can you restart the iPad and try again ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks, I've tried that, several days ago, but it hasn't made a difference.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Did you run any other command and check if it works ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It's not responded to Meraki since 8 Aug:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I gave it a day or 2 to see if the iPad and Meraki would resume communication... but they didn't. Ended up restoring the iPad back to a fresh build and re-enrolling into Meraki and re-installing all the apps. A lot of work to clear a passcode. Will test another iPad and see if the Meraki "Clear Passcode" feature is working at all with iOS 15.6
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
That you got the "MCPasscodeErrorDomain" response shows the Meraki SM sent the command successfully to the device, and that the device received it, but couldn't action it.
Getting the inability to do any further commands against the device would imply that there was a deeper issue with the device itself. Whilst brutal, resetting it appears to have been the only resolution.
