Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-05-23 08:58:41 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 114

Custom OS settings guide: add call out (#27975)

Browse source 
Doc update for the following bug: #24322

Also, remove repetitive "OS settings" from headers.
This commit is contained in:
Noah Talerman 2025-04-08 12:59:51 -04:00 committed by GitHub
parent 087d7209fe
commit 6a22631b03
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 7 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
articles/custom-os-settings.md
View file

@ -4,7 +4,7 @@ In Fleet you can enforce OS settings like security restrictions, screen lock, Wi
Currently, Fleet only supports system (device) level configuration profiles.
## Enforce OS settings
## Enforce
You can enforce OS settings using the Fleet UI, Fleet API, or [Fleet's GitOps workflow](https://github.com/fleetdm/fleet-gitops).
@ -24,7 +24,7 @@ Fleet UI:
Fleet API: API documentation is [here](https://fleetdm.com/docs/rest-api/rest-api#add-custom-os-setting-configuration-profile)
### OS settings status
### See status
In the Fleet UI, head to the **Controls > OS settings** tab.
@ -32,14 +32,16 @@ In the top box, with "Verified," "Verifying," "Pending," and "Failed" statuses,
* **Verified**: hosts that applied all OS settings. Fleet verified by running an osquery query on Windows and macOS hosts (declarations profiles are verified with a [DDM StatusReport](https://developer.apple.com/documentation/devicemanagement/statusreport)). Currently, iOS and iPadOS hosts are "Verified" after they acknowledge all MDM commands to apply OS settings.
* Verifying: hosts that acknowledged all MDM commands to apply OS settings. Fleet is verifying. If the profile wasn't delivered, Fleet will redeliver the profile.
* **Verifying**: hosts that acknowledged all MDM commands to apply OS settings. Fleet is verifying. If the profile wasn't delivered, Fleet will redeliver the profile.
* Pending: hosts that are running MDM commands or will run MDM commands to apply OS settings when they come online.
* **Pending**: hosts that are running MDM commands or will run MDM commands to apply OS settings when they come online.
* Failed: hosts that failed to apply OS settings. For Windows profiles, the status codes are documented in Microsoft's documentation [here](https://learn.microsoft.com/en-us/windows/client-management/oma-dm-protocol-support#syncml-response-status-codes).
* **Failed**: hosts that failed to apply OS settings. For Windows profiles, the status codes are documented in Microsoft's documentation [here](https://learn.microsoft.com/en-us/windows/client-management/oma-dm-protocol-support#syncml-response-status-codes).
In the list of hosts, click on an individual host and click the **OS settings** item to see the status for a specific setting.
Currently, when editing a profile using Fleet's GitOps workflow, it can take 30 seconds for the profile's status to update to "Pending."
<meta name="category" value="guides">
<meta name="authorGitHubUsername" value="noahtalerman">
<meta name="authorFullName" value="Noah Talerman">