Our organization recently moved over to Jamf Cloud from on-prem hosting. Trying to provision five iPads for a department. Stuck on awaiting final configuration from "our organization" loop. Has anyone experienced this before and if so how did you resolve it? I've already unassigned and reassigned the devices to our MDM in ASM and then wiped the devices in Apple Configurator. Left the iPads running overnight and it was still stuck on awaiting final configuration from "our organization". We had no issues with mobile devices with on-prem hosting.
We too have been seeing this the last couple weeks. Our workaround has been to delete the device from JAMF and then restore the device in iTunes. After doing that process, we plug them into Ethernet to complete the setup. Luckily it's not widespread, but definitely adds to the setup process. Hope that helps some people!
I started seeing this yesterday, too. Had a client who checked out 4 iPads. One worked fine, but the other three were repeatedly stuck on the "Final Configuration" step. We didn't have Time Zone set, but we did have "Install Configuration Profiles before Setup Assistant." Turning that off and sending the devices a wipe seems to have resolved it.
Our clients now have to set a passcode during set-up, and then have to set a new passcode a bit later when our passcode policy hits it, which is irritating, but at least it works.
When this happens is it stuck installing a WIFI profile? This happens with our iPads too from time to time and it is always when trying to install a WIFI profile. I cancel the install of the WIFI profile and the rest of the install proceeds. I then push the cancelled profile to the iPad.
Check your firewall rules. Apple has changed the end points and silently updated the article. Loads of end points are now on Akamai and not on the 17/8 IP range. See https://support.apple.com/en-us/HT210060
You can download service test app, that will check your firewall rules from your network against JAMF and Apple.
Going to Jamf Settings > Global Management > Push Certificates > MDM Push Notification Certificate and changing the push protocol from Binary to HTTP/2 as well as toggling off the "Install Configuration Profiles before Setup Assistant" option in our prestage settings seems to have resolved our issue.
I was originally seeing this issue back in November 2020 and after trying all of these proposed fixes, I still have 3 iPads that absolutely refuse to move past this error. Of my leftover stockpile of 20 devices I run tests on, 17 always succeed no matter what I throw at them and 3 always fail. Unchecking the install config profile allows them in and then they get hit by the inventory update issue and never process commands. I will reopen my case and mention the above product issue.
I noticed also that when trying to reset the iPad in configurator, the 3 failing devices always stay hung up on the awaiting final configuration step there as well.
Im a little confused about this. I am experiencing this with several iPads, however some things that you all are saying make no sense to me. If the iPad is awaiting configuration it is not fully in Jamf yet? How can you send a blank push or update inventory if the iPad is unmanaged? I don't understand, we are experiencing this on more and more devices. If i uncheck the install config files before set up assistant the iPad doesn't even go into Jamf. I have turned in a help ticket with Jamf, but haven't heard anything back.
@christina_luis If you search for the affected devices you'll see that you are able to send commands, and they do receive them. At least that's been our experience. It's more that Jamf hasn't fully configured these devices than them not being in Jamf at that point.
We too had this problem happen with a brand new iPhone. I had manually added it to DEP with Apples Configurator, so I figured I had done something wrong. But removing the "Set Time Zone" option in Prestage Enrollment for Mobile Devices in JAMF, did the trick. Just like @jphillips experienced, this was the key to moving on from "Awaiting configuration"...
unfortunately the time zone suggestion does not work here as we have never had it checked. I received 3 brand new iPads from apple that all went through the basic setup flawlessly. Now that I am trying to use them with iCloud backups, they are having the exact same issue as all the others.
I had the same problem, however, when I searched for the display name it was gone. So I search for the serial number and found it, however, the display name was reset. Therefore, I changed it back to the display name that I originally gave it and the iOS update was completed and all the apps that I had assigned to this device were reinstalled.
I found a solution that worked for my devices, hoping it works for others as well. I first unscoped the iPad from its prestage enrollment. I unassigned the iPad from my Apple School manager instance, then I deleted the iPad from Jamf. After that I did a DFU restore and after it completed, I set it up as a generic non managed iPad. Then I went through and reassigned it in school manager, added it back to the prestage, then reset the iPad and went through the enrollment process. Worked first time every time.
Ouch @Tolandese That is hardly a solution for a lot of devices, but good score if it works for you. After schooling through I had hoped that I would be finding some hope, rather than an issue without a clear solution for half a year. I was able to do a hard restart and that got all but one of my iPad through. I tried just removing it from Jamf and putting it through PreStage, no dice, then DFU didn't even work for me. Just one iPad is preventing me from calling our summer iPad refresh "DONE".
Was told this week it is PI-009362 causing the issue and is a planned fix in an upcoming release.
By Chance did anyone receive a functional fix? I still see this pop up, such as today where i cycled through 10 devices repeatedly until one decided to complete.
Our situation was caused by a certificate trust not being set for a WPA2 Enterprise Wi-Fi (PEAP)
Had this problem today. I had an ipad that was not in DEP. I added it using apple configurator method, and then assigned to jss. Now comes up with "managed by MYSITE" but cant proceed through the above error. Whiped the ipad many times, removed from jamf completely.... Since it is just inducted into apple school manager i didnt remove it from there. Dont have any timezone set.
I did have set "assign profile before setup assistant" on the prestage "newly assigned devices" and unchecked it. The ipad now works. But we have literally had that set forever with no issue. Would appreciate a better explanation of why this was necessary from JAMF if they are monitoring these forums.
EDIT: spoke too soon. Gets by that error but then never downloads policy. Update inventory command just hangs. tried hotspot as well to rule out network issues. sigh...
EDIT2: the root cause of this issue was that our push certificate expired (LOL) so check the obvious things first!!! lesson learned. I have restored the "assign profile" setting, as i thought that might not be the issue... The ipad is now recieving settings and policy.
Good morning,
In case you are using JAMFSchool, I was getting this issue with 14.X and 15.X devices. If you log on to the admin console, go to devices --> Inventory. Find the device you are having the issue with and select it. On right, under device details, click on refresh. That worked for me getting past the configuration loop.
I wish I had more to add to this discussion but I wanted to leave a note here for others like me finding this in the future. We did not have install profiles before setup assistant enabled but we did have the set time zone setting enabled. After unchecking the time zone settings it appears to be working as intended. Our iPads are currently on iOS 16.5 so it doesn't appear to have been fixed on JAMF or Apple's ends.
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.