Technical · Course T4Lesson 3 of 3
Verify, tag, and troubleshoot
6 min read- Verify enrollments and what "done" unlocks
- Use tagging and know where Azure AD integration lives
- Run the troubleshooting playbook for the four common failures
Enrollment ends with verification, not installation. The routine takes two minutes per batch and catches the stragglers while you're still on site.
Verify
In Devices, filter by Windows and confirm each machine shows Online/Active. Enrolled devices immediately have: the agent running, assigned policies applying, and WeSupport remote assistance available — which, incidentally, is the best "it's working" demo you can give a customer: enroll, then remote-view the machine thirty seconds later.
Tag
The Tagging tab manages device tags — the organizational layer you'll want before the fleet grows. Tag by site, department, or hardware batch at enrollment time; bulk operations and filtered views downstream all key off tags, and retro-tagging five hundred machines is nobody's favorite afternoon.
Azure AD
The third tab wires Azure Active Directory integration for directory sync. If the customer runs Entra/Azure AD, this is where that conversation lands — set it up early so identity and device records line up from day one.
The troubleshooting playbook
Four failures cover nearly every Windows enrollment ticket:
- URL won't generate — Windows platform not enabled in Settings → Platform, or a permissions gap. Enable, refresh, retry.
- Installers "unavailable" — they're still building after first setup; the countdown timer says how long. Refresh after it expires.
- Device missing from the list — give it 2–3 minutes, confirm connectivity, restart the WeGuard agent service, and confirm the edition isn't Home.
- No "Open" prompt in the browser — wrong browser. Edge (or IE11) only; paste the URL directly into Edge's address bar.
Plus the PPKG pair from last lesson: package at USB root, USB in before the network screen.
The trilogy, complete
With this course you've now got all three platforms' enrollment stories — Android's ownership×scale framework, Apple's trust chain, and Windows' URL-or-installer simplicity. That's the foundation every technical deployment conversation stands on.