We are about to go full bore and test this extension at our entire middle school. We need it or something like it - so I realize it's not officially released, but I guess we'll be guinea pigs.
When I change the location field in google dashboard, and reload the policy - I can see the location field update on the chromebook's policy page, but the OneTwoOne extension doesn't start blocking traffic. Only after they reboot or sign out and back in, does the extension start blocking traffic properly.
Removing the user and adding an asterisk to the location field, and reloading the policy does not unlock the chromebook either - we still have to log out or reboot to allow anyone to log back in. Not a big deal, but wasn't sure if that was expected behavior.
We are about to go full bore and test this extension at our entire middle school. We need it or something like it - so I realize it's not officially released, but I guess we'll be guinea pigs.
When I change the location field in google dashboard, and reload the policy - I can see the location field update on the chromebook's policy page, but the OneTwoOne extension doesn't start blocking traffic. Only after they reboot or sign out and back in, does the extension start blocking traffic properly.
Removing the user and adding an asterisk to the location field, and reloading the policy does not unlock the chromebook either - we still have to log out or reboot to allow anyone to log back in. Not a big deal, but wasn't sure if that was expected behavior.