mirror of
https://github.com/fleetdm/fleet
synced 2026-05-21 16:08:47 +00:00
bd3e775e67
#15565 Replace the use of the isFederated registry key with a keys that check for AAD (Azure Active Directory, now Entra ID) Federated enrollment (`isFederated`) seems to be when windows uses a Discovery MDM endpoint to get its policy and management endpoint configuration. This is always the case when a client is enrolled with fleet, so installations always show up as automatic. It's being replaced by a different key, `AADResourceID`, which appears to identify the resource that controls the automated deployment. In my tests it only appears to be populated when the computer is enrolled through automated deployments. This key appears on both Windows 10 and 11. There is a similar key, `AADTenantID`, which appears to identify the client (tenant) to the Azure cloud. I haven't seen this ID in our systems, so it is likely exclusively used in Azure. Both this key and `AADResourceID` seem to always be set at the same time, so we only check for the `AADResourceID`. I've also added documentation on the registry keys I've analyzed for future reference. |
||
|---|---|---|
| .. | ||
| .keep | ||
| 15565-windows-automatic-enrollment | ||
| 16120-add-windows-mdm-support-to-osquery-perf | ||
| 16260-recategorize-mdm-api-endpoints | ||
| 16562-sql-deadlock | ||
| 16817-ms-edge-vuln | ||
| 17003-ingest-vscode_extensions | ||
| 17061-homebrew-python | ||
| 17308-script-content-cleanup | ||
| 17313-add-env-from-secret-capability-to-helm | ||
| 17347-team-user-os-version-restrict | ||
| 17557-ui-mdm-off-tooltip | ||
| 17563-windows-add | ||
| 17624-modal-flash-message-error | ||
| issue-17476-get-bitlocker-status | ||
| min-node-version | ||