Configurator 2 error - Pairing is prohibited by a policy on the device

Question

Level 1

36 points

Configurator 2 error - Pairing is prohibited by a policy on the device

Has anyone else run into this error in Configurator 2?

An unexpected error has occurred with these X iPads.

Pairing is prohibited by a policy on the device. [com.apple.configurator.MobileDeviceKit.amd.error – 0xFFFFFFFFE800009A (-402653030) [sys = 0x3A, sub = 0x0, code = 0x9A (154)]]

I've been wrestling with Configurator 2 and my library's 20 new iPad Air 2s for several days now. I thought I had my workflow figured out when I started getting this error while applying a blueprint that 1) restores (wipes) the iPads 2) adds apps via VPP and 3) restores my "master" backup. (I have a second blueprint to apply after the first that prepares, renames, sets the wallpaper, and adds profiles.)

When I check device info in AC2 after the blueprint process has ended, it doesn't show that any profiles are installed that would affect pairing. If I simply try to "Prepare" the device (not via a blueprint) to reset the organization info and allow pairing, I get the same error.

I even tried Actions > Advanced > Erase all content and settings prior to applying my blueprint.

I'm using a brand new MacBook Pro running El Capitan 10.11.1, and the iPads have updated to iOS 9.2. The iPads have only ever been connected to this machine. In earlier test runs I had disallowed pairing with other devices figuring they only ever needed to pair with my MacBook, but now a complete wipe doesn't seem to remove this setting!

Any suggestions?

Configurator 2.1-OTHER

Posted on Dec 9, 2015 11:22 AM

Reply

Answer 1

Jan 17, 2016 12:04 PM in response to rccharles

i'm curious, as we suddenly started receiving this with configurator 1.7.2. No changes to configurator, and the iPads we are adding are straight out of the box brand new. If we restore them manually, they (usually) go through. I called tech support and they had no answers. Are you saying this is a known issue that calling them should sort it?

WHen end I look in the logs, I see the Bluetooth pairing errors, but BT is disabled on our Mac mini, and as I stated, the devices are not even on and are brand new.

Reply

Answer 2

Jan 23, 2016 10:30 AM in response to APL_Anderson

I see the reply to call support but I would ask that if you get an answer please post it here as well. This will make your solution searchable on the inter-webs. This error started for me when I attached new iPads to my previously smooth running Configurator. 1.7.3 and it happened in my failed attempt to upgrade to Configurator 2 during a supervision test. Thankfully I did not convert all my licenses to Managed and was able to go back to 1.7.3 but others may not be so lucky. I am still struggling with this error in 1.7.3 and it is causing a 15 to 30% failure rate during reset and happens on different iPads each test which is wildly unacceptable.

Reply

Answer 3

Jan 29, 2016 9:00 PM in response to stllibrary

After my last post, I double-checked the Bluetooth on one of the Mac mini's (running Configurator), and found that some recent OS update has re-enabled Bluetooth. >:-/ I've turned it off (again!), and am hoping that It helps. Regardless, i'm hoping we move to MDM before we reach end of life for Configurator 1, which I fear will come quickly.

Reply

Answer 4

rccharles

Level 6

13,037 points

Dec 9, 2015 1:12 PM in response to APL_Anderson

Education Customers
Support: 1-800-800-2775
Sales: 1-800-780-5009

R

Reply

Answer 5

Sep 26, 2017 7:12 AM in response to Vanillabn

I had this same issue this morning when trying to use my JAMF server. The only was to resolve the issue was doing the manual restore/update via iTunes. After that I was able to configure using JAMF.

Reply