Device management
Mobile device management from enrollment to remote command
Enroll and manage Windows, macOS, Linux, and Android devices from one tenant workspace—policies, compliance, and remote commands (iOS/iPadOS via native Apple MDM, no Infronest app).
Which operating systems can Infronest MDM manage — does it cover iPhones and iPads?
Infronest manages Windows, macOS, Linux and Android. iPhone and iPad are managed through native Apple MDM enrollment (a signed configuration profile and your organisation's own Apple push certificate); there is no Infronest iOS app. What each supported OS can do also differs, because management runs over two channels — a cross-platform agent and the OS vendor's native MDM protocol.
Already live in the product
Running in production today: the MDM dashboard, devices, enrollment, policies, apps, groups, compliance, commands, reports, and settings.
Built around real workflows
Highlights below describe capabilities already present in the protected app behind this page.
- Multi-OS device registry and dashboard KPIs
- Enrollment tokens and QR flows
- Policy and device group management
- Compliance rules and org-wide scans
- Remote commands with audit trail
- Inventory and compliance reports
- Per-tenant module gating (Enterprise)
- Linux and API enrollment for QA
What teams can do here
- Step 1Enable MDM module for tenant
- Step 2Create enrollment token
- Step 3Register or enroll device
- Step 4Assign policy and run compliance scan
- Step 5Queue remote command and review status
How it works
- 01
Enrol devices
Mint an enrollment token or QR code and register Windows, macOS, Linux and Android devices into one tenant workspace. Each device resolves the management channels it actually has.
- 02
Understand its channels
A device is managed over an agent (our software) and/or the OS vendor's native MDM protocol. The platform computes, per device, which commands each live channel can genuinely carry.
- 03
Apply policy and scan compliance
Assign policies and device groups, then run org-wide compliance scans against the rules you set, so drift is visible rather than assumed.
- 04
Send commands honestly
Queue remote commands from the capability list. An action a device cannot truly perform is refused with a reason — for example "requires native MDM enrolment" — instead of being offered and silently doing nothing.
- 05
Support and report
Start an in-app remote-desktop session to Windows, macOS or Linux endpoints via the MeshCentral relay, and pull inventory and compliance reports — all with an audit trail and per-tenant isolation.
A worked example
Say a 250-employee logistics firm enrols 180 Windows laptops, 25 Macs, 15 Linux workstations and 30 Android handhelds into Infronest MDM. On the Windows fleet the console offers lock, wipe, BitLocker and BIOS actions, because the Windows agent genuinely carries them. On the Macs, factory-wipe and true lock light up only on devices that completed native MDM enrolment — an agent-only Mac refuses those buttons with "requires native MDM enrolment", since Apple restricts EraseDevice and DeviceLock to its own protocol. The Linux boxes manage over the agent alone, and the Android handhelds are driven through Google's Android Management API.
Frequently asked questions
See also: Infronest MDM — full product tour · Blog: What is MDM? · Blog: Best MDM software compared · Blog: MDM best practices · Patch management
Security and VAPT for IT teams
Learn more
IT asset management from request to retirement
Learn more
Access control, SSO, and conditional access for every workspace
Learn more
Data loss prevention that closes USB, print and browser-upload leaks
Learn more
Device activity monitoring that starts only after consent is approved
Learn moreManage Windows, macOS, Linux and Android from one console
The full Infronest MDM tour at infronest.com/mdm shows the per-OS capability matrix, remote desktop and policy engine — a platform that refuses actions a device cannot truly perform instead of pretending.
