Chromebooks on N4L Individualised Filtering

[Patrick Dunford]

OK

So it looked pretty promising with our testing, we were all ready to roll out, and then someone thought to log the Chromebook out, and guess what? The certificate disappeared off the Chromebook.

So now I have this problem

• The console cannot push the certificate down to the Chromebook automatically
• If we install the certificate manually, it disappears as soon as the user logs off.

Either of these install techniques needs to be installing the certificate for all users on that device.

I have to do some more testing to see whether the problem is N4L blocking something the Chromebook needs, or the Chromebook blocking the certificate in some way.

Anyone else here trialling this?

[Alan at Wadestown School]

Hi Patrick

Did you solve this problem? Have you found a feasible way to get the certificate onto the shared Chromebook for all users?

Alan Pugh
Wadestown School

[Patrick Dunford]

Using the Google Apps Console works because Google told us there are no per-device settings in that system. They are all per-user. So apply the certificate to the org unit that contains all the user accounts, or the top of the org unit tree.

We are having a different kind of a problem now with Chromebooks. When the HTTPS filtering is turned on, when the browser opens for the first time, they have to authenticate to N4L, then they get a 405 error in their browser.

--
You received this message because you are subscribed to the Google Groups "Techies for schools" group.
To unsubscribe from this group and stop receiving emails from it, send an email to techies-for-sch...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.