Skip to lesson
Exit
Fleet, MDM & Device Trust Deep Dive1 / 4

1 min lesson

Mixed-platform fleet management

Tell someone how to act on this idea: "Cursor's fleet is not one OS."

Step 1 of 4

Cursor's fleet is not one OS. The JD calls out macOS, Windows, Linux and ChromeOS by name and the fastest way to look junior is to be a single-platform admin who treats the other three as someone else's problem.

Each OS exposes a different management surface, so there is no single tool that does all four well. The skill is knowing where to unify and where to specialize: unify the intent (the compliance baseline every device must meet) and specialize the mechanism (the per-OS tooling that enforces it).

Learn more

Advanced table

Three of the four have a real MDM story

OS
macOS
Management primitive
Apple MDM protocol + profiles + scripts
Typical tooling
Kandji, Jamf
Where it gets hard
Keeping up with Apple's yearly changes and the shift to declarative device management
OS
Windows
Management primitive
Windows MDM/CSP + (sometimes) GPO
Typical tooling
Intune, partner MDM
Where it gets hard
Legacy GPO/AD overlap and a deeper, messier policy surface than macOS
OS
ChromeOS
Management primitive
Cloud policy via Google Admin
Typical tooling
Google Admin console / API
Where it gets hard
Genuinely simple - the risk is forgetting it exists in your posture model
OS
Linux
Management primitive
Config management + agents (no true MDM)
Typical tooling
Ansible, osquery, Fleet, MDM-lite
Where it gets hard
Heterogeneous distros, sudo/root realities and no force-enroll equivalent

Three of the four have a real MDM story; Linux you manage like a server fleet, which is a feature if you already think in config management.