The civic vSphere cluster that holds on-prem Horizon desktop VMs is down. What is true about Horizon availability?
Select an answer to reveal the explanation.
Short Explanation
If the cluster that holds the desks is dark, the broker has empty rooms. On-prem Horizon depends on vSphere for those desktop VMs—UEM, App Volumes, and NSX do not magically host them.
Full Explanation
If the civic vSphere cluster that holds on-premises Horizon desktop VMs is down, Horizon has no desktop VMs to broker until that cluster is healthy again. Connection Server cannot invent desktops without the virtualization platform underneath a self-managed municipal pod. Horizon Connection Server will not instantiate desktops on Workspace ONE UEM until vSphere returns. App Volumes Manager does not become the hypervisor or broker the same pools. Horizon Cloud Control Plane does not automatically fail that on-prem pod over to NSX-T as a substitute hypervisor for local desktop VMs. Exam caveat: Horizon Cloud environments have different control planes, but this stem is about on-prem VMs on a down civic vSphere cluster—do not invent a UEM or NSX failover that restores those local desktop VMs. Operational check: in an outage drill, document that pool launches fail while vSphere is down, restore cluster health first, retest brokering for a clerk pool, keep UEM and App Volumes off the hypervisor-recovery checklist, and brief leadership on the dependency. Keep civic diagrams labeled so help-desk and network teams do not swap these products during incidents. Document the successful test in the municipal runbook for the next change window.