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 111

Custom OS settings: Fleet limitation not a Windows MDM limitation (#34156)

Browse source
This commit is contained in:
Noah Talerman 2025-10-13 12:46:57 -04:00 committed by GitHub
parent c1836818bd
commit 4de509b6af
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 3 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -81,11 +81,8 @@ In the list of hosts, click on an individual host and click the **OS settings**
Currently, when editing a profile using Fleet's GitOps workflow, it can take 30 seconds for the
profile's status to update to "Pending."
On Windows, due to limitations of the MDM protocol, verification of [Win32 and Desktop Bridge app ADMX
policy](https://learn.microsoft.com/en-us/windows/client-management/win32-and-centennial-app-policy-configuration)
CSPs are limited. Fleet only verifies that the host returned a success status code in response to the MDM
command to install the configuration profile. You can query the registry keys defined by the ADMX
policy. For instance, if an ADMX file defines the following policy:
For Windows configuration profiles with the [Win32 and Desktop Bridge app ADMX
policies](https://learn.microsoft.com/en-us/windows/client-management/win32-and-centennial-app-policy-configuration), Fleet only verifies that the host returned a success status code in response to the MDM command to install the configuration profile. You can query the registry keys defined by the ADMX policy. For instance, if an ADMX file defines the following policy:
```
<policy name="Subteam" class="Machine" displayName="Subteam" key="Software\Policies\employee\Attributes" explainText="Subteam" presentation="String">
<parentCategory ref="DefaultCategory" />
@ -96,7 +93,7 @@ policy. For instance, if an ADMX file defines the following policy:
</policy>
```
The following osquery query will return any values set by this policy:
To verify that the OS setting is applied, run the following osquery query:
```
SELECT data FROM registry WHERE path = 'HKEY_LOCAL_MACHINE\Software\Policies\employee\Attributes\Subteam';
```