Currently Being ModeratedOct 17, 2012 6:04 AM (in response to jasstbenson)
Are you supervising and restoring a backup with ios 5.x? Your best bet is to update everything to 6 , including apps, on one and update the rest to 6 and restore from this backup. Not sure about any apps or docs the students have added because I do not know what your policy is.
Currently Being ModeratedOct 17, 2012 6:45 AM (in response to gyrhead)
So, in Configurator, where it says iOS: 5.1.1 (Check for Update) we should go ahead and check for the iOS update and then it will let us check in the iPads that already have 6? We are planning to upgrade everyone at this refresh cycle. We are not restoring from a backup. That should allow us to check in everyone, won't it? Because if they have the older system, then it will install the newer iOS...
Currently Being ModeratedOct 18, 2012 10:11 AM (in response to jasstbenson)
Yes, that's right. Updating your configuration in Configurator for those checked out devices to specify iOS 6 (by clicking "Check for Update") should allow you to check in the devices. You can always try that experiment with a single device first.
Currently Being ModeratedOct 18, 2012 12:11 PM (in response to Todd Fernandez)
Thanks! We experimented and were successful. Hopefully not too many kids updated their iOS! But considering that Siri was the prize, I am not holding out much hope of compliance!
Currently Being ModeratedApr 2, 2013 2:54 PM (in response to jasstbenson)
I have the responsibility in our school district for developing and testing user procedures for managing iPads in the schools using Configurator. We have 600 iPads being managed by Configurator on 16 sites.
We cannot find a way of restricting users (students or teachers) from updating the iOS while using the iPad. Any mis-match of iOS version means most Configurator functionality will no longer work. Refreshing a backup, installing a new profile, and using the Assign Checkin/Checkout ALL require iOS congruence. This occurs not just with major version changes, but also with the near-weekly iOS patches within a version. "Device running newer version" errors occur with a mismatch between 6.1.2 and 6.1.3.
This causes a lot of frustration and overhead in maintaining a standard image on the iPads. At worst, students lose their work if they cant check the device back in.
Ideally, we would like to control the timing of version updates. Is there a prescribed way to do this?
Currently Being ModeratedApr 2, 2013 3:21 PM (in response to mackinaw213)
There is no way to prevent users from updating the ios or coordinating updates. Apple needs to lock down the settings. Until then we are herding cats and coyotes.
Currently Being ModeratedApr 2, 2013 3:50 PM (in response to gyrhead)
Thanks - that was as I suspected.
I'll submit a bug report to Apple on this one.
Currently Being ModeratedApr 2, 2013 4:06 PM (in response to mackinaw213)
currenty all you can do is try and block apples update servers
not much use though if devices leave the network