Updated: 4/28/2023; Published: April 20, 2023
Pearson support is aware that students assigned managed 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 ChromeOS devices for secure testing, and we recommend checking each device's managed status before testing. We also recommend disabling developer tools on devices used for student testing.
To prevent students from testing on unmanaged (non-secure) ChromeOS devices, technology personnel should
Disable developer tools on each testing device.
See instructions for processes below.
To block Chrome developer tools:
Sign in to your Google Admin Console and select Chrome > Settings > Users & browsers.


To set or verify your organization's forced re-enrollment settings:
Sign in to your Google Admin Console and select Devices > Chrome > Settings > Device.

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.
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.

To check the managed status of each device:
|
Pearson will provide an update on resolution status once one has been reached either by Google or Pearson engineering. Monitor TestNav Online Support's Recently Updated page for the most current information. |