Discharge7443/fleet
1
0
Fork 0
Code Issues Pull Requests Actions 5 Packages Projects Releases Wiki Activity

Guide update: Unenroll Windows hosts (#37366)

Browse Source 
We were telling users they had to turn off Windows MDM features for all
hosts to turn off MDM for one Windows hosts
This commit is contained in:
Noah Talerman
2026-01-09 10:06:36 -05:00
committed by GitHub
parent fc03dacc95
commit a3c55d936c
1 changed files with 6 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
articles/enroll-hosts.md
+6 -5
View File
@@ -138,15 +138,16 @@ In the Google Admin console:
### Unenroll
You can unenroll a macOS, Windows, or Linux host from Fleet (iOS, iPadOS, and Android hosts coming soon).
1. Determine if your host has MDM features turned on by looking at the **MDM status** on the host's **Host details** page.
2. For macOS hosts with MDM turned on, select **Actions > Turn off MDM** to turn MDM off. For Windows hosts with MDM turned on, follow the [instructions for turning off MDM](https://fleetdm.com/guides/windows-mdm-setup#turn-off-windows-mdm). For iOS, iPadOS hosts with MDM turned on, select **Actions > Turn off MDM**.
2. If MDM is turned on, for macOS, Windows, iOS/iPadOS, and Android hosts:
- For macOS hosts, select **Actions > Turn off MDM** to turn MDM off.
- For Windows hosts, download and run the [turn off MDM script](https://github.com/fleetdm/fleet/blob/main/it-and-security/lib/windows/scripts/turn-off-mdm.ps1) on the host.
- For iOS/iPadOS and Android hosts, select **Actions > Unenroll**.
4. For macOS, Windows, and Linux hosts [uninstall fleetd](https://fleetdm.com/guides/how-to-uninstall-fleetd).
3. Next, for macOS, Windows, and Linux hosts [uninstall fleetd](https://fleetdm.com/guides/how-to-uninstall-fleetd).
5. Select **Actions > Delete** to delete the host from Fleet.
4. Last, select **Actions > Delete** to delete the host from Fleet.
> If an end user wants to switch their workstation's operating system (e.g. Windows to Linux), before they switch, delete the host from Fleet. Then, re-enroll the host.