Mock MDM
A device management connector that implements every MDM capability and talks to nothing.
| Category | MDM |
| Authentication | API token, unused |
| Reaches | Nothing |
| Needs an agent | No |
Capabilities
Section titled “Capabilities”device.lookupBySerial, device.get, device.listForUser,
device.applyPolicy, device.sendCommand, device.searchSerial,
device.listGroup
It implements the full MDM surface, so every feature that depends on an MDM behaves as though one is connected.
What it is for
Section titled “What it is for”Demonstrations where you want the device screens populated without wiring up a real MDM.
Training environments where technicians should practise sending a wipe command without a wipe happening.
Testing the product’s own behaviour, which is its original purpose.
Configuring it
Section titled “Configuring it”Admin, Connectors, Mock MDM, Configure.
| Field | Value |
|---|---|
baseUrl | Anything. It exists so the configuration form has something in it |
apiToken | Anything |
The test connection always succeeds.
When not to use it
Section titled “When not to use it”Never in production. A mock MDM in a live deployment means technicians see device data that is not real and send commands that do nothing, with no indication that either is happening.
If you want realistic data for a demonstration, prefer the demo mode on a real connector. It returns fixture data through the real code path, so what you are demonstrating is closer to what the school will actually get. Demo mode is also counted on the compliance page, so it gets noticed and turned off.
The mock connector is for the cases where you deliberately want no vendor at all.
Alternatives
Section titled “Alternatives”For anything real: Jamf Pro, Intune, Kandji, Mosyle, Chrome Enterprise.