Select a Template File
Before working with any template, Identify the Chrome OS version
Note: Press “alt+v” at the welcome screen on a Chromebook displays the Chrome OS version
Our templates should work for most environments, but in some cases edits to a template may be required to run smooth and efficiently. Test the template by connecting a single Chromebook to the Go-Box unit with the Logging utility active. See “View the Logging Utility” for instructions on this tool)
If your script does not run as expected the first time you may need to make edits to your Template.
Edit a Template File
- The Error Check function will find most common input errors, but save time
by observing and maintaining the format provided in the demo Template files.
- Syntax is important and commands / arguments are case sensitive
- If you introduced custom variables in your Credential file that you want to call in the Template, those will need to be declared on Line 1 with the others shown by default. Separate with a comma and no space.
- Some keystrokes are hard coded and cannot be received by the Chromebook. This includes the ESC + Refresh + Power and on some models, the first Enter press.
- Use an iterative process to remedy any script issues.
- Script consistency is more important than script speed.
- The most common errors where a script goes somewhere it should not are fixed by increasing WAIT times within the template, particularly around the Wi-Fi connection and Terms and Conditions screens. This is identified by watching the logging utility to see if the Chromebook is not ready when commands start being sent after a WAIT command.
- 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. All sample templates include “HIT ctrl alt e” (to skip the OS update). Remove “HIT ctrl alt e” from the template to allow OS updates.
- Experiment with your scripts and get creative! You can automate a lot more than just White Glove provisioning and force-wipes.
List of Accepted Commands for Templates:
*Note that while mouse actions are supported, keyboard commands are always more consistent. When using move and drag commands the positive x axis is 0 to 63, negative x axis is 64 to 127, positive y axis is 64 to 127, and negative y axis is 0 to 63.