*Note:
This is only an issue with the original iPad Airs. jamf is aware of this issue.
We have this happening with an iPad mini 2 Wi-Fi (A1489) as well.
Managed student AppleID, DEP, supervised, and Config Profile for Restrictions.
Have been able to deliver update to iOS 11.0.1 while it is locked, but disabling Lost Mode still fails.
Also tried removing Restrictions Profile, and testing again still failed.
I know it is early to ask, but any likelihood of a resolve, without needing to DFU mode restore the iPad, in the next day or two?
I've got the same issue with the same error message running JSS 9.101.0 and iOS 11 on an iPad Mini 2. Device in question does have a managed Apple ID.
We are getting the same error. If there isn't a fix, I'll need to restore. Please let us know if anyone has any ideas.
It looks like iOS 11.0.1 fixes this issue. Although if you have an iPad Air/ Mini 2 on iOS 11 that doesn't help with having to DFU, removing all data and updating to 11.0.1
JSS 9.101.0-t1504998263
iPad Air, Updated to iOS 11.0.2
Sent a Lost Mode command.
Able to locate, able to send sound, able to disable Lost Mode, despite returned error: "Unable to Disable Lost mode..."
Tried same again:
Sent a Lost Mode command.
JSS returned error: "Could not be put into lost mode ... ", But the device went into Lost Mode (Always enforce Lost Mode checked)
Able to Locate, Able to Send Sound
Unable to disable Lost Mode, despite successfully sending "Clear Passcode" command to device, so communication was working
Rebooted device, it went off Wifi.
Tried Sierra's Internet Sharing> USB iPad, didn't work (self assigned IP).
Was able to put the device into recovery (not DFU) and using iTunes restore, wipe
and reactivate/DEP enroll successfully....
After re-enroll, record in JSS shows enrollment 5 minutes ago, 2 scoped apps install, but there is no "Enable Lost Mode" only "Disable Lost Mode" but device is not disabled. Sent "disable LOST mode" command successfully (which did nothing)
Sent ENABLE LOST MODE successfully (despite jss error) with sound, both worked
Sent Disable Lost Mode command, device was unlocked.
Rinse/repeat, worked as expected (successfully) with no glitches
so.... not reliable, but kinda works??
I'm seeing this on an iPad air (original). The iOS is 11.0.2 and I cant get it out of Lost mode. This is a rather large issue in our district since we are 1:1 and these kids are always losing their iPads, AND they are all original iPad airs... The DFU mode is most reliable right now.. I hope they can fix this soon!
Hate to add another but us too!
I have been testing this with an iPad 2. I can successfully enable and disable Lost Mode on the iPad 2 (MF081LL/A) six or seven times in a row with 100%.
BUT......if I enable Lost Mode and then do an Update Location and Play Sound, both will complete successfully.....but I can no longer disable Lost Mode.
I can do anything, like restart, send sound, etc... so commands are still be able to be successfully send and processed. But if any command is sent while in lost mode I lose the ability to disable Lost Mode.
My only solution is to send a Wipe command, which is successful, and re-enroll in JSS. Then can repeat the same scenario. Can Enable / Disable successfully......unless I send a command while in Lost Mode, then all other commands remain effective, EXCEPT for Disable Lost Mode.
Chiming in with another original iPad Air that is stuck in lost mode. Looks like i'll be DFU'ing this iPad.
Collin
We did some more testing today and follow up on my post above......
On iPad Mini 2....can enable lost mode, send sound and disable lost most.
BUT.....when we enter lost mode and request updated location... that seems to be the constant trigger to make the disable lost mode command not work. We can send any other command successfully, except for disable lost mode after a location request. Only solution is to send wipe command (which is successful) and start fresh.
Same issue here with an Air 2 on ios 11.0
I have an iPad doing this also.
Model: iPad mini 2nd Generation (Wi-Fi)
Model Identifier: iPad4,4
Model Number: ME789LL
iOS Version: 11.0.3
iOS Build: 15A432
Hello,
I am having this issue as well any updates? Our devices are restricted to connect to any device so restore is my only option would like to avoid this. It's a student device that has a good amount of work on it.
I too have this issue. iPad Air with iOS 11.0.3. This is a student device with also a good amount of work on it.
Same thing here. The iPad Air is at iOS 11.0.3, and we are at JSS 9.101.0.
Add us to this list as well. I can't believe it has been almost a month and still no solution to this problem other than to wipe and re-enroll the device. Doesn't that defeat the purpose of this?
Let me throw my hat in the ring - iPad Air 11.0.3 MDM Lost Mode Could Not Be Disabled on this device
We're running an environment with 300 iPad Air 32gb models.
No solution offered from JAMF? I'll be using DFU
We are seeing the same issue in our 1:1 environment. We don't use JSS to manage our iPads, we use Lightspeed MDM.
Lightspeed let us know that this an issue on Apple's end affecting multiple MDMs. Until Apple produces a solution, lost mode will not function properly on iPads that do not have biometric hardware (fingerprint scanner) and the only fix is a DFU reset for now.
I know I'm not offering a solution, but at least you know it's happening on multiple MDMs now.
Any idea if the new Jamf Pro 10 fixes this?
Can confirm Jamf Pro 10 DOES NOT resolve the issue nor does iOS 11.1.
I am also a LightSpeed user having the same issue. I can play the sound and view the map, but getting it out of lost mode does not work.
Devices are iPad mini 2s.
However, Apple seeded iOS 11.2 Beta 1 today. I updated an iPad, put it in Lost Mode, and then WAS able to get it out of lost mode! It will be interesting to see if others have the same result!
I updated an iPad Air to iOS 11.2 beta today like jrobinson2, and I was also able to get the iPad out of lost mode. Now if only I could upgrade the two that I am having lost mode problems with without wiping them...
So it's not until 11.2 when this is going to be fixed? Has 11.1 been released?
