Hi, I'm new to this community and new to using fleets. I have windows hosts to integrate into MDM, I have activated the integration but the status mdm of the hosts is always "off", can you help me?

Hey @Stefano! Thank you for your interest and drive in trying Windows MDM from fleetdm. A MVP for Windows MDM should be available soon. Can find more information on this article along with setup instructions (you might already have gone through this). Specific to the status you're seeing, believe you might be looking at the "Hosts" page -> "MDM status". This information is pulled from a detail query of the host and extended information from the fleetd client. There is some work being done to make this correct. Can try to support some more use-cases for things you might be running into. Please let us know and thanks again fleet

Thanks for your support, I followed the guide but the MDM status is always "off", so I assume that until the MVP for Windows is released I won't be able to take advantage of the MDM, right?

Greetings @Stefano, there now is a MVP for Windows MDM. This sprint they are removing the "feature flag" and the "not ready for production" wording on docs. Here are some things that Fleet's Windows MDM has with current release (4.41.1), some require Premium Fleet- • Manual enrollment (install fleetd agent, programmatically enrolls to MDM, hosts already part of an existing MDM will not enroll to Fleet) • Automatic enrollment (non-Autopilot and Autopilot, "zero-touch") • Disk encryption and key escrow • Script execution • MDM commands (ex. wipe, restart) Upcoming features, tentative dates (4.42.0), subject to change • OS updates - 2023-12-15 • Custom settings (configuration profiles) - 2023-12-15 • Software installation - 2024-01-05 How are you installing the fleetd agent on your Windows endpoints?

I install it by generating it on the server and then export it and install it on the windows host, for company policy I will continue with the open source version, the agent should take the configuration from the yaml file, but judging by the status of the mdm it seems that I'm wrong somewhere