Is anyone else seeing this with their jss? We allow all students/staff to update to iOS 11, I thought I tested everything, but we are seeing an issue with Lost Mode. I am able to enable Lost Mode, utilize all features (Play Sound, Update Location) however I am unable to disable Lost Mode through the jss. I am running the most current jss (9.101.0).
*I want to get it on the radar incase anyone else is having the same issue and a simple solution to prevent the iOS update till a solution is there (unless I'm missing something).
Error: "MDM Lost Mode could not be disabled on this device"
Current solution is DFU on the iPad.
iPads have no Apple IDs/ Using all device-based deployment.
Any sight helps, thanks all.
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?
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!
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.
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.
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.
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!
Now that 11.2 came out this weekend has anyone tried putting an iPad that was stuck in recovery mode and updating it to 11.2 via iTunes? I have it downloading now and can provide an update once finished. Just curious if anyone has tried that yet?
I just update about 10 different devices we have to 11.2 via over air updates and sent them all lost mode commands. I was then able to successfully remove them from lost mode without having to erase them. I also got no failed commands like we use to.
The devices this was tested on were: iPad Air (Gen1), iPad Air 2, iPad mini (4th gen), iPad 5th Gen, iPad Pro 10.5 and 12.5
Hopefully everyone sees these same results. One thing I want to test as well is if we enable lost mode on a device that is not on 11.2 and it goes through, then we send the command from the JSS to force the iOS update if that will go through and if it does then once that is finished can we then disable lost mode. That way we don't have to potentially erase a student device.
I plugged the iPad into my MacBook and then opened Apple Configurator 2 and updated it to iOS 11.2. I then sent out the command from the JSS to disable the lost mode. On the screen it said it had updated the position of the iPad and then I was able to get in. Glad to see that this is working again.
Interestingly, I just had this happen on an iPad Air 2 running 10.3.3. We are on JSS 9.101.3, hosted.
I was able to configure Apple Configurator 2 with Organization and Supervision Identity, so gained access to the logs.
biometrickitd <Error>: AssertMacros: err == 0 (value = 0x10000003), file: /BuildRoot/Library/Caches/com.apple.xbs/Sources/Mesa_NonUI/Mesa-424.18/AppleBiometricServices/biometrickitd/BiometricKitXPCServer.m, line: 2542 FindMyDeviceHelperXPCService <Error>: Error disabling TouchID: 268435459
This does sound like the biometric issue even though it is on a device with that capability. However upgrading to iOS 11.2.1 did NOT solve the problem. Submitting ticket to Apple Enterprise now.