This page provides a guide to planning the deployment and on-going management of Chromebooks in a school. It is intended for people that are leading the deployment process.
Chromebooks are designed to be used with G Suite (previously known as Google Apps for Education – GAFE) and may be used as 1:1 devices or as class sets which are shared between classes.
Chromebooks can be managed using the Google Admin Console . This console has been designed to allow teachers to manage many Chromebooks at once so that students get a consistent and learner-friendly experience.
As well as the technical aspects of deploying and managing Chromebooks, this page includes suggestions on how to involve your school community, supporting teachers and learners, purchasing, and using the Chromebooks at home.
Before you start, ensure your Chromebook deployment fits in with your school’s vision for learning. Your Chromebook deployment should be just one part of a well-thought out plan for improving learning at your school.
Use the e-Learning planning framework and Strategic thinking roadmap to assist you with your strategic plans. Ensure your annual and three or five year plans reflect the relative difficulty of changing technology and changing how teachers teach and students learn.
Give teachers, learners, parents, and whanau the opportunity to contribute toward the success of your Chromebook deployment. Involve stakeholders at all stages of the project. Ensure that consultation takes place before key decisions are made and that regular feedback occurs.
If caregivers are expected to contribute toward the cost of the Chromebooks, ensure that the rationale of your decision is communicated clearly. Schools cannot compel parents to buy Chromebooks, as outlined in Ministry Circular 2018/01 , so plan on having some school-owned devices for students to use.
Teachers and learners will respond best to a Chromebook deployment if they are well prepared and have appropriate expectations:
Well-supported teachers and learners will make your Chromebook project successful. Things to consider include:
Plan ahead to ensure lessons proceed as intended even if a Chromebook is not available (lost, left at home, damaged, or being repaired):
Provide ongoing support:
Do a "hands-on" evaluation of the various models of Chromebook that you are considering purchasing. Ask a vendor or another school if they will loan you a Chromebook for a few days.
Check the: build quality, performance, screen size, keyboard, weight, and battery life. Involve both teachers and learners in your evaluation. Use the 2018 Chromebook Comparison chart to compare the different models of Chromebook.
New Zealand Schools are eligible to join the All of Government (AoG) purchasing scheme. Suppliers to AoG are contractually obliged to ensure that their products are not available at a cheaper price through any other channel. Currently, this approach offers approximately 13% saving on bulk purchasing of computers. If the Chromebook package you want is not available in AoG, it may be worth arranging a bulk purchase with other schools.
The usual manufacturer’s warranty for a Chromebook is one year. If you pay a little extra to increase this up to three years, the Chromebook remains useable for an extended period. Factor in the cost of a bag for each Chromebook, a storage cupboard, and a few extra charging units to complete your budget.
Most school insurance policies will have a claim excess that is larger than the cost of a single Chromebook. Device insurance can be obtained with a low claim excess, and your school may find this useful. You will need a protocol for handling warranty and insurance claims.
Even if all your students have their own Chromebook, and are expected to look after it themselves, you will need to think of ways to ensure the Chromebooks are safe during, for example, PE.
School-owned Chromebooks will need a safe-storage cabinet or box. Pre-made storage boxes and DIY solutions are available.
The ability to control, administer, and set policies on Chromebooks greatly reduces the amount of effort to make them a manageable device. Chromebooks are managed using the Google Admin Console.
In order to manage the Devices themselves, the school will need to deploy a Chrome Education Licence for each device. Since November 2018 the Ministry of Education has funded Chrome Education Licenses for school-owned and BYOD Chromebooks. See the Google software for schools page for more information.
A one-off license may be obtained for each Chromebook that you wish to manage. The license is specific to the model of Chromebook purchased, but not to the actual device itself.
While Chromebooks are very useable without purchasing the Chrome Education License, you will find that the reduction in the amount of time and effort required to manage the devices makes the small additional cost of the license very worthwhile.
Chromebooks are supported by Google (updates and so on) for at least five years from the date of introduction.
Use this guide alongside Google’s excellent Chrome Device Deployment Guide and Networking Best Practices for Large Deployments guide. The latter document is more relevant to large schools and is quite technical.
Chromebooks are wireless-only devices and require a robust wireless network and good internet connectivity.
Your school’s wireless network should be at a standard similar to the Wireless School’s Network Upgrade Project (WSNUP).
Ensure you have a robust wireless network with enough IP addresses. Provide three IP addresses per person at school. Google’s own advice on Enterprise networking for Chrome devices has further recommendations on WiFi settings, bandwidth and access points.
Chromebooks require unrestricted access to Google’s servers. If your school’s firewall is a N4L router, then the required firewall settings should be in place already. If you have your own firewall instead of, or in addition to, the N4L router, then the firewall ports to the destinations in the Networking Best Practices for Large Deployments guide will need to be opened.
Your internet filtering may need also need adjusting. If you use N4L internet filtering, the required filtering policies that allow access to Google’s servers should be in place already. Otherwise, you will need to create a filter that allows direct access to *.google.com, and this list of ports/domains .
Individual Chromebooks will need labelling in some way so that they can be identified easily. Asset labels or barcodes are a good idea. If your Chromebook cases/bags are identical, a good Technology project is to design and make a personalised bag tag/identifier.
Charge the batteries every day even though Chromebooks have a long battery-life. School-owned Chromebooks should be placed on-charge every night.
If the Chromebooks are taken home, set an expectation that the Chromebook will arrive at school fully-charged. Even so, a few strategically placed Chromebook chargers will be a good investment and ensure that work can continue throughout the day.
The management features that the Chrome Admin Console offers are updated continually by Google. Rather than trying to reproduce Google’s information, this section offers useful pointers to the documentation and outlines settings that have proved particularly useful. Most of the information below is available from Google’s Manage Chrome Devices site.
Adjust your Google Apps for Education Domain to best manage your Chromebooks. For example, you may wish different year groups to have different sets of Chrome Apps on their Chromebooks or want teachers to have the ability to control the apps of their own class.
Both of these cases require users in your G Suite domain to be organised into organisational units (OUs). Common ways to organise G Suite users include: year groups; class groups; teachers; non-teachers. OUs can have sub-OUs and Chromebook policies can be inherited from their parent OUs. Your G Suite user OUs can be set up to give you the control you wish. Create an OU and user to test your device and user policies.
Consider the needs of your students and staff and turn on appropriate accessibility settings so that they can be used when needed.
Chromebook network settings , including connecting to wireless networks are easy to configure.
Google Cloud Print (GCP) is the standard way that printing is managed on Chromebooks.
Use a desktop or laptop machine that is connected to the printers and is left on all the time (or will be on when Chromebook printing is needed). Install the Google Cloud Print Service Connector. The connector is available for both Windows and Linux, OSX (or any operating system that uses the Common Unix Printing System). This service allows the desktop or laptop to act as a printing proxy and share printers with Chromebooks. Manage the printing for your Chromebooks from the same machine that the Connector is installed on.
Some printers can be purchased "Cloud Print ready ". Consider this when you purchase a printer. A printer that has been set up for Cloud Print can be shared with specific users or groups. The sharing settings for the printer work similarly to the sharing in Google Drive.
Some third-party printing services augment GCP by enabling print-auditing, queue control and print quotas. Papercut is an example of one of these applications.
User policies are applied when a user who is a member of a particular organisational unit (OU) logs into a device or signs into the Chrome browser on another device (Windows, Apple, Linux, Android).
A comprehensive list of Chrome user policies is maintained by Google. User policies include items such as wireless network settings, automatically installing apps, pinning apps to the taskbar, which web pages open at start-up, and some printing settings. The Chrome Education License is not required to set User Policies.
Device policies are applied to the Chromebook, regardless of who is using the device. A list of device policies and how to set them is maintained by Google. A Chrome Device Management License is required to set device policies.
Read through the list of policies and consider how they may be useful to you. For example, devices can be deprovisioned from your G Suite domain, or disabled if they are lost or stolen. The “Disabled device return instructions” setting allows you to include a return address and contact phone number on the device boot screen.
Device settings can also be used to restrict who is able to log in to the Chromebook, alternatively the Chromebook can be set to “kiosk mode”. Some Google Cloud Print settings are also controlled by device policies.
Use the "Mobile devices" section of the Device Management panel with caution. This section enables management of the G Suite aspects of the device (Gmail and so on) of anyone who signs into your G Suite domain using a mobile device, even if the device is not owned by your school.
During the first month of your Chromebook deployment, be prepared to discover that your wireless network coverage or performance may require improving. Move or add Wireless Access Points to suit where your Chromebooks are being used. Encourage your teachers to have alternative lessons planned if using Chromebooks at a location or classroom that has yet to be confirmed as having good wireless performance.
Set aside time to support teachers and students during the first stages of a Chromebook deployment.
Something is certain to go not quite as intended during the first few months of a Chromebook deployment.
School students spend much more time at home than at school. Increase the educational impact of a Chromebook by having it available for use at home. This may be be particularly relevant if the Chromebook is considered a personal device for the exclusive use of the student.
With your stakeholders (school, students, parents) consider:
You may want to think about extending the filtering available through the N4L to students when they are away from the school site. This is possible, but not particularly easy and requires some technical skill. A proxy server, hosted at school, is configured to listen on a public IP address. The next-hop of the server should be the N4L gateway. The Chromebooks are configured to use the proxy server using the Admin Console. Split-horizon DNS is used to prevent the Chromebooks using proxy server when they are at school. Using this method, the Chromebooks will be forced to use the proxy server and the N4L when connecting to the internet when the they are outside (but not when inside) the school’s network.
It is also possible to set "Off Hours" policies so that policies that are set to be pertinent to a school setting, such as disabling logins from guests or outside of the school domain, can be relaxed outside of school hours.
Join these groups to participate in discussions with other teachers/educators about the content here, or that is relevant for you.
Subscribe to the newsletter.
Note: You can manage your email subscriptions using the links provided in the email footer.