Skip to main content
All CollectionsSignagelive Media PlayersChromeOSChromeOS - FAQ's & Troubleshooting
Understanding ChromeOS Players and their Auto Update Expiry Information
Understanding ChromeOS Players and their Auto Update Expiry Information
Ian Maison avatar
Written by Ian Maison
Updated over 9 months ago

All customers should be aware that all Google ChromeOS devices are subject to an Auto Update Expiry policy (see here for more details). It is after this date occurs that Google does not automatically update the operating system on the device.

Please Note

Typically the Auto Update Expiry date is 8 years from the release date of the device.

See here for more details and for a list of all AUE dates for all players.

Finding Auto Update Expiry date in Google Admin console

For devices with Chrome Education Upgrade or Chrome Enterprise Upgrade, the Auto Update Expiry date is available in the Google Admin console.

To find this information, please work through these steps:

  1. In the Google Admin console (via admin.google.com)

  2. In the Google console, please now go to Devices > Chrome devices.

  3. View the Auto-update expiration column.

Findind_your_Chrome_AUE_Date.gif

Risks associated with Auto Updates Expiry

It is worth noting that there are the following risks associated with devices that have past their auto update expiry date -

  • Device has an old version of ChromeOS and Google makes a breaking change to the marketplace - device breaks

  • Device has an old version of ChromeOS and Google makes a breaking change to CDM e.g. a policy update - device breaks

  • Signagelive release an application update that is not compatible with old versions of the OS - device breaks

  • Signagelive only tests against the Long Term Support version therefore there is a risk of an application update not being compatible with an older version of ChromeOS.

We strongly recommend that you replace ChromeOS devices prior to passing Auto Update Expiry to ensure that you are running a supported and secure version of ChromeOS.

Did this answer your question?