For some odd reason during the PBA session of PARCC we always seemed to have 1 or 2 Chromebooks in a class of 30 that would just hang on the "loading" screen right after the student types in their seal code.   We fixed by swapping out their Chromebook with another which seemed to fix the issue.   We are wondering if anyone else was experiencing this and if they found a way to fix this annoying issue.   During the last day of testing we set one of the sections to not use our internal Proctor Cache server and we seemed to get better results, but not sure if this will fix for all occurrences moving forward.   We had to turn off "Load Balancing" on our access points during infrastructure trials to get more than 10 devices on at a time.  We are wondering if we need to tweak our wireless further to get better results. 

We had similar issues and found that if we turned the chromebook off and then back on again (and the proctor resumed the test) all was fine.  We did not use proctor caching and the entire process went relatively smoothly, especially considering our fears coming into it.

We had a few similar issues- strangely after the CB's were working fine for two weeks.  We were also able to resolve the issue by resetting just the few that it happened to.