InterwebsGuy Posted April 4, 2014 Posted April 4, 2014 We are trying to supervise a bunch of iPads using Apple Configurator (1.5), however we keep having devices randomly fail to restore/refresh. It appears as AC is trying to refresh a device, it gets to the 'Checking Supervision' stage and then fails with the 'Unable to send ProceedWithKeybagMigration command to device' error message. I've Googled this and I'm unable to find anything of help. After a device fails with this error message, if you attempt to refresh it again it may well complete successfully. I'm wondering if anyone here has come across this error and how/if you resolved it. Cheers
Brimstone Posted April 7, 2014 Posted April 7, 2014 We are trying to supervise a bunch of iPads using Apple Configurator (1.5), however we keep having devices randomly fail to restore/refresh. It appears as AC is trying to refresh a device, it gets to the 'Checking Supervision' stage and then fails with the 'Unable to send ProceedWithKeybagMigration command to device' error message. I've Googled this and I'm unable to find anything of help. After a device fails with this error message, if you attempt to refresh it again it may well complete successfully. I'm wondering if anyone here has come across this error and how/if you resolved it. Cheers I would check to ensure you are running the latest version of iTunes, Configurator and iOS it's likely that a command sent via your keychain has failed 1
InterwebsGuy Posted April 8, 2014 Author Posted April 8, 2014 I would check to ensure you are running the latest version of iTunes, Configurator and iOS it's likely that a command sent via your keychain has failed Sorry, I did forget to add everything is up to date. I'm puzzled by this error!
EL_S Posted April 10, 2014 Posted April 10, 2014 I've just had the same problem and I think it was the fact that the iPads were new and the date/time and time zone were set wrong. Changed that and it started working. 1
InterwebsGuy Posted April 10, 2014 Author Posted April 10, 2014 I've just had the same problem and I think it was the fact that the iPads were new and the date/time and time zone were set wrong. Changed that and it started working. Interesting. That's worth investigating, cheers, I'll take a look.
Arcticomp Posted April 30, 2014 Posted April 30, 2014 Try resetting the Network Settings on the device that's reporting the error. 1
gsk Posted April 30, 2014 Posted April 30, 2014 Are you restoring a backup? I found with this error that by preparing and supervising the device first and then restoring the backup it would work fine. Cheers, 1
InterwebsGuy Posted May 7, 2014 Author Posted May 7, 2014 Try resetting the Network Settings on the device that's reporting the error. This was one of the first things we tried, followed by unsupervising the iPad then erasing all content and reseting the iPad (just for good measure). Sadly it doesn't solve it.
InterwebsGuy Posted May 7, 2014 Author Posted May 7, 2014 Are you restoring a backup? I found with this error that by preparing and supervising the device first and then restoring the backup it would work fine. Cheers, Yes, we are. We do it the way you describe, as standard practice, supervise the devices first, then restore a backup afterwards. Each time the iPads go back into their trolley, AC resets and restores the backup to them - this tends to be when this error message randomly pops up. Hitting the refresh button on AC will successfully restore the backup to the device that just had the error, which to me, is the strange part.
InterwebsGuy Posted May 7, 2014 Author Posted May 7, 2014 Just to add to this thread, we wiped the Mbp that hosts our AC instance, and started over again with everything. All iPads were unsupervised before changing the Mbp's hard disk, and all iPads fully reset for good measure before starting a fresh with it all. This error message still randomly pops up on different devices, though I would say it seems less frequent than before. I really cannot fathom why this is happening, to the point I'm considering trying to open some kind of support call with Apple about it now.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now