Fleet docs: Clarify to use chrome extension only on ChromeOS (#12266)

# Checklist for submitter

If some of the following don't apply, delete the relevant line.

- [x] Documented any permissions changes
This commit is contained in:
RachelElysia 2023-06-09 15:12:14 -04:00 committed by GitHub
parent b7acae39bb
commit d1e085f7ab
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 3 additions and 1 deletions

View file

@ -29,7 +29,7 @@ Fleet gathers information from an [osquery](https://github.com/osquery/osquery)
You can also install plain osquery on your hosts and connect to Fleet using osquery's `TLS API` plugins.
> For ChromeOS hosts, the fleetd Chrome extension is installed instead of osquery.
> For ChromeOS hosts, the fleetd Chrome extension is installed instead of osquery. This Chrome browser extension is only supported on ChromeOS operating systems that are managed using [Google Admin](https://admin.google.com).
## Add hosts with Orbit

View file

@ -3,6 +3,8 @@
## Adding ChromeOS hosts to Fleet
Fleet provides a Chrome extension which you can install via Google Admin.
> For ChromeOS hosts, the fleetd Chrome extension is installed instead of osquery. This Chrome browser extension is only supported on ChromeOS operating systems that are managed using [Google Admin](https://admin.google.com).
To learn how to add ChromeOS hosts to Fleet, visit [here](https://fleetdm.com/docs/using-fleet/adding-hosts#add-chromebooks-with-the-fleetd-chrome-extension).
## Available tables