Search Results

What By default, wiped ChromeOS devices automatically re-enroll into your account without users having to enter their username and password. Re-enrollment ensures that the ChromeOS devices remain managed and policies you set are enforced on the ChromeOS device...

What As an administrator managing ChromeOS devices you want to update the Annotated Custom fields in FileWave, but aren't sure how soon those changes will be reflected in the Google Admin console.  When/Why In FileWave 15.3+ we have changed how Annotated Cu...

What It was previously possible to customize the user-visible information for the FileWave Inventory Extension. It was possible to customize icons, name and description. This involved: Download chromebook-whiteboxing.zip and modify the data inside (adding ...

What Powerwash and Wipe Users are ChromeOS reset actions you can send from FileWave. Powerwash resets the Chromebook to a factory-reset state. Wipe Users clears local user data while keeping the Chromebook enrolled for the next user. When/Why Powerwash Powerwa...

What For an MDM (Mobile Device Management) administrator managing ChromeOS devices, the ability to remotely send a reboot command is a powerful tool for device maintenance and troubleshooting. This command ensures that devices are running smoothly, updates ar...

What When setting up Chromebooks you need to ensure that the right APIs are enabled. In FileWave 15.4 there are 2 APIs that are required that were not previously needed. You may have these enabled, but you should still do this process just in case they are no...

What With the release of FileWave version 15.5.0 and onward, administrators can now send custom messages to enrolled devices directly from FileWave Anywhere, FileWave Central, or through API calls. These messages appear as system notifications on users’ devic...

What As an administrator managing ChromeOS devices, you may want to change how often FileWave syncs with Google Admin.  When/Why FileWave syncs ChromeOS data from Google Admin, including the organizational unit a device belongs to. If you make frequent ChromeO...

What The FileWave Chromebook Inventory extension collects Chromebook inventory details that are not available from the Google Admin console alone. This FAQ explains when the extension reports data and why FileWave inventory dates may differ from Google Admin c...

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 config...

FileWave syncs Chromebook data from Google Admin Console so you can view Chromebook inventory alongside the rest of your managed devices. FileWave does not replace Google Admin Console, but it gives you reporting, inventory, custom field, and location tools fo...

Use this article as the starting point when a device is leaving FileWave management, being reassigned, sold, disposed of, or preserved as an inactive record. The key rule is to remove or reset the device's management path before you delete the record from File...

Use this page when a Chromebook should be reassigned, retired, sold, disposed of, or removed from FileWave’s ChromeOS management view. ChromeOS devices are different from macOS, Windows, and FileWave Client devices because FileWave syncs Chromebook records fro...

Use this workflow when you need to remove the Google OAuth token from FileWave and stop ChromeOS management for the environment. This disables ChromeOS integration in FileWave Central and returns the ChromeOS license count to zero. This page disables ChromeOS ...