To be able to scan your Chrome OS (e.g. Chromebook) devices with Lansweeper, you need to ensure that they meet the scanning requirements. This article describes these requirements, and how to set up the required project and credential.
Chrome OS scanning requirements
To perform Chrome OS scans, the following requirements must be met:
- Your Lansweeper installation must be version 7.2 or higher.
- Your Lansweeper license must support Chrome OS scanning.
- Your Lansweeper scanning server must have access to the Internet.
- You must have access to the Google admin console that manages your Chrome OS devices.
- You need a G Suite, educational or governmental license to configure and use the API.
- You need to have a project that has the Admin SDK enabled, and a credential that has access to the necessary scopes. Detailed instructions on how to configure this can be found below.
Configuring your Google environment for scanning
Step 1: create a project
First, you'll need to create a project for the domain your Chrome OS devices are located in.
Browse to https://console.developers.google.com/ and sign in as a super administrator. Open the navigation menu in the upper left corner, select the IAM & Admin sub-menu and then Manage Resources within. From here, you can hit the Create project button at the top.
Give your project a name, select the correct organization and location and hit Create
Step 2: enable Admin SDK for your project
Next, enable the Admin SDK for the project you just created.
In the developer console, make sure you have your newly created project selected at the top. Open the navigation menu in the upper left corner, select the APIs & Services sub-menu and then Library within. Perform a search for "Admin SDK", select the API in the search results and hit the Enable button.
Step 3: create service account
Next, create a service account with access to the Admin SDK API of your project.
In the developer console, make sure you have your project selected at the top. Open the navigation menu in the upper left corner, select the APIs & Services sub-menu and then Credentials within. Hit the Create credentials button and then select Service account from the available options.
Enter a name and description for your account, hit Create and continue and then Done
Step 4: copy service account ID and generate JSON key
On the resulting page, the Credentials sub-menu of the APIs & Services menu, click on your newly created service account. Copy the unique ID you see listed on the page, as you'll need it in step 5 of this article.
In the Keys tab of the service account, click the Add key drop-down menu and select the Create new key option within. In the resulting popup, select the JSON format. The key will be saved to your computer. Make sure to keep it somewhere safe. If you lose your key, you'll need to generate a new one. The JSON key will be used as part of your Chrome OS scanning target in Lansweeper.
Step 5: grant service account scope access
Next, grant your service account access to the necessary scopes.
Browse to https://admin.google.com/ and sign in as a super administrator. Open the Security menu on the left, then Access and data control and finally API controls
Hit Manage domain wide delegation at the bottom of the resulting page and then Add new. In the resulting popup, submit the service account ID you copied earlier. In the OAuth scopes input box, paste the following to grant the service account access to the necessary scopes, and hit Authorize:
https://www.googleapis.com/auth/admin.directory.orgunit.readonly,
https://www.googleapis.com/auth/admin.directory.device.chromeos.readonly
Step 6: configure user with Services Admin role
Lastly, make sure you have a user with the Services Admin role. In the Users menu of the admin console, you can add or select a user. Under Admin roles and privileges, you can then select the Services Admin role.
You're now ready to start scanning your Chrome OS devices in Lansweeper, by following this Chrome OS scanning guide. As part of your Lansweeper scanning target, you'll need to submit the user account you configured or created, the one with the Services Admin role. You'll also need to provide the JSON key you generated.
