DEP issue - configuration could not be downloaded, "cancelled"?

Good Morning Dan,

I am not sure it is the same issue, and you may have already tried it, but we had a lot of iPad minis display a similar message lately. We were able to remedy this issue with a software restore from iTunes. To be honest, I am not sure what the disconnect with the server was or what the restore cleared from the system, but I do know that it worked for us.

Good luck and I hope this helps you!

Chad Krape
Technology Department
Jersey Shore Area School District

Yes I've tried the restore from iTunes method - holding down Home and Power to put it in recovery mode while connected to a Mac. It restored fine but then when the DEP kicks in during the setup process we get the "cancelled" error again. Unassigning the devices in Apple School Manager does allow us to get in, but then we can't enrol them to the JSS as non-DEP devices require that MDM profiles have to be removable, which we don't want.

Could it be that our Jamf Pro installation needs to be on the latest version in order to successfully manage iOS 13 devices?

I've tried to upgrade to 10.15.1 with no success as we are facing the same issue as you. Devices with iOS 13+ will not enroll and the ones already enrolled stop communicating with Jamf. Luckily we pushed out the profile to defer updates for 90 days but a few managed to update before we realized it was a problem. Currently talking with support over it.

We just updated to 15.1 and have the same issue with iOS 13. In MacOS 15, Self-Service and policies still don't work either.

Interesting. The pre-built cert from the primary server is automatically added to the prestage. We also have 3 JSS servers behind a load-balancer for device communication. The primary just handles APN communication. Does iOS 13/macOS 15 also need the the load-balancer cert added now? That wasn't the case before.

We are still working with Jamf over this issue. We actually have the same setup as lehmanp00 and are running into the same thing. It is strange, like lehmanp00 said, that the SSL cert would be needed in prestage as we never needed that before with the built in certs. I'll give that a try on our test prestage and see what happens.

We're using a 3rd party SSL certificate for our JSS rather than the built in certificates, if that makes a difference.

https://support.apple.com/en-us/HT210176

So iOS 13 and MacOS 15 need new/extra attributes in your keys. So we need to generate a new cert, from our JSS system, to the load balancer with the new requirements.

My Network Manager and I are guessing Apple and JAMF are assuming most customers are using a 3rd-party cert, not the built-in certs, and didn't need to worry about this.

Got this figured out. We had to take the keystorepass from the tomcatconf folder and use the keytool in Java to separate the files into the cert.pem and key.pem. Once that was done we uploaded them to our load balancer.

@DanJ_LRSFC

We have the Same Problem with Profile Manager. How did you add the new cert into the PreStage Enrolments settings?

Having same issue. Was able to use Apple Configurator and enroll a device a few short months ago. Now I keep getting "The configuration for your iPhone could not be downloaded...cancelled". Need help.

reyagarcia88 , Same issue yesterday across multiple schools and accounts. found the server url was slightly different in the AC2 blueprint than that displayed in JAMF under enrol new devices. Rewrote the "prepare" steps in each blueprint with a "new" server... all was good.

I set up a new Blueprint with the server I see on Jamf and get the same error.

Can someone check

Anyone found a working solution to this hell?

I only experience it on my iPads.

Hi,
Have you checked your DEP server token if hasn't expired? If so then the server token needs to be renewed from ASM. Hopefully that helps.

Have you checked if the DEP server token is not expired? If expired then it needs to be renewed from ASM. Hopefully that helps.

This post saved my sanity. Thanks 

Was this for on-prem Jamf Pro? We're having the same issue after migrating to Jamf Cloud, but Jamf said to leave the anchor certificate empty.