ChromeOS
Chrome OS is a lightweight operating system developed by Google, primarily designed for Chromebook devices. It is based on the Linux kernel and primarily revolves around the Google Chrome web browser. Chrome OS is known for its simplicity, speed, and security. It focuses on cloud-based computing, with most applications and data stored and accessed through the Chrome web browser and cloud services. Chromebooks running Chrome OS offer a streamlined user experience, automatic updates, and integration with Google services such as Gmail, Google Drive, and Google Docs. With its emphasis on web-centric usage and cloud-based productivity, Chrome OS provides an efficient and secure computing environment for users who primarily rely on web-based applications and services.

Chromebook Management
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 for Chromebook management.
So what can we do?
FileWave can report Chromebook inventory data such as available disk space, the last logged-in user, and login timing. You can use that data in Reports, scheduled emails, custom fields, and exports.
FileWave can also gather location data and show it on a map in FileWave Central.
How do I set all this up?
Before managing Chromebooks in FileWave, complete the Google Admin Console sync and license setup.
Confirm that FileWave has enough Chromebook licenses. In FileWave Central, check this under Server > Activation Code.
FileWave syncs the full Chromebook device list from Google Admin Console. If FileWave does not have enough Chromebook licenses for the devices you manage in Google Admin Console, you will not be able to update the model.
Follow the linked quick start guide to sync Google Admin Console with FileWave and enroll your Chromebooks: Quick Start Guide for Chromebooks
After the sync is complete, FileWave Central shows the synced Chromebook groups in Clients.
These devices and groups are synced from Google Admin Console, so they cannot be deleted directly from FileWave.

Chrome OS: FileWave Inventory Extension Behavior (FAQ)
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 console dates.
When/Why
Use the Inventory extension to collect additional Chromebook inventory, request updated inventory, and start remote control sessions.
How does it work?
Q: How do I install the Inventory extension?
A: Use the Quick Start Guide for Chromebooks.
Q: What does the Inventory extension do?
A: See Chrome OS: FileWave Inventory Extension Capabilities for the full capability list.
Q: How frequently does the extension report data?
A: The extension reports data based on the frequency in the JSON configuration file. The default is once per day, and you can change it in the JSON.
Q: Will the extension send data no matter what?
A: No. These conditions must be true before the extension can send data:
The device is on and connected to a network.
The device is not asleep.
A user is logged in, because the extension runs in the user context.
The extension is installed for that user.
The endpoint can reach the FileWave server. For off-network devices, that means the FileWave server must be reachable from the internet path the Chromebook is using.
Q: What happens if the device is offline, off, or asleep when it should send inventory?
A: Nothing happens immediately. When the device comes back online with a user logged in, it should submit inventory right away.
Q: Will the Inventory extension work if Chrome is not open?
A: No. The Inventory extension is a browser extension, so it works only when a user is logged in and Chrome is open.
Q: Why are Last Sync and Last Connected different in inventory?
A: Last Connected is usually the more useful value. It shows when the device last talked directly to your FileWave server through the extension. Last Sync shows when the device last checked in with the Google Admin console.
Q: How frequently does FileWave receive data from the Google Admin console?
A: By default, the FileWave server synchronizes with Google nightly at midnight. You can force an on-demand synchronization from the Google preferences tab.
Q: Why does Google Admin console data differ from FileWave inventory?
A: The data probably changed after the last Google-to-FileWave synchronization. The device checks in with Google on one schedule, and FileWave synchronizes with Google on another. A manual synchronization should bring the data up to date.
Related Content
Quick Start Guide for Chromebooks
Chrome OS: FileWave Inventory Extension Capabilities

Chrome Troubleshooting Guide
You have already:
Enrolled devices into your Google Suite (https://support.google.com/chrome/a/answer/1360534?hl=en)
Followed the Quick Start Guide for Chromebooks to install the extension on your devices
Verified you have a license for Chrome devices
Problem
Having issues with Chrome OS devices communicating with FileWave Admin.
Solution
Verify Chrome extension is installed in the policy
Verify FileWave extension has registered with FCM/GCM by looking at the log
Devices are not showing at all in FileWave
In the native client open Preferences > Google as shown
Is the status icon not green? Anything other than green would indicate an issue
If you have a large number of ChromeOS devices it is possible that the server is timing out when trying to sync with Google. This can be especially true on the first sync
A solution is to edit this file on the FileWave server: 
/usr/local/filewave/apache/conf/httpd.conf
Look for a section in the file like this:
    # chrome app
    WSGIDaemonProcess chrome display-name=filewave-chrome processes=1 threads=2 python-eggs=/usr/local/filewave/apache/.python-eggs shutdown-timeout=5 deadlock-timeout=300 inactivity-timeout=3600 request-timeout=3600 socket-timeout=3600
Change the timeout values so that deadlock-timeout=600 but otherwise the values above should match your server. If any values are lower in your config you should make them at least match the above listed values
Restart everything with;
fwcontrol server restart
If the issue was a timeout then the sync should now complete. For about 50,000 devices the sync can take 10+ minutes to complete on first sync.
Devices are not showing Geolocation information in FileWave
If devices are showing in FileWave, but Geolocation details are not showing up, and possibly the FileWave Inventory Extension icon is not showing even if you set it to Force Install + Pin then you very likely enabled Geolocation as well as the Extension for an OU that only includes the Device, but not the User who is logging in. You must ensure that both OUs are enabled or put the User and Device in the same OU for testing. This should not be an issue if you have set Geolocation and the Inventory Extension enabled for your entire domain, but frequently when someone is evaluating FileWave they might enable it for only one OU for testing. If you do that then make sure that the User and Device are in that same testing OU.
View the device policy
Open a Google Chrome window
Browse to the URL: chrome://policy
Scroll down to ExtensionInstallForcelist and select show more
Look for the ID of the FileWave Inventory Extension ( ldhgnmkjehdokljjhcpkbhcmhoficdio  Figure 1.1 )
If you see it there, scroll to the very bottom
There will be a whole section for the FileWave Inventory Extension
Verify all the policy fields are there ( Figure 1.2 )
 
Figure 1.1 - Chrome Policy Force List
 
Figure 1.2 - Chrome Policy for FileWave
View the Extension Console Log
Open a Google Chrome window
Browse to the URL: chrome://extensions
Be sure Developer mode is enabled
Click Details (Figure 2.1)
Open the Background page (Figure 2.2)
Select the Console tab to view the log 
Verify the log contains "FCM Registration" (Figure 2.3)
The is the messaging system FileWave uses to talk to the device, if it does not register then we can not communicate.
If it failed or is empty. make sure the JSON used in the extension configuration contained FCM information
Verify the log contains "... Report sent successfully"
This confirms that the device is able to talk to your FileWave server
if it is unable to send reports, then verify your JSON contains your server name and an inventory token
 
Figure 2.1 - Chrome Extensions
 
Figure 2.2 - Chrome Extension Details
 
Figure 2.3 - Extension log
 
 
 
Error
Details
Solution
GCM failed to register
The device(s) are unable to use the information they received to contact Google's GCM/Firebase services
Be sure you have GCM registered properly (Google Cloud Messaging (GCM/Firebase) Setup) in your admin preferences BEFORE you exported the settings for upload into Google Suite. You can always export it again.
Failed to load resource: net : : ERR_INSECURE_RESPONSE
The device(s) is unable to connect to your server with a secure connections
* Verify the server has a valid certificate
* Verify the server's certificate is either root trusted or has been uploaded to your google suite (see Quick Start Guide for Chromebooks)
* Verify the ports between devices and server are open (see: Default TCP and UDP Port Usage )
Error: failed to gather Geolocation data: All attempts exhausted
The FileWave client on the device was unable to receive location information from the devices' OS
* Verify in the devices security preferences the app has admin rights to location information
Failed to send inventory data
The device was unable to contact the inventory port on the server
* Verify the ports between devices and server are open (see: Default TCP and UDP Port Usage )
* Verify you have all your settings in preferences BEFORE you exported the settings for upload into Google Suite. You can always export it again.
GET https://server.name:20445/inv/api/v1/client/settings/asdasdasd net : : ERR_NAME_RESOLUTION_FAILED
There was a problem looking up the same of your server from the information received during enrollment
* Verify you have all your settings in preferences BEFORE you exported the settings for upload into Google Suite. You can always export it again.
Uncaught (in Promise) TypeError: Cannot read property 'state' of undefined at ...
Device was unable to contact the FileWave server OR the device was able to contact the FileWave server but the state of the device could not be read.
* Attempt to change the state FileWave Admin and update the mode. Wait for the device to verify or force a verify of the device.
* If the problem persists contact FileWave support.

Chrome OS: FileWave Inventory Extension Capabilities
What
An optional add-on for Chromebook management in FileWave is the FileWave Inventory extension.  We'll describe what this add-on allows you to do in this article.
When/Why
We'll want to make use of the inventory extension for any of the following functions:
Additional Inventory Retrieval (Beyond what the Google Admin Console sends us):
Application Information (installed app and extensions)
User Information (currently logged in user, etc)
Network Information (current IP)
Font Information
Device Storage data (drive space, etc)
Geo-location Information (location, but only if explicitly turned on)
Submit "Last Connected" time (which should not be confused with last sync time...Last Connected is the last time the device talked directly to the FileWave server)
Ability to initiate an remote control session through TeamViewer (version 14.6+)
To send a "Verify" to make the device check in immediately
How
Reference the Quick Start Guide below for instructions on setting up the inventory extension for your Chromebooks.

Disable Chrome OS in FileWave
These steps will walk you through the process of disabling Chrome OS in FileWave
Open Preferences in the FileWave Admin
Go to the Chromebooks tab
Click Configure OAuth token
Sign in with your super user credentials
In the window that pops up (seen below), click the Clear button
Confirm that you wish to process by clicking Yes
You have now disabled Chrome OS from FileWave. All of your Chrome OS licenses are now at zero.

Powerwash / Wipe Users on ChromeOS (15.3+)
What
Powerwash and Wipe Users are features on ChromeOS that allow users to reset their Chromebook to its original state, effectively erasing all user data and returning the device to its factory settings. These features are particularly useful for managing devices in environments where they are shared among multiple users, such as schools and businesses, or when preparing a device for a new user.
When/Why
Powerwash
Powerwash is the term used by ChromeOS for its factory reset process. When you Powerwash a Chromebook, the device undergoes a complete reset, removing all user accounts, their files, and every setting adjustment made to the device. This process returns the Chromebook to its original state, just as it was out of the box. It's a straightforward way to ensure that no personal data is left on the device, making it ready for a new user or for troubleshooting purposes.
Technical Perspective:
Use Case: Ideal for individuals returning, selling, or reassigning their Chromebook. Also used for troubleshooting device issues that cannot be resolved through standard fixes.
Process: Initiated through the settings menu under "Advanced" settings or via a keyboard shortcut at the login screen (pressing Ctrl + Alt + Shift + R).
Considerations: Before performing a Powerwash, it's crucial to back up any important data stored on the device, as the process will delete everything.
Wipe Users
Wipe Users is a feature aimed more at administrators managing multiple Chromebooks within an organization, such as a school or a corporation. This feature allows administrators to remotely clear all user data from a Chromebook without affecting the device's enrollment status in a domain. It's particularly useful for quickly preparing devices for new users without going through a full device setup process again.
Technical Perspective:
Use Case: Primarily used by administrators to quickly clear all personal data from devices between different users while retaining device management settings and policies.
Process: Can be executed remotely via Google Admin Console, under the device management section, allowing for bulk operations across multiple devices.
Considerations: Ensures that devices remain under organizational control and policies after user data is wiped, streamlining the reassignment process.
Both Powerwash and Wipe Users serve critical roles in the management and maintenance of ChromeOS devices, ensuring data privacy and security while facilitating device transitions between users. Powerwash provides a complete reset for individual users or troubleshooting, while Wipe Users allows administrators to efficiently manage device readiness in a controlled environment without disrupting device enrollment and management settings. For organizations using Chromebooks, understanding and utilizing these features effectively can greatly enhance operational efficiency and device security.
How
These commands are executed by right clicking one or more Chromebooks and picking Wipe Device or Wipe Users as shown below.
REMOTE_POWERWASH Command (Wipe Device)
Description: System administrators can remotely Powerwash ChromeOS devices, resetting them to factory settings for efficient troubleshooting and maintaining device security.
Execution: Initiates the Powerwash process, erasing all user data and configurations.
Access:
The REMOTE_POWERWASH command is accessible through the Central as well as Anywhere Admin for ChromeOS devices.
Find the command in the dropdown menu labeled "Wipe device(s)..."
Modify Clients/Groups and Wipe Devices permissions are required.
When wiping a device keep in mind it will fully wipe the device and you should consider Force wiped ChromeOS devices to re-enroll (15.3+)
WIPE_USERS Command
Description: System administrators can remotely and securely wipe user data from devices, ensuring compliance with data protection regulations and maintaining organizational security.
Execution: Initiates the data-wiping process on all user accounts.
Access:
The WIPE_USERS command is accessible through the Central as well as Anywhere Admin for ChromeOS devices.
Find the command in the dropdown menu labeled "Wipe user(s)..."
Modify Clients/Groups and Wipe Devices permissions are required.
Command History tab
Description: Users can now view all information related to sending REMOTE_POWERWASH, WIPE_USERS, and REBOOT Commands in the Command History tab for Chromebook devices. As shown below you can see this when looking at device details for a Chromebook. 
Related Content
ChromeOS
Reboot for ChromeOS (15.3+)

Reboot for ChromeOS (15.3+)
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 are applied, and any minor issues are resolved without the need for manual intervention.
When/Why
Understanding the Reboot Command
Purpose: The reboot command allows administrators to remotely restart ChromeOS devices, which is essential for applying updates, enforcing new policies, or fixing software issues.
Execution: Through the MDM solution integrated with Google's Chrome Enterprise services, admins can issue reboot commands directly from the management console. This process ensures that all devices are up-to-date and functioning as expected.
Considerations: When sending a reboot command, it's important to consider the timing and potential impact on users. Ideally, reboots should be scheduled during off-hours or times when the device is not in active use to minimize disruption. It's also good practice to inform users about planned reboots.
Practical Use Cases
Applying Updates: To ensure devices have the latest features and security patches.
Resolving Issues: To fix minor glitches that can be cleared with a restart.
Enforcing Policies: To apply new configurations or policies that require a reboot to take effect.
Tips for MDM Administrators
User Communication: Notify users about scheduled reboots, especially if they are during working hours.
Scheduling: Plan reboots during times that will least impact users, like after-hours or during known downtime.
Monitoring: After issuing a reboot command, monitor the devices to ensure they restart successfully and operate as expected.
By leveraging the reboot command through your MDM solution, you can maintain control over the ChromeOS devices within your organization, ensuring they remain secure, up-to-date, and operate without issues. This command is a straightforward yet essential part of device management that helps keep everything running smoothly.
How
This command is executed by right clicking one or more Chromebooks and picking Restart... as shown below.
REBOOT Command
Description: Introducing the REBOOT command, enabling system administrators to reboot devices for troubleshooting remotely and applying system updates.
Execution: Initiates the remote reboot process on the selected devices.
Access:
The REBOOT command is accessible through the Central as well as Anywhere Admin for ChromeOS devices.
Find the command in the dropdown menu labeled "Reboot..."
Read permissions is the only requirement.
Command History tab
Description: Users can now view all information related to sending REMOTE_POWERWASH, WIPE_USERS, and REBOOT Commands in the Command History tab for Chromebook devices. As shown below you can see this when looking at device details for a Chromebook. 
Related Content
ChromeOS
Powerwash / Wipe Users on ChromeOS (15.3+)

Google Admin Sync Interval for ChromeOS
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 ChromeOS changes, a shorter sync interval can help FileWave pick up those changes sooner.
How
In FileWave Central, go to Preferences > Google, then adjust the value for "Synchronize with Google Admin every 24 hours." The value can be between 1 and 24 hours. The default is 24 hours.
Related Content
ChromeOS

Custom Field Annotated Field Sync for ChromeOS (15.3+)
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 Custom Fields are synced with Google. In the past there would be issues reported because the fields would only sync on the 24 hour sync interval for all ChromeOS information with Google.
How
Annotated fields in Edit Custom Fields in 15.3+ now update immediately upon clicking Save, independently of the Model Update, ensuring swift and accurate changes.
The Chromebook Data tab in Device Details is removed. Users can access Chromebook-related info by double-clicking on the device, eliminating the need for an additional tab.
The Device Details View now offers a more informative and user-friendly experience for Annotated fields.
Annotated fields are seamlessly displayed and editable in the Edit Custom Fields dialog, like any other custom fields.
A convenient button in the Client Info dialog allows users to sync annotated fields (one way: Google to FileWave) individually for specific devices, offering granular control over data synchronization.
Related Content
ChromeOS

Forcing wiped ChromeOS devices to re-enroll (15.3+)
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. Otherwise, users can't sign in, browse in guest mode, or see the consumer sign-in screen.
When/Why
Don’t force ChromeOS devices that are used in developer mode to re-enroll. Instead, put them in a different organizational unit and turn off forced re-enrollment for that organization. If a ChromeOS device is no longer going to be managed by your account, you should deprovision the device.
How
For convenience we've included Google's documentation below from: Force wiped ChromeOS devices to re-enroll - Chrome Enterprise and Education Help (google.com)
Turn forced re-enrollment on or off
Sign in to your Google Admin console.
Sign in using an administrator account, not your current account bob@gmail.com
In the Admin console, go to Menu 
 Devices
Chrome
Settings
Device settings.
To apply the setting to all devices, leave the top organizational unit selected. Otherwise, select a child organizational unit.
Go to Enrollment and access.
Configure the Forced re-enrollment setting:
Force device to automatically re-enroll after wiping—Wiped ChromeOS devices automatically re-enroll into your account without users having to enter their username and password. 
Force device to re-enroll with user credentials after wiping—Users must manually re-enroll ChromeOS devices into your account.
Device is not forced to re-enroll after wiping—Users can use the ChromeOS device without re-enrolling it into your account.
Click Save.
Settings typically take effect within minutes, but it might take up to an hour to propagate through your organization.
Sometimes, ChromeOS devices might not be able to automatically re-enroll themselves. If an error occurs during automatic re-enrollment, users are notified. They can click Enroll manually to proceed with manual re-enrollment. ChromeOS devices that don’t support automatic re-enrollment show a screen that prompts users to manually re-enroll them.
Related Content
Force wiped ChromeOS devices to re-enroll - Chrome Enterprise and Education Help (google.com)

Confirming Firebase APIs are enabled for Chromebooks (15.4+)
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 not. 
When/Why
You will want to do this when you are using FileWave 15.4.0 or higher with Chromebooks to make sure everything is right. If you have not previously, you definitely need to enable the 2 APIs. You can enable them on a 15.3.1 server as well, but the APIs are required for 15.4.0 and beyond, and required to be on 15.4.0 after June 20, 2024.
How
To enable the 2 APIS you may go to https://console.cloud.google.com/apis/dashboard and enable them. You would be looking for Firebase Cloud Messaging API and Firebase Management API. To simplify here is a more direct URL to add them to a project: https://console.developers.google.com/flows/enableapi?apiid=firebase.googleapis.com,fcm.googleapis.com which should be straightforward if you only have 1 Firebase project. If you don't really know how Chromebooks were setup in the past you could go through Chromebook Client Pre-Requisites and set it up again.
When you go to the URL you should see something like this next screen where you can pick a project and click Next. 
Next you will see the 2 APIs to enable and you'll click Enable. 
Once you have enabled this you should see in FileWave Central on v15.4 that it is able to sync by going to Settings -> Google and viewing the sync status there. 
Related Content
Chromebook Client Pre-Requisites
Update your apps to the latest Firebase Cloud Messaging APIs and SDKs