Apple Configurator / iTunes unable to restore iPhone 4s after update, Apple Configurator / iTunes unable to restore iPhone 4s after update

Question

Apple Configurator will not restore any iPhone 4S after the latest update (ERROR: Unable to prepare)and iTunes gives the error 3194.  But all usual 3194 fixes don't work and this happens exclusively on the 4S.
Tested on 15 different iPhone 4S's
Using 4 Mac Minis and 8 different Windows 7 machines.
Hosts files have not been altered.
Latest version of iTunes / Configurator on all.
Both have been removed and reinstalled.
No dice.

Answer 1

Ok, well after two days of recieving nothing but the usual generic template response from the "support team" the only thing i was sure of was that my original message had not been read at all.
I was able to fix the issue myself though, so i'll leave this here in case someone else is unfortunate enough to have the same issue:
It appears for whatever reason Apple Configurator removed the previous versions of iOS itself before attempting to download iOS 7, the only conclusion i could draw was that for whatever reason the download failed and i was left without a firmware file both the iPhone 4S and the iPhone 5.  Older handsets were unaffected. 
To fix this, simply download the firmware from http://www.ipswdownloader.com/
Then (if you're on a Mac) navigate to: Library/Containers/com.apple.configurator/Data/Library/Caches/com.apple.configu rator/Firmware and copy the new .ipsw into that folder.
Restart configurator and you will be good to go.
Porbably worth mentioning I spoke to my colleages in the US and they we're having the exact same issue ever since last weeks Configurator upgrade so why the support team are still sending templates out asking users to go on a wild goose chase with things like "Are you SURE you have the latest version of "XYZ" are you SURE you have rebooted the machine, are you SURE blah blah blah"
YES.  I'm sure.  I know what i'm talking about, I work in the industry and this is not another generic fault and you do not have a fix published yet.
How about listening to what the users are ACTUALLY saying before emailing this rubbish out?
/Rant.