Chromebook Management
-
- Part of:
- Device Management
Suggested audience: school staff, school administrators, local authority administrators, education partnership administrators.
Overview
The Google Admin console is where you can manage your Chromebooks and other managed devices. You can use it to set device settings and restrictions, deploy apps and extension, configure network connections, and more.
The Google Admin console can be accessed by navigating to: https://admin.google.com
Who has access
User allocated the Google Admin role, in the UMP, have access to the Google Admin console, but are scoped to only see appropriate organisational units.
The role can only be assigned to a user, by an existing Google Admin. For example, a Google Admin in a school, will only see the organisational units for their school. Whereas a Google Admin in a local authority will see all school organisational units as well as any organisational units at an LA level.
Note: A user with a Google Admin role will have admin rights for a school or the whole LA and can remotely control ChromeOS devices. Ensure that only those that need this level of access, have this role applied.
Organisational units
Devices and users are organised into Organisational Units. There are 4 organisational units (OU), each then divided into a hierarchy of regions, local authorities and schools.
- Devices
- Governors
- Staff
- Students
Additional OUs can be created on the Devices, Staff and Students branches. This can allow different device policies and apps to be applied to different devices and users.
Add device organisational units (OUs)
- Navigate to Organisational Units
- Search for the OU to create the child OU in
- Click on the + on the OU row under the Devices branch
- Enter a name and description for that OU
- Click Create
Add User Organisational units (OUs)
- Navigate to Organisational Units
- Search for the Learner or Staff Organisational Unit for your school
- Select the Learner or Staff OU to create the child OU in
- Click on the + on the OU row under the Learner or Staff OU branch
- Enter a name and description for that OU
- Click Create
Once OUs are created, they can only be edited or deleted by the Hwb team.
Please contact the Hwb Service Desk for support.
Moving users to a newly created OU
Once you’ve created an OU within the Staff or Learners OU for your school, Google administrators can move users to the that OU.
- Navigate to Users
- Search for the OU the users you wish to move reside in
- Select the users you wish to move
- Choose the “More” dropdown at the top of the page and select “Change organisational unit”
- Select the new OU you wish those users to reside in and click continue
- Select Confirm to confirm the move
If the OU is created outside of the Staff or Learner OU branch, any users moved into those OUs will be moved back to their original location by the provisioning service.
Google admin users have delegated access to perform the appropriate tasks. Some settings, such as those that affect the whole tenant, are only available to the Hwb team.
Chromebook enrolment
A Chromebook is a device which runs Google’s Chrome operating system instead of Windows or MacOS. Chromebooks are designed to be used primarily while connected to the internet, with most applications and documents being in the cloud.
We recommend that all schools enrol their Chromebooks.
Chromebooks can be enrolled and managed via the hwbcymru.net domain.
Benefits of this include:
- allowing users to sign directly into the Chromebooks with Hwb credentials (meaning they are signed into the browser and Hwb applications immediately).
- gaining the ability to manage and enforce device policies which are set in the Google admin console, giving enhanced security controls.
Schools can work with local authorities and Google partners to purchase device management licences and enrol Chromebooks on the hwbcymru.net domain.
There are three enrolment options for maintained schools in Wales:
Managing Chromebooks
When a Chromebook is enrolled into the Google Admin console, it is automatically placed in the correct OU for the school or local authority. This is governed by the enrolment account used.
These devices can be moved to a different device OU to have different policies applied, or have other actions performed on them such as disabling, de-provisioning or resetting.
Individual Chromebooks can be managed by clicking on them on the device list or by searching for them in the Google Admin search bar. Additional information can be viewed and/or edited on an individual device such as asset ID or location.
Chrome remote desktop
As Google Admins, the Chrome Remote Desktop feature has been enabled for use.
Chrome Remote Desktop allows you as administrators to give remote support to your ChromeOS users. If the device is managed in the Hwb tenant, you can use your Hwb account to provide remote support as well as collaborate in a share screen format.
The feature and supporting documentation are available at the following site: https://remotedesktop.google.com
Settings
Policies can be created at any organisation unit level to configure settings or restrictions on the devices or users within the OU, and are inherited by the child OUs.
For user-based settings, you need to create a policy on the user OUs that you want to receive those settings. For example, if you want all users in the school to be assigned a certificate you need to add it to both the Staff OU and the Students OU.
Device settings
Chrome device policies can be used to control settings that apply to a Chromebook or Flex device. Device settings apply for anyone who uses that device.
Chrome device policies must be configured on an organisational unit in the Devices branch.
Multiple device policies can be created on separate device OUs to provide a different set of configurations. Devices will receive the policy assigned to whichever OU it is in, so can be moved to another OU to receive a different policy.
Settings that are not explicitly specified within a policy are inherited from the policy above them.
To view, amend or create a device policy:
- Via the main menu, navigate to Devices > Chrome > Settings > Device
- Search for and select the relevant OU to which you want to apply the policy
- Configure the settings, you can search for a specific setting using the Search or add a filter option
- Click SAVE
For more information on settings available in a Chrome device policy please see the Google support article
User settings
Chrome policies for users are applied when a user logs into a Chromebook or Flex device, or a Chrome browser, the policy is applied regardless of the management of the device.
Some common user settings are homepages, managed bookmarks or wallpaper for managed devices.
User policies are not available for Google Admins. A request to the Hwb Service Desk can be made to change any user settings.
Please contact the Hwb Service Desk for support:
Managed guest sessions
Chromebooks and Flex devices can be configured to allow managed guest sessions, which means that a user can log onto the device without an account while still having some policies and restrictions applied.
Settings configured in a managed guest session are very similar to user settings, but only apply to the ‘guest’ account using the device.
Managed guest sessions must be configured on an organisational unit in the Devices branch.
To enable, disable or configure managed guest sessions
- Navigate to Devices > Chrome > Settings > Managed Guest Sessions
- Select the OU containing the devices
- Change the setting for Managed guest session
- Configure any additional settings
- Click SAVE
No data is saved to the device during a managed guest sessions. The user can still log into Hwb and save work to their Google Drive or OneDrive through the Chrome web browser.
Apps end extensions must be assigned to the device OU to be accessible in the managed guest session. Some apps or extensions may not function properly as they require a user account to be signed in.
For more information on using the managed guest session refer to the Google support article
Printers
Local and network printers can be made available on Chromebooks or Flex devices. These can be deployed to users or devices.
Networks
Network policies can be used to push out Wi-Fi profiles to a user or device. You can also specify other restrictions on Chromebooks such as only allowing connections to a configured Wi-Fi networks.
Wi-Fi profiles can be applied to user or device OUs, and are inherited by the child OUs.
You can create a separate Wi-Fi profile for the device and user. This way, the device would connect to one network while the user would connect to a different one once logged in.
Certificates
Certificates can be assigned to users for use on Chromebooks, Flex devices or Chrome browsers. Since certificates are user assigned they are only applicable when the user logs on and independent of the device used.
Certificates are user based and must be applied to a user OU
Apps and extensions
Before an app or extension can be installed, a Google Admin will need to approve it for use. An app can also be force assigned by a Google Admin and it will then install automatically in your Chrome browser or managed Chromebook. Please refer to the Hwb Privacy Policy before using or deploying any applications.
Apps and extensions, including Android apps, are user based so must be applied to a user OU.
Learners do not have access to the Chrome Web Store so apps and extensions must be force assigned.
Force assigning a Google app will give it permission to access information on the device it’s installed on, such as user’s bookmarks or location, without allowing the end user to review it or even disable it.
Further support
For further support please contact the Hwb Service Desk:
- email: support@hwbcymru.net
- telephone: 03000 25 25 25