Jamf PreStage: validate the first startup of Apple devices
A zero-touch deployment is judged by the journey employees actually experience. The new Jamf PreStage settings provide a starting point for documenting first-startup screens and checking that a simpler journey preserves IT controls.
1. The verified change in Jamf Pro 11.33.3
In its 29 October announcement, Jamf adds a Liquid Glass setting to computer and mobile device PreStage enrolments to skip that screen during Automated Device Enrollment. The Device Features Tour setting also skips the feature tour on mobile devices. This announcement does not provide a detailed matrix of compatible operating system versions: check the notes and the availability of the settings in your environment before the pilot.
2. Prepare a first-startup matrix
We recommend a worksheet for each journey: model, operating system version, Jamf version, PreStage, MDM assignment in Apple Business Manager, network and target population. Record the expected behaviour, observed behaviour and acceptance decision for each screen. Keep a baseline before making changes so you can isolate the effect of the setting under test.
3. Test one change at a time
On a test device authorised for erasure, compare the baseline journey with the journey using the candidate setting. Record the screens actually displayed, interventions required and time until a validated business task can be completed. Repeat with the operating system versions in your fleet; a result on one model does not validate every other model.
4. Check the controls after the screens
Our proposed acceptance checks cover MDM enrolment, the expected identity, installation of essential applications and access to a business resource. On Mac, add FileVault and SSO checks if those features form part of your architecture. Test Wi-Fi and certificates under actual delivery conditions. These are Underside recommendations, rather than regressions reported by Jamf.
5. What this changes for a Belgian or French organisation
For an SME, a short worksheet and a pilot device for each representative journey can structure device handover. A mid-sized organisation, large enterprise or public administration should organise acceptance by population, site and business dependency. For teams spread across Belgium, France and other European countries, we recommend common criteria and instructions adapted to user languages and local support teams.
6. Underside analysis: simplify while retaining evidence
Our view is that removing a screen is useful only if the employee reaches a working device and IT can explain the outcome. Separate three criteria: the displayed journey, effective management and business access. Each requires its own validation. A fast journey that subsequently requires manual intervention should remain visible in the pilot results.
7. Prepare rollout and exceptions
Before extending the setting, have the MDM owner and support team approve the worksheet. Define an acceptable failure threshold, an escalation owner and a tested alternative journey. If a discrepancy occurs, pause the affected wave and compare the model, system, network and PreStage against the baseline. Archive the result without capturing passwords or unnecessary personal data.
Apple onboarding and inventory · Jamf MDM
Recommendation: validate a screen matrix and evidence of a completed business task before rollout. Underside, an Apple Business Partner, supports organisations in Belgium, France and Europe with Apple Business Manager, Jamf and device lifecycle management.
Prepare your deployment acceptance planSource: Jamf — Jamf Pro 11.33.3 Now Available (2026-10-29).