A town runs only on-premises Horizon VDI and has no mobile managed mail. Does it need Email Notification Service?
Select an answer to reveal the explanation.
Short Explanation
If the town has no Boxer and no managed mobile mail, it does not need the mail doorbell. ENS lives in the UEM email family. Horizon brokers desktops without it.
Full Explanation
A town that runs only on-premises Horizon VDI and has no mobile managed mail does not need Email Notification Service. ENS belongs to the Workspace ONE UEM email family for managed-mail notifications on clients such as Boxer, not to Horizon VDI brokering. If there is no managed mobile mail path in that civic design, ENS is out of scope and should not be forced into the Horizon bill of materials. ENS is not required for Horizon Connection Server to broker desktops to clerks or call-center agents. ENS does not store Blast protocol events for session troubleshooting. ENS is not the Horizon Cloud Connector used with Horizon Cloud control-plane registrations. Those are separate Horizon and control-plane concepts that a VDI-only town may need without any ENS deployment. Exam caveat: adding Workspace ONE managed mail later can introduce ENS; absence today does not forbid future UEM email—it only means Horizon alone does not mandate ENS on the exam. Operational check: inventory whether any Boxer or managed-mail profiles exist across departments; if the town is Horizon-only, omit ENS from purchasing and architecture diagrams, and keep Connection Server, Unified Access Gateway, and related Horizon components on the VDI checklist instead.