Please enable JavaScript to view this site.

SchoolProtect User Guide

Introduction

Chromebooks can be set up to seamlessly send the logged-in username to SchoolProtect to associate users with the correct filtering group and allow all traffic to be logged under the correct username.

 

The set up is done in two parts:

1.in the SchoolProtect admin portal

2.and then in your Google admin console

 

For each group of users, a policy group is set up in SchoolProtect which generates a unique configuration file for the extension deployed through the Google admin console.

Please note that due to the sequence in which Google Workspace processes extensions, which cannot be altered, there can be a brief delay (mostly a couple of seconds) each time a user logs in before the Chrome extension will become active.

 

Prerequisites

School must be on the SchoolProtect filtering platform.

Chromebooks must be enrolled into the school’s Google Workspace Admin Console.

Google Admin account with sufficient permissions to see the Device Management section.

Each device must have a unique LGfL IP address (10.x.x.x), not behind a school NAT or proxy.

 

Instructions

Setup in SchoolProtect

1.Sign into the SchoolProtect admin console: https://schoolprotect.lgfl.org.uk/.

2.Browse to Policies > Policy Configuration.

3.Create a new policy, choose what to base it on (system default or copy existing policy) and give it a name. The new policy will show under the Inactive Policies section at the bottom of the page.

4.Click Edit to enter the Policy Group page (this is where you can configure time schedules and edit the policy allowed/blocked URLs, categories and Bundles).

5.You should not enter anything into the Priority box.

6.Under Target Group click Chromebook Users (if this button is not showing, check the policy is not targeted to any other user type, i.e. IP addresses, AD groups or USO groups).

7.Click the Download Chromebook Config button and save the file ready to upload to the Google admin console in the next section.

 

 clip0028

 

Repeat this process for each different filtering policy you need to set up.

 

Extension Installation in Google Admin Console

8.Sign into the Google Admin Console and navigate to Devices > Chrome > Apps & Extensions.

9.Navigate to the Organisational Unit (OU) for the group of users that you are targeting. Apps are deployed to users rather than devices, so make sure you are targeting the user OU.

10. Hover over the + sign in the bottom-right-hand corner and click the icon for Add from Chrome Web Store (Chrome icon ).

11. Search for Netsweeper Workstation Agent or paste this into View app by ID: gehcmbonedocjpdjfemeklocmmpedmoj

12. Click Select.

13. Set the Installation policy to Force install. This is vital to stop users uninstalling the extension

14. Scroll down to Policy for extensions and click the upload button.

15. Browse to and upload the config file downloaded in step 6.

16. Click Save.

 

The extension will now be installed when users in the selected OU log into Chromebooks.

 

Repeat this process for each policy group set up in SchoolProtect.

 

Testing & Troubleshooting

To test the extension is working, sign into a Chromebook with a user account that has the extension deployed. After a minute or two, visit http://wsblock.co.uk. You should see a block page which will show the Policy Group. You can see the user name by clicking Display additional information.

 

If users are not getting the correct filtering policy after waiting a few minutes, check the extension is installed by opening the extensions menu and looking for Netsweeper Workstation Agent. If this is not showing, review the Google Admin Console Support Guide: Automatically install apps and extensions - Google Chrome Enterprise Help.

 

If the extension is listed but the user is not placed in the correct group, check the correct config file has been uploaded to the Google admin console. Hoving over the Netsweeper Workstation Agent icon in Chrome will give details of whether the user was added to a filtering group or if there was an error.