Technical Bulletin

---

Updated: May 5, 2023;

Published: April 1920, 2023 2023

What is happening?

Pearson support is aware that students assigned managed Chrome devices (typically Chromebooks - do they use any other kind of ChromeOS device?) can ChromeOS devices can bypass security settings by performing a series of complex processes that include resetting the device to factory settings (powerwashing or wiping) and then reconfiguring the device as unmanaged.

Pearson does not support unmanaged Chromebooks ChromeOS devices for secure testing. Google is working to resolve this issue, and Pearson is monitoring the status of that resolution. Pearson is also working on an update that will check a To prevent students from testing on unmanaged devices, Pearson recommends using ChromeOS 108 LTS or ChromeOS 111+, disabling developer tools, forcing re-enrollment, and checking each device's managed status prior to testing. (In App Check? at sign in? perhaps we stay vague for now.)on test day.

What does this mean?

To avoid To prevent students from testing on unmanaged (non-secure) ChromeOS devices:, technology personnel should:

• Update or roll back ChromeOS to either version 108 LTS or 111+.
• Disable developer tools on each testing device.
• Set each device
• Technology personnel (or proctors) must check the managed status of each device before testing.
• Technology personnel must also ensure that each device is set to force re-enrollment as a a managed device when after it 's powerwashed (do we want to use this term or keep the wording "reset to factory settings"?) is powerwashed/wiped and restarted for reuse. This is a best practice.
• Immediately before the start of the test session, check the managed status of each device. Teachers or proctors can also complete this task.

See instructions for Instructions for both processes below. 

What do I need to do (and how do I do it

?)

To use ChromeOS 108 LTS or ChromeOS 111+:

Use your established practice for updating ChromeOS testing devices.
Customers that need to to roll back ChromeOS, see Roll back ChromeOS to a previous version.

To block Chrome developer tools:

1. Sign in to your Google Admin Console and select Chrome > Settings > Users & browsers
   Image Added
   
   
2. Select or search for the organizational unit for which you want to apply (or verify) these settings. The example below shows Pearson as the intended organization. Your organization will be a district or school.
   Image Added
   
   
3. Search for Developer tools in the User experience section. Then, select Never allow use of built-in developer tools.

To set or verify your organization's forced re-enrollment settings:

1. Sign in to your Google Admin Consoleand select Devices > Chrome > Settings > Device.
   Image Added
   
   
2. Select or search for the organizational unit for which you want to apply (or verify) these settings. The example below shows Pearson as the intended organization. Your organization will be a district or school
   Image Added
   
   
3. In the Forced Re-enrollment section, select one of the options below:
   - Force device to automatically re-enroll after wiping
   - Or, Force device to re-enroll with user credentials after wiping
   Image Added

Image Removed

Tiny Link: 

To set to force re-enrollment as a a managed device:

Tiny link: https://support.assessment.pearson.com/x/JwD5BQBoRHBg