Google Chromebook Education for Schools setup

[password1234]

Hi Guys

 

One of our schools we support are moving completely down the route of Google Chrome Book, they have purchased a bunch of Chrome books and the Educational licensing and we due to setup in the next few weeks or so,

 

Its all completely new to us this so first time we getting involved in this setup, its a managed setup we are deploying

 

I'm assuming its extremely straight forward to setup, once the licenses are activated on the console, setup the polices from within the console, select what apps you want to push out and user setup and all sorts

 

then once we unbox the chrome books its just a case of connecting them to Wifi, sign in using the admin account and it will then download all the policies automatically

 

I guess thats all there is to it right?

 

Its for a small primary school, would you recommend setting up generic class logins? or each individual pupil have their own logins? any other tips or pointers?

 

 

Thanks

Edited May 16, 2022 by password1234

[Danp]

then once we unbox the chrome books its just a case of connecting them to Wifi, sign in using the admin account and it will then download all the policies automatically

 

I guess thats all there is to it right?

 

Basically, yes, that's it

 

Its for a small primary school, would you recommend setting up generic class logins? or each individual pupil have their own logins? any other tips or pointers?

 

I would and do promote individual usernames and passwords as it's part of their learning to use devices.

[dhicks]

once the licenses are activated on the console, setup the polices from within the console, select what apps you want to push out and user setup and all sorts then once we unbox the chrome books its just a case of connecting them to Wifi, sign in using the admin account and it will then download all the policies automatically

 

Yes, pretty much. You might want to create a separate account for adding devices with just the permissions needed for adding devices, then you're not logging on to your fully-privileged admin account each time you add a device.

 

"apps" on ChromeOS might be different to what you're thinking of from iOS / Android. Most of the apps we use are web-based, you just point the children at a login page. Ideally, any such application would use Google logins so they just get logged straight in. You can push out ChromeOS / Android apps, but we've generally gone for web-based instead.

 

Settings can be added per-device but, quite often, are per-user. This is quite useful as a pupil should get the same settings and apps available no matter what device they log on to, even a home device if they log on with their school account.

 

Its for a small primary school, would you recommend setting up generic class logins? or each individual pupil have their own logins?

 

We have our junior devices (up to Year 3) log in with a default guest session, so they open the device and it just starts up. That session is reasonably limited - they can't get to YouTube on it, for instance. Each child does have an individual login, so in Year 3 they can start to log on to websites using their username and password, and by Year 4 they've generally all got the idea.

[jthompson]

The term for adding Chromebooks into your domain, so that they are school-owned and managed devices, is enterprise enrollment.

 

There is a user setting that will allow users to enrol devices into the domain. You will probably only want to grant that ability to your admin account(s), rather than give it to a broad selection of other users.

 

When a Chromebook gets enrolled, it will use up one of your Chrome upgrade licenses. That's irreversible as you can't release that license from the device or transfer it to another one (unless it's a specific case of a faulty device being replaced by the manufacturer). That's why you don't want just anybody to have enrollment privileges, lest they enrol their own personal device and cost you a license.

 

I've found it best to set up OUs such that they contain either users or devices, and not a mix of both. That helps with the mental gymnastics of device settings versus user settings.

[paulkerton]

Enterprise Enroll them, and then basically yes, you're away.

Like said above keep OUs for users and devices seperate from each other.

Edited May 17, 2022 by paulkerton