Boxer on inspector phones should show a badge for new civic mail without keeping a full ActiveSync session open all day. Which component provides that wake and badge path?
Select an answer to reveal the explanation.
Short Explanation
A badge is a doorbell, not a live mailbox hose running 24/7. Email Notification Service rings that doorbell so Boxer can fetch mail under policy. Events SQL, Tunnel, and App Volumes do not badge civic mail.
Full Explanation
Boxer on inspector phones that should show a badge for new civic mail without keeping a full ActiveSync session open all day relies on Email Notification Service (ENS) for managed-mail notifications and badging. ENS provides the wake and badge path so the managed mail client can fetch mail under policy when needed rather than holding a continuous mailbox connection that drains batteries and keeps unnecessary sessions against municipal mail infrastructure. The Horizon Events database stores Horizon broker and session events such as disconnects; it does not drive Boxer mail badges on phones. Workspace ONE Tunnel is a per-app VPN path into civic systems and does not supply mail notification badges. App Volumes Manager manages Windows package attach for VDI or RDSH desktops and has no role in badging civic mail on inspector phones. Exam caveat: ENS notifies; Exchange or the mail backend still stores the mailbox, and Boxer still retrieves messages under UEM email policies—do not treat ENS as a second mail server. Operational check: send a test message to an inspector’s managed mailbox, confirm an ENS-driven badge or notification appears on Boxer or Hub as designed, verify mail content still arrives from the real mailbox server, and confirm ActiveSync is not required to remain connected twenty-four hours a day solely to keep that badge current.