mirror of
https://github.com/fleetdm/fleet
synced 2026-05-14 20:48:35 +00:00
For #27854 I was able to reproduce the issue by simply unassigning device from an MDM server, and then assigning back. Once assigned back, Fleet did not resend the profile to ABM, and device was not able to enroll into MDM. # Checklist for submitter - [x] Changes file added for user-visible changes in `changes/`, `orbit/changes/` or `ee/fleetd-chrome/changes`. See [Changes files](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/Committing-Changes.md#changes-files) for more information. - [x] Added/updated automated tests - [x] Manual QA for all new/changed functionality |
||
|---|---|---|
| .. | ||
| android | ||
| apple | ||
| assets | ||
| crypto | ||
| cryptoutil | ||
| internal/commonmdm | ||
| lifecycle | ||
| linux | ||
| maintainedapps | ||
| microsoft | ||
| nanodep | ||
| nanomdm | ||
| scep | ||
| testing_utils | ||
| mdm.go | ||
| mdm_test.go | ||