Configuring Google Chromebooks to Sync with FileWave
The following processes and steps will walk you through getting your FileWave server set up to manage Chromebooks. Current functionality will allow you to pull/query inventory data and utilize our location tracking feature in FileWave. Some steps can be skipped if certain accounts and projects were made beforehand.
- List of countries where Chrome OS Management licenses are sold directly by Google to end customers:
Go to https://eduproducts.withgoogle.com/, click 'contact sales', and then look at the drop-down menu 'Country' - if the country is in the list, it's supported.
- Even if the country is not listed under the link above, a local google partner might be able to help :
- Admin rights within the Google Domain
At least one Chromebook
- Chromebooks Enterprise enrolled
Pre-existing Google Organizational Unit structure (RECOMMENDED)
Running FileWave Server
- Enough FileWave Chromebook licenses to cover every Chromebook in the Google OU
- FileWave HTTPS Root Trusted Certificate
- GCM Setup - Google Cloud Messaging (GCM/Firebase) Setup
Enable Access to APIs
If you just completed the Google Cloud Messaging (GCM/Firebase) Setup, the project will already be selected and will use the project created during the GCM setup (this MUST be set up to continue). If it's not automatically selected, select the drop-down at the top of the screen and choose the correct project. You can also create a new one if you'd like. My Project is called 'FileWave Chromebooks'.
2. Confirm the Project and Enable the APIs for the project
Creating a Service Account and Credentials
Save this JSON file. We'll use it later.
Adding a Delegated User
Any Google user with correct privileges can be used. Make sure whatever Google user you use has a role with the minimum privileges below:
- Admin Console Privileges / Organization Units (Note that this will automatically give corresponding Admin API Privileges)
- Admin Console Privileges / Services / Chrome OS / Manage Devices
Once you have your Google user with the proper role setup, get back to the APIs & Services > Credentials section of Google Cloud Platform so we can tie the Google user with the service account created. https://console.developers.google.com/apis/credentials
OAuth Client ID & Authorizing API Scopes
Sync Google with FileWave
|Now if you go into the Clients section in FileWave you will see a Chromebooks group with the same structure and devices you have in your Google Admin. This may take some time.|
Deploying FileWave Inventory Extension to Chromebooks - We're almost done!
If you want to change the frequency of check-in, you can modify the following attribute in the JSON to reflect check-in frequency (in minutes). The default is 1440, or once per day.
Location Tracking Permissions
If you're wanting to use Location Tracking, you will need to "Allow sites to detect Users' geolocation" in Google Admin. You will find this option in Devices > Chrome > Settings, on the page that loads it will be under Security > Geolocation. For this setting, you want to ensure that you set it at the level in the organization that it should apply. In the image below we only enabled it for Foundry Chromebooks but did not set it for all. If you would like to enable Geolocation for all devices then make sure you set it at the domain level and also make sure that none of your OUs are set to ignore the inheritance of this setting. Simply check the setting on each OU and you will see what it is set to.
Just like with the Extensions, it is important that the OUs that you enable this on either be all of them or, at a minimum, you need to enable it for both the User and Device OUs that you will be using with FileWave.
Congratulations, you can now manage your Chromebooks with FileWave!
If for any reason you experience issues seeing your ChromeOS devices in FileWave or issues with reporting then see the notes in our Chrome Troubleshooting Guide