fleet/articles/chrome-os.md

# ChromeOS
For visibility on ChromeOS hosts, Fleet provides the fleetd Chrome extension which provides similar functionality as osquery on other operating systems.

Follow the instructions in our [host enrollment guide](https://fleetdm.com/guides/enroll-hosts#enroll-chromebooks) to add Chromebooks to Fleet.

> The fleetd Chrome browser extension is supported on ChromeOS operating systems that are managed using [Google Admin](https://admin.google.com). It is not intended for non-ChromeOS hosts with the Chrome browser installed.

## Available tables
See our [ChromeOS tables list](https://fleetdm.com/tables/chrome_extensions?platformFilter=chrome) for available tables.

## Setting the hostname
By default, the hostname for a Chromebook host will be blank. The hostname can be customized in Google Admin under Devices > Chrome > Settings > Device > Device Settings > Other Settings > [Device network hostname template](https://support.google.com/chrome/a/answer/1375678#zippy=%2Cdevice-network-hostname-template%2Creport-device-os-information).

## Current limitations in ChromeOS
- Scheduled queries are currently not available in ChromeOS
- The Fleetd Chrome extension must be force-installed by enterprise policy in order to have full access to the host's data.
- More tables that could be added:
  - `disk_events`: https://github.com/fleetdm/fleet/issues/12405
  - `client_certificates`: https://github.com/fleetdm/fleet/issues/12465
  - `usb_devices`: https://github.com/fleetdm/fleet/issues/12780

## Debugging ChromeOS
See our [fleetd Chrome extension testing docs](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/getting-started/testing-and-local-development.md#fleetd-chrome-extension) for debugging instructions.

<meta name="category" value="guides">
<meta name="authorGitHubUsername" value="zhumo">
<meta name="authorFullName" value="Mo Zhu">
<meta name="publishedOn" value="2023-11-21">
<meta name="articleTitle" value="ChromeOS">
<meta name="description" value="Learn about ChromeOS and Fleet.">
Chrome docs (#11747) 2023-06-09 17:03:01 +00:00			`# ChromeOS`
Warning about installing extension on Chrome browsers (#12596) Co-authored-by: Rachael Shaw <r@rachael.wtf> 2023-07-07 16:55:38 +00:00			`For visibility on ChromeOS hosts, Fleet provides the fleetd Chrome extension which provides similar functionality as osquery on other operating systems.`
Chrome docs (#11747) 2023-06-09 17:03:01 +00:00
Clean up "here" link anchors in articles (#29755) 2025-06-09 13:48:27 +00:00			`Follow the instructions in our [host enrollment guide](https://fleetdm.com/guides/enroll-hosts#enroll-chromebooks) to add Chromebooks to Fleet.`
Chrome docs (#11747) 2023-06-09 17:03:01 +00:00
Warning about installing extension on Chrome browsers (#12596) Co-authored-by: Rachael Shaw <r@rachael.wtf> 2023-07-07 16:55:38 +00:00			`> The fleetd Chrome browser extension is supported on ChromeOS operating systems that are managed using [Google Admin](https://admin.google.com). It is not intended for non-ChromeOS hosts with the Chrome browser installed.`

Chrome docs (#11747) 2023-06-09 17:03:01 +00:00			`## Available tables`
Clean up "here" link anchors in articles (#29755) 2025-06-09 13:48:27 +00:00			`See our [ChromeOS tables list](https://fleetdm.com/tables/chrome_extensions?platformFilter=chrome) for available tables.`
Chrome docs (#11747) 2023-06-09 17:03:01 +00:00
			`## Setting the hostname`
			`By default, the hostname for a Chromebook host will be blank. The hostname can be customized in Google Admin under Devices > Chrome > Settings > Device > Device Settings > Other Settings > [Device network hostname template](https://support.google.com/chrome/a/answer/1375678#zippy=%2Cdevice-network-hostname-template%2Creport-device-os-information).`

Docs: Fix title (#13917) Sentence-case fix 2023-09-13 20:57:30 +00:00			`## Current limitations in ChromeOS`
Chrome docs (#11747) 2023-06-09 17:03:01 +00:00			`- Scheduled queries are currently not available in ChromeOS`
			`- The Fleetd Chrome extension must be force-installed by enterprise policy in order to have full access to the host's data.`
List future tables in Chrome (#12781) 2023-07-18 16:54:05 +00:00			`- More tables that could be added:`
			- `disk_events`: https://github.com/fleetdm/fleet/issues/12405
			- `client_certificates`: https://github.com/fleetdm/fleet/issues/12465
			- `usb_devices`: https://github.com/fleetdm/fleet/issues/12780
Chrome docs (#11747) 2023-06-09 17:03:01 +00:00
			`## Debugging ChromeOS`
Clean up "here" link anchors in articles (#29755) 2025-06-09 13:48:27 +00:00			`See our [fleetd Chrome extension testing docs](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/getting-started/testing-and-local-development.md#fleetd-chrome-extension) for debugging instructions.`
Docs quick reference optimization (#21331) This PR closes https://github.com/fleetdm/fleet/issues/21108 @noahtalerman, I double-checked all redirects, and they are working. Clicking through the URLs in [this spreadsheet](https://docs.google.com/spreadsheets/d/1djVynIMuJK4pT5ziJW12CluVqcaoxxnCLaBO3VXfAt4/edit?usp=sharing) is a pretty quick way to go through them all. Note that "Audit logs" and "Understanding host vitals" redirect to the contributor docs on GitHub, so they will throw a 404 until this is merged. Some new guides benefitted from a name change, so they make more sense as stand-alone guides, and also so that we don't have to mess around with more redirects later. Those name changes followed [this convention](https://fleetdm.com/handbook/company/communications#headings-and-titles), which was recently documented in the handbook. Have fun! --------- Co-authored-by: Eric <eashaw@sailsjs.com> Co-authored-by: Noah Talerman <noahtal@umich.edu> 2024-08-16 20:30:31 +00:00
			`<meta name="category" value="guides">`
			`<meta name="authorGitHubUsername" value="zhumo">`
			`<meta name="authorFullName" value="Mo Zhu">`
			`<meta name="publishedOn" value="2023-11-21">`
			`<meta name="articleTitle" value="ChromeOS">`
			`<meta name="description" value="Learn about ChromeOS and Fleet.">`