Jamf School: investigate completed MDM commands
How do you investigate a profile that appears installed but does not deliver the expected result? The Jamf School update of November 2, 2026 provides another starting point. This is Underside’s proposed method for connecting a command, the observed device outcome and a support decision, without treating a technical history as proof of compliance.
1. The scope confirmed by Jamf
The official notes introduce Management History (Beta), with limited availability. In device details, this category shows commands completed over the past 90 days: type, details, queue and completion timestamps, and status. Filters cover type, status and completion date. First check that your environment has access; this announcement does not concern Jamf Pro.
2. Start with a question you can test
Our recommendation: open a ticket with one expected outcome, for example “the pilot configuration profile should be present on this iPad”. Record the device identifier in your internal tool, the expected profile, the time range and the time zone used. Avoid another fleet-wide distribution until you understand the initial result.
If the beta is available, find the relevant command and record its status and timestamps. If no entry matches, do not automatically conclude that it failed: your search covers completed commands within a limited window. Review the distribution scope and continue troubleshooting with the tools available.
3. Separate technical execution from service delivery
We suggest documenting two separate checks. First, what does command tracking report? Second, does the device actually have the expected configuration and behave as intended? For a pilot Wi-Fi profile, test an authorised connection to the intended network and record the outcome. A command status alone is insufficient to validate business access.
- Expected outcome: record the verified configuration and usage test.
- Failure: retain the observed status and context before another targeted attempt.
- Ambiguous outcome: compare against a reference device and request support analysis instead of repeating actions.
4. A useful record for Belgian and French organisations
For an IT team spanning sites in Belgium or France, we recommend a shared format: ticket, device, command, profile, timestamps with time zone, status, local observation, owner and next action. This record supports handovers between French- and English-speaking teams, institutions and service providers. Limit shared data to what the incident requires, following your internal rules.
Businesses using another MDM can adopt this correlation method but must check the capabilities of their own console. The documented feature remains specific to Jamf School; it does not extend Apple Business Manager or Jamf Pro.
5. Underside analysis: make evidence part of support
Our interpretation is operational: use this history as one part of the diagnostic record. We recommend defining who verifies the device outcome and who authorises another attempt. For a small business, a short record may suffice; for a large organisation or public administration, connect it to change management and support escalation.
This guide complements our analysis of Jamf School access changes. To structure fleet management, see our pages on Apple for business in Belgium and Apple for business in France.
Official sources : Jamf School Release Notes — 2026-11-02 · Device Management History (Beta).