MCCloudConfigErrorDomain – 0x80EF (33007)

[snagrat]

I am trying to add multiple iPad Air 2 to ASM but get the error "MCCloudConfigErrorDomain – 0x80EF (33007)"

 

Nothing seems to work. Have tried several suggestions on the internet around partially completing the wizard before trying to prepare. All result in the same error.

 

Mac and AC2 are now both fully up to date. On home WiFi with no firewall or filter.

 

Any suggestion on what to try?

[Steve21]

Had that same error previously occur for a number of issues so don't think it's one specific items sadfully

I assume if you're doing this at home you've done things like add the WIFI profile for your home network (or joined the wifi network on the apple iPad on the welcome screen prior to running past that stage?)

Ensure you've got "Activate and Complete Enrollment" unchecked, we found some MDMs you need to manually assign it via ASM first to the MDM now and if you have that checked it'll fail as it can't find it yet (Also make sure no enrollment URLs in the blueprint have been changed as nowadays most seem outdated so easier just to do that via the DEP manual settings in ASM)

Would also be worth checking whether they're new enough (OS cap wise) to do it via the iPhone version of Configurator as that seems to work better for newer models too

Steve

[snagrat]

iPhone - no - they are 15.8.4.

 

WiFi is set to my home. It connects fine automatically if I go through the wizard.

 

Used to have this error before and adding to WiFi manually was a fix, but that just doesn't cut it anymore.

[synaesthesia]

Air 2s I believe are too old. I think you can force them to play ball if you want to faff with an older version of Configurator but I found out the hard way it was just down to age and ended up chucking the devices  (Had exactly the same problem)

[lparry]

6 minutes ago, synaesthesia said:

Air 2s I believe are too old. I think you can force them to play ball if you want to faff with an older version of Configurator but I found out the hard way it was just down to age and ended up chucking the devices  (Had exactly the same problem)

Exactly this - I had a big back and forth with Apple sending logs and all different sorts of hoop jumping.. save your sanity and just give up on them now.

 

My last response from apple:

Quote

Hi Lewis,   I have had an update, but again not definitive. I'm starting to think this may not be resolved as it's been ongoing for 4/5 months now.   In any case, I will continue to monitor the case and the engineer who was in touch with me to promised to keep me in the loop.   Your case number is: X.   If you have any questions, please let me know. I’ll be happy to help. Please mention your case number in any correspondence.   Kind regards,   X Apple Inc.