The Go-Box Chrome automatically initiates the active script (Credentials + Template files) immediately upon the USB cable being plugged into the Chromebook. All configurations are maintained even on power down.
Each USB port runs the script independently of the others to ensure each Chromebook completes the script in the shortest time possible.
If your script doesn’t run as expected the first time, don’t worry! It takes a little practice to get it just right.
Here are some tips:
- Use an iterative process to remedy any script issues.
- Script consistency is more important than script speed.
- Mouse commands can be harder to work with and should be used as a last resort.
- Timing issues are harder to recognize, but it’s a good rule of thumb to add a short WAIT delay when a dialog window is appearing, or if you can see the Chromebook pausing for a screen to load.
- In mixed Chromebook environments (either OS version, model or both) – it will save you time and frustration to organize your inventory into common groups before beginning. Tools like Chrome Gopher can be helpful.
- If your Chromebooks are requiring OS updates, consider staging your process with two Templates (or two Go-Box Chrome units) – one that brings the Chromebooks to the downloading stage, and the next to take them the rest of the way.
- Experiment with your scripts and get creative! You can automate a lot more than just White Glove provisioning and force-wipes.
Contact the Go-Box Team with questions or any technical support needs: