Happened to us too - we were running 10.2.2 in the cloud and the issue persists after they upgraded us to 10.3.0-t1521825567. Apparently the JSS is still trying to send the update but the iPads won't take it because they don't need it.
iOS 11.2.2 to 11.3 - It seems that in some cases it starts the update but communication is severed prior to completion - it can no longer communicate with the ipad so it doesn't "know" that it doesn't need so it keeps trying and everything else just lines up behind it. We are on Jamf cloud so we are borked until they fix it in Jamfland.
We are seeing the same thing. Wiping and re-enrolling the device causes it to work fine afterwards. Existing devices that update to 11.3 have mostly stopped communicating--- we have 6 still checking in and around 6500 not checking in. We just had the server updated to 11.3 from 9.101 Thursday.
Jamf is investigating an issue related to the MDM Software Update workflow on iOS 11.3. While we don't have all of the details just yet, I want to share what we know for transparency:
MDM Software Updates are composes of three distinct steps:
1. Send an 'AvailableOSUpdates' command to determine what is available for a device
2. Send a 'ScheduleOSUpdate' command to tell the device what to install
3. Send an 'OSUpdateStatus' command to monitor download/installation status and completion
The response for 'OSUpdateStatus' includes a key for 'IsDownloaded', which should return a boolean True/False. We are investigating an issue where the 'OSUpdateStatus' is returning a '0' instead of a boolean True/False. This is causing a failure and affecting subsequent MDM communication. We have filed Radar 39116010 with Apple regarding this response change and our teams are investigating ways that we can handle these scenarios if the response does not conform to the documented standards.
"We filed a radar."
What I want to see is, "We will meet to improve our QA process to avoid scenarios like this in the future."
This is a major bug. Yes, due to a change (maybe undocumented) Apple made. Jamf still did not do their due diligence in testing. Hire me to do QA. I'll press all the buttons before shipping a release.
@hyprmatt The issue happens when you push the 11.3 iOS update from Jamf - the update completes on the device but the JSS thinks it is still in process so all new management commands get stuck behind whatever the JSS is still chewing on. As long as you don't push the iOS update until they get the issue sorted you should be fine no matter what version of Jamf you are on.
I get mistakes happen, whether it's jamf or apple, but I don't understand why Jamf would not send an email by now to all customers saying to hold off on 11.3 to lessen the potential blow (not that customers shouldn't test pushing the update in dev, and/or in test group in production, too).
We're on Jamf Pro 10.2.2 and seeing this issue occur on devices all the way down to iOS 9.3.5 but not all of the devices. The reset on each iPad re-enrolls the device and gets the 3rd Party apps back. I have a support call in about 10 minutes hopefully we'll learn a little more.
@FastGM3 The issue exists for devices that get upgraded to iOS 11.3, regardless of Jamf Pro version or previous iOS version. Once the iOS device is upgraded, Jamf Pro attempts to validate that the upgrade is complete. This is the step that is failing.
I havent issued the iOS update commands from the JSS. All of my ipads are on 11.2.5 and commands either take forever to actually apply on the ipad, (Erase device has taken upwards of 45 minutes after consistently sending blank pushes) or they dont take at all. As far as i know this has only started happening since yesterday when our Jamf Cloud instance was upgraded to 10.3. I have checked with out networking team as well and have looked through the firewall logs and nothing is being blocked or has changed.
@FastGM3 When you send the MDM Software Update command to upgrade to iOS 11.3, the device should go through the upgrade properly and the device should be usable by end users. The 'OSUpdateStatus' command that I outlined above is then designed to verify the upgrade is complete. Because that command fails on iOS 11.3, it prevents any subsequent commands from completing successfully. That includes update inventory, which would update your reported iOS version. That's why no devices are reporting their successful upgrade to iOS 11.3. With the upcoming maintenance release, that failed response will be accepted and devices will resume normal behavior as managed devices.
In the same boat...... Doing support with Jamf, they recommended upgrading to JSS 10.5: issue persist. Can't even do an OTA update on the iPad itself, it fails. Never even downloads the iOS, message shows on the iPads the update request failed. I've had to connect iPads to a computer and do the update to iOS 11.4. That seems to fix the issue and all works as expected after the iPads are updated to 11.4. Now I have to locate and do this for my 1600 out of 2200 devices having issues........