Wizard
Troubleshoot
Deployment Guides
Error Codes
Click any guide to open the full installation documentation for that platform and MDM.
Answer three quick questions, then start from what the user is seeing.
127.0.0.1:8080. Activity Monitoring only → no tray icon, and that’s expected. Mixing these up is the most common false problem report.Pick a platform and MDM to break the deployment into its stages. Each stage lists what to verify and the problems that surface there — with likely cause and fix.
Look up a code a user reads off the Status page, toolbar popup, or a Report a Bug submission. Each code tells you the fault domain, who owns the fix, and what to check first.
catalog.ts). The Route and What to check guidance is inferred by the SSE team and flagged for Engineering review. Users only see the code and the generic message — don't read the support meaning back to a district as a confirmed cause until you've checked.MACG-3390MACG-3391MACG-2908). MACG-3392C-104, C-106, C-107, S-110, A-108) are unused, and E-500 is not a live code in the Chrome catalog. If a user reports a code that isn't listed here, collect a Report a Bug submission and escalate — it may be newer than this page.Policy answers live in the S band. S-105, S-106, S-109, and S-112 aren't server failures — the service answered correctly that this user or device isn't entitled. They're tagged Policy / config here so they route to a district or account settings change rather than to Gaggle engineering. The PI-893 brief recommended a separate P-1xx band for these.
Catch-all. The PI-893 brief proposed E-500 as an unknown-error intake that carries the raw error through. It isn't in the shipped Chrome catalog, so unmatched failures may show no code at all.
Still open: what the Windows Agent will show once MACG-2908 ships, and where district-facing documentation for the M codes will live.
Generate MDM configuration profiles and managed Plist files for your deployment.