Jelly Bean OTA fails on Galaxy Nexus, how to fix? The company I am working for has hundreds of Galaxy Nexus handsets which are used as the standard operating platform of a company specific app. The app is not important.

We have found that about 70% of the devices fail to install the standard OTA Jelly Beans update. We are running completely stock OS (4.0.4 ICS) and the devices are not rooted.

My questions are:


Why does the OTA fail for completely standard builds? Factory reset makes no difference.
How can I get some idea as to why the OTA fails?
Where does Google provide support for this situation?
Can I disable the OTA updates? We are getting very frustrated with the regular interruptions to normal service when the OTA notification pops up no matter what the user is doing.
Is there a Google web site that describes how to do the OS update manually? Perhaps we can manually handle the hundreds of handsets, costing us thousands of dollars in labour costs?


I have reported this to the code.google.com Android issues list, no response from that.

I tried to post a notice on Android Developers but the moderation process there seems to take four or more days, perhaps never.

This must be happening tothousands of non-developer users of the Galaxy Nexus, they can not be expected to hack their way around it. Where is the Google fix (or does Google simply not care?).
Try the old trick of doing this, from ICS, tap on Settings > Apps, tap on the tab called 'All', look for 'Google Services Framework', then tap on 'Clear Data', you may need to do this a few times and restart the handset. 

This is known to work with the Galaxy Nexus line of handsets.