From 6a22631b03b8ceedc3cc182d7a046d40dfc26cfb Mon Sep 17 00:00:00 2001
From: Noah Talerman <47070608+noahtalerman@users.noreply.github.com>
Date: Tue, 8 Apr 2025 12:59:51 -0400
Subject: [PATCH] Custom OS settings guide: add call out (#27975)
Doc update for the following bug: #24322
Also, remove repetitive "OS settings" from headers.
---
articles/custom-os-settings.md | 12 +++++++-----
1 file changed, 7 insertions(+), 5 deletions(-)
diff --git a/articles/custom-os-settings.md b/articles/custom-os-settings.md
index 2dc2336bba..82ed0c352d 100644
--- a/articles/custom-os-settings.md
+++ b/articles/custom-os-settings.md
@@ -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."
+