mirror of
https://github.com/fleetdm/fleet
synced 2026-05-19 06:58:30 +00:00
0b04e7ea9f
#17692 Recently there was a change that filtered out hosts in `EnrollmentState` 3. This change may cause some hosts that are in otherwise good health to appear unresponsive to MDM in the management UI. This change will allow hosts with `EnrollmentStatus` 3 show as enrolled. The root cause of some hosts being in state 3 is still not entirely clear, but may have to do with either trying to re-enroll once already enrolled, or windows updates causing some sort of issue with fleet. Despite the "failed" `EnrollmentState` 3, the host will still display that the system is managed by Fleet, and will actively sync. |
||
|---|---|---|
| .. | ||
| .keep | ||
| 15565-windows-automatic-enrollment | ||
| 16120-add-windows-mdm-support-to-osquery-perf | ||
| 16260-recategorize-mdm-api-endpoints | ||
| 16345-disabled-checkbox-tooltip | ||
| 16562-sql-deadlock | ||
| 16817-ms-edge-vuln | ||
| 17003-ingest-vscode_extensions | ||
| 17061-homebrew-python | ||
| 17208-hover-states | ||
| 17308-script-content-cleanup | ||
| 17313-add-env-from-secret-capability-to-helm | ||
| 17347-team-user-os-version-restrict | ||
| 17534-improve-error-states-org-settings | ||
| 17557-ui-mdm-off-tooltip | ||
| 17562-windows-server-2019-os-details | ||
| 17563-windows-add | ||
| 17624-modal-flash-message-error | ||
| 17662-render-standard-query-platforms-correctly | ||
| 17692-enrollment-state-3.md | ||
| issue-17476-get-bitlocker-status | ||
| min-node-version | ||