The city is standing up Horizon Connection Server for 311. What third-party OS dependency still exists?

Horizon Connection Server for 311 still depends on a supported Windows Server build; Horizon does not replace that OS, and NSX Manager or UEM SaaS is not the OS that hosts Connection Server. In municipal EUC terms, treat the endpoint as a window into city systems when the architecture says so, not as the system of record for the files or apps in the stem. Distractor concept: Horizon does not eliminate the Windows Server OS license/requirement. Distractor concept: NSX Manager is not the operating system hosting Connection Server. Distractor concept: Workspace ONE UEM SaaS is not the OS for Connection Server. Exam caveat: Connection Server = application on Windows Server; remember the OS dependency. Operational check: Verify Connection Server VMs run a supported Windows Server build and patch that OS on the municipal schedule. Record the chosen control and the rejected failure modes in the civic change ticket or runbook so on-call staff and auditors share the same rationale after the next maintenance window. Re-validate after personnel or image changes that the same control still meets the city's continuity, security, and support expectations for this service. Helpdesk coaching tip aligned to the conversational brief: Connection Server is an application you drop onto Windows Server, not a magic appliance that retires the OS. The city still needs a supported Windows Server build. NSX Manager and UEM SaaS are different products, not the broker's host OS.