Turning off Windows MDM fails to unenroll existing devices #24209
Labels
~backend
Backend-related issue.
bug
Something isn't working as documented
#g-mdm
MDM product group
:incoming
New issue in triage process.
~released bug
This bug was found in a stable release.
Fleet version:
4.59
Web browser and operating system:
N/A
💥 Actual behavior
Turning off Windows MDM should unenroll devices from Fleet's MDM. As part of my test for Windows migration, I noticed that it failed to do so.
🧑💻 Steps to reproduce
You should see logs like this:
🕯️ More info (optional)
This is likely because the Windows MDM management endpoints are wrapped in a middleware that checks if Windows MDM is enabled, but at the point in time when hosts try to unenroll, Windows MDM has been turned off so the fleet server rejects the request due to MDM not being enabled:
fleet/server/service/handler.go
Lines 929 to 950 in 317b94b
The text was updated successfully, but these errors were encountered: