J-R

Strangely enough, applying apps seems to work absolutely fine for me now. It doesn't matter if it's on wifi, or plugged in with a network cable, or itunes signed in etc. it just seems to work how it's supposed to work. I haven't changed any configuration on any of the mac's, it just started working by itself. I wonder if Apple has pushed out an update, or changed something on their app store servers etc.

Thanks for your help I logged into itunes as suggested, and authorised the computer, however I've come across a strange result. After logging into itunes I tried applying the blueprint again and it didn't work (same error message). I then tried a further 4 times, didn't work. On the sixth attempt it actually worked fine and deployed the apps correctly. I then wiped the ipads and tried applying the blueprint a seventh time, where it failed with the same error message as above. During my testing, it appears that every now and again it works (maybe something like 1 out of every 20 attempts). It just seems that Apple Configurator 2 is extremely buggy. There doesn't appear to be any differences in my setup between when it works and when it doesn't work - it appears to be completely random. There's a thread on the Apple Developer forum which might be worthwhile following if anyone has the same issue: https://forums.developer.apple.com/thread/21638 Thanks very much

Hi all, We've recently tried setting up new ipads using Configurator 2, however, we have an issue when trying to add apps to the ipads. When applying the blueprint to the ipads, during the "app download" stage, we receive the following error message: An unexpected error has occurred with these 2 iPads. An underlying service (ACUInternetServiceContext) unexpectedly quit. ConfigurationUtilityKit.error - 0x68 (104) We've tried this at a secondary school, and at a primary school, and get the same error message. Both schools are completely separate networks- different ipads, different mac mini, different vpp account etc. Has anyone else encountered the same or similar error? I'll try contacting Apple and see if there's any resolution, and will update this thread if I find anything. Thanks very much!