Skip to main content


Showing posts from 2018

How to beat ChromeOS EOL and carry on getting updates

ChromeOS devices are great in loads of ways, but they have built-in obsolescence. Google will stop providing updates at a predetermined time according to the schedule you can find here. So the best you will achieve is 6.5 year if you buy the device on the launch day. In reality, it will be generally much less. It's something to watch as a good deal might not be such a good deal if the device only has two years left.

Once a device reaches its "due" date, you get a red pop up telling you its time to update every time you log in. The update section tells you there are no more updates. Now the device will work fine - for a while. You might get another 6 months use out of it before core services like Gmail stop working. However, if you are prepared to do a little work, you can install the OS of your choice onto the device and carry on using the device and not accept this. If you want ChromeOS, then you can install Cloudready from Neverware. I'll outline the basic steps be…

Macros in Google Sheets - a quick look.

New Directory Settings in the G Suite Admin Console

Quick demo of the latest version of the JamBoard App on ChromeOS

JamBoard is rapidly becoming my go-to "whiteboard" type app on ChromeOS. The latest update means your "Jam" file send up in Drive which allows you to preview and organise them.

Preview in a browser
Quick demo on ChromeOS

Kapwing online video editor

Switching from Windows 10 to Ubuntu 17.10

How to lock down API access on your G Suite Domain by Whitelisting

In the G Suite Management Console, there is an important setting that allows you to whitelist the apps that have API access to your domain. I'd recommend doing this to safeguard your data and prevent malicious apps doing bad things! Quick video guide below:

How to lock down who can use Chrome on Windows via Group Policy

You can restrict the use of Chrome to only the accounts you want to use it by enforcing a few group policies. The most recent of these is to force users to sign into Chrome. However, this policy need others to make it effective. Below are the ones I use.

Firstly - force users to sign in to Chrome

Make sure they can only use a domain account

Make sure they cannot use accounts you don't want them using in G Suite services

Disable incognito mode

Disable guest mode
Disable add user (might not want to use this for a staff account as they may need to use more than one account)
With this combination of policies, your users are locked down to their G Suite account and cannot do anything about it. Quick video on what it looks like:

Quick look at the ClearOS Egress Firewall config

Just a quick follow up to my video from a while ago about using ClearOS at a gateway server. One of the things I did not cover was the Egress Firewall app, which is an important part or securing your network.