LALITE — AUTOPILOT ESP EVIDENCE CHECKLIST
Updated 10 September 2026
Guide: https://lalite.org/school-it-guide/intune/autopilot#esp-walkthrough

Use for classic Windows Autopilot and ESP. Record evidence before a reset.

Incident / date / technician:
Device serial / model / Windows version:
Deployment method / intended tenant / profile:
Affected scope / known-good comparison:

[ ] Exact stage, error code and timestamps captured.
[ ] Registration and assigned profile checked by the authorised owner.
[ ] Network, time and relevant service status checked.
[ ] ESP profile, timeout and blocking-app list recorded.
[ ] Available diagnostics collected into an approved restricted location.
[ ] App identifier matched to device installation and detection evidence.
[ ] Requirements, dependencies, install context and return codes checked.
[ ] Proposed correction, owner, pilot and rollback recorded.
[ ] Intended deployment retested on authorised pilot hardware.
[ ] Required apps work; intended user, management and access checks pass.

Finding / evidence location:
Approved action / owner / result:
Remaining issue / escalation owner / next update:

Do not import diagnostic registry dumps. Do not publish logs containing user
or device identifiers. Desktop access alone is not acceptance evidence.
Primary sources and the worked example are linked in the full guide.