Fleet version: 4.65.0, Orbit 1.40.1
Web browser and operating system: Tested with Windows 11 -> Ubuntu 24.10
💥 Actual behavior
An end user has a Fleet enrolled Windows host with MDM turned on. Then they decide they want to use Linux for work so they re-enroll to Fleet as a Linux host. When this happens, the host's MDM details are not cleared out. This causes issues for reporting where it appears the Linux host is enrolled in Windows MDM, when it is not. The other host details are updated to accurately reflect the new OS details.
🧑💻 Steps to reproduce
- Enroll a Windows host into Fleet with MDM turned on. Make sure MDM server details populate on the host's details page.
- Install Ubuntu on that same host and enroll it into Fleet. Do not erase the host record from Fleet!
- Observe that that the existing host record has been updated to reflect that host is now running Ubuntu. The MDM Status and MDM server URL still show the host is enrolled in Windows MDM, which is not correct.
🕯️ More info (optional)
🛠️ To fix
Product designer: marko-lisica
When end users switches from Windows to Linux...
- The Linux hosts re-enrolls (fleetd is installed)
- Clear MDM status and MDM server URL
Fleet version: 4.65.0, Orbit 1.40.1
Web browser and operating system: Tested with Windows 11 -> Ubuntu 24.10
💥 Actual behavior
An end user has a Fleet enrolled Windows host with MDM turned on. Then they decide they want to use Linux for work so they re-enroll to Fleet as a Linux host. When this happens, the host's MDM details are not cleared out. This causes issues for reporting where it appears the Linux host is enrolled in Windows MDM, when it is not. The other host details are updated to accurately reflect the new OS details.
🧑💻 Steps to reproduce
🕯️ More info (optional)
🛠️ To fix
Product designer: marko-lisica
When end users switches from Windows to Linux...