What Enrollment Troubleshooter helps you do
When Device Triage (or an enrollment UI) points at join/MDM trouble, this specialist classifies Entra join, MDM enrollment, Autopilot/ESP, session, cancel, timeout, blocked, and network failures from a HRESULT, diagnostics JSON, or MDM log excerpt — then explains likely cause, check-next steps, and why.
Check the tool page and Privacy Policy for how this workflow handles your input.
How to use Enrollment Troubleshooter
- Paste an enrollment HRESULT, MDM log excerpt, or diagnostics JSON, and choose a path hint when known.
- Run Troubleshoot and review the classified issue, likely cause, and check-next steps.
- Deep-link HRESULTs into Error Code Explorer with enrollment context when you need broader code lookup.
What you can do with Enrollment Troubleshooter
- Accept enrollment HRESULTs, dsregcmd/MDM log excerpts, and haivix-device-diagnostics.json.
- Classify not-joined, not-enrolled, already-enrolled, blocked, session, canceled, timeout, Autopilot/ESP, and network issues.
- Honor enrollment path hints (Autopilot/ESP, Company Portal, Access work or school, bulk).
- Deep-link HRESULTs into Error Code Explorer with enrollment context.
- Keep all analysis browser-local — logs and JSON never upload to Haivix.
Example: 0x80180014 already enrolled
Paste 0x80180014 or the MDM lines that mention already enrolled, choose Access work or school if known, then run Troubleshoot.
Follow Check next to clear leftover enrollment state, then re-attempt enrollment or return to Device Triage for a fresh snapshot.
What to know before you start
- This is not a full Autopilot forensic suite — it prioritizes teachable classification for Tier 1/Tier 2.
- Forced Issue kind overrides auto-detect when you already know the failure mode.
- Always confirm guidance against dsregcmd, Autopilot profiles, and MDM Admin events.