Google General Info
The Google General Info section serves as a comprehensive resource for a wide range of information related to Google services, products, and features that don't fit into specific categories. This section covers it all. Whether you're seeking troubleshooting assistance, discovering hidden Google gems, or staying updated on the latest developments, the Google General Info section is your go-to destination for all things Google beyond the scope of specific topics.

Update your apps to the latest Firebase Cloud Messaging APIs and SDKs
What
Google notified Firebase customers in December 2023 that legacy Firebase Cloud Messaging (FCM) APIs would be discontinued on June 20, 2024. That deadline has passed, so this page is mainly useful for confirming the required FileWave and Google-side configuration for Chromebook messaging.
We’re writing to remind you that starting June 20, 2024 the legacy Firebase Cloud Messaging (FCM) APIs will be discontinued.
What do you need to know?
On June 20, 2024, we’re reducing the number of Firebase Cloud Messaging (FCM) legacy register APIs and legacy send APIs that provide similar functionality. This step will allow us to provide you with a more consistent experience and align with Google security standards to improve security, reliability and performance.
Because of these API decommissions, some already-deprecated SDKs and features will stop working after June 20, 2024.
Please consult the tables below to find which Firebase Cloud Messaging (FCM) APIs and corresponding services/SDKs/features will be discontinued and replaced with new alternatives.
When/Why
Google retired legacy FCM APIs in favor of the newer FCM APIs. FileWave 15.4 added support for that change, so Chromebook environments should run FileWave 15.4 or later and confirm that the required Firebase APIs are enabled.
Official Release with 15.4:
FileWave 15.4 added support for Google's newer FCM APIs.
How
What to check
Run FileWave 15.4 or later for Chromebook FCM support.
Confirm the required Firebase APIs are enabled in Google Cloud.
Use the linked Chromebook articles below when validating the setup.
Action Required:
Update to FileWave 15.4 or later if you manage Chromebooks with FileWave. Then follow Confirming Firebase APIs are enabled for Chromebooks (15.4+) to verify the Google-side API configuration.
If Chromebook push behavior is still failing after the FileWave upgrade and Firebase API check, contact FileWave Support with the affected Chromebook details and the API-verification results.
Related Content
Confirming Firebase APIs are enabled for Chromebooks (15.4+)
Chromebook Client Pre-Requisites

Managed Google Chrome
Description
Google allows for management of the Chrome browser through Google Enterprise and Education.  Regardless of device type, by way of  an Enterprise Token, those browsers become managed by Google Admins.
Chrome browser management allows for the control of many aspects,  from setting features like Home Page to browser reporting.
Chrome Enterprise Policy List
Chrome Browser Reporting
Ingredients
The following is required:
Chrome Enterprise Core
Google Management Token
Additionally, the token will need to be delivered to devices.  Instructions for each device type can be found under the relevant section of the FileWave KBs.
Directions
Google have their own KB on this topic: Enroll cloud-managed Chrome browsers
To retrieve the Google Token value:
Log into the Chrome Enterprise Core account
From the Chrome Browser view in the Google Admin console, the token value may be observed.
Use the 'kebab' (vertical ellipsis) to copy the token, to paste into relevant Filesets.
Chromebook devices require no further token, if the device is already managed through the Google console.