Devices on civic Wi-Fi cannot resolve enrollment and UEM hostnames, so Intelligent Hub never checks in. Which Workspace ONE third-party dependency is that?
Select an answer to reveal the explanation.
Short Explanation
Hub cannot check in if it cannot find the door. Enrollment and UEM hostnames have to resolve on civic Wi-Fi — DNS is the Workspace ONE dependency. SQL events, PCoIP firmware, and NSX T0 are the wrong stack.
Full Explanation
Workspace ONE device enrollment and callbacks require DNS resolution of UEM and related hostnames (including AirWatch Cloud Messaging-style endpoints) from the networks devices use. A DNS failure presents as Hub never checking in even when the SaaS tenant is healthy. SQL Server events databases, PCoIP firmware, and NSX Tier-0 gateways are not that Workspace ONE dependency.