Inspectors say Intelligent Hub shows no new-mail badge. Which UEM email-stack component should the technician investigate first?
Select an answer to reveal the explanation.
Short Explanation
A missing mail badge is a doorbell problem, not a VPN problem. ENS is the doorbell in the UEM email stack. Tunnel, Help Desk, and DEM do not stamp that Hub count.
Full Explanation
When inspectors say Intelligent Hub shows no new-mail badge, the UEM email-stack component to investigate first is Email Notification Service, which supplies the mail notification and badge path for managed clients. At associate depth, a missing badge on civic phones is treated as a notification-path problem in the Workspace ONE email family before blaming unrelated VPN, VDI help-desk, or Windows environment tools. Workspace ONE Tunnel draws per-app VPN tunnels for managed apps; it does not automatically draw Hub mail badges. Horizon Help Desk assists with VDI sessions and does not badge Hub from session scores. Dynamic Environment Manager writes Windows user-environment settings on Horizon desktops and does not write iOS badge counts to a file share for Hub mail notifications. Exam caveat: also verify mailbox connectivity, Boxer or Hub mail configuration, and user entitlement after ENS health is confirmed—ENS is the named notification component, not the only possible failure point in the whole mail path. Operational check: confirm ENS service health for the tenant or on-prem deployment, send a test civic mail to a known-good inspector device, watch for badge restoration, and only then escalate to Tunnel, Help Desk, or DEM if the symptom is clearly outside notifications.