Instant-clone desktops in the permitting VLAN boot with no IP addresses. Which Horizon third-party dependency is missing?

Instant-clone desktops in the permitting VLAN with no IP addresses indicate missing DHCP on the desktop VLAN so clones can receive addresses. 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: UEM compliance profiles do not assign IP addresses to clone NICs as DHCP. Distractor concept: App Volumes Manager is not the address server. Distractor concept: Workspace ONE Tunnel is not the DHCP service for VDI desktops. Exam caveat: Clones need DHCP (or equivalent IP assignment) on the desktop network—UEM/App Volumes/Tunnel are not that dependency. Operational check: Check DHCP scope on the permitting VLAN, boot a clone, and confirm it receives an address and registers DNS if required. 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: New clone desktops are like new cubicles that need a phone number on day one — DHCP on the desktop VLAN hands out IPs. UEM compliance, App Volumes, and Tunnel do not run the address pool for those VMs.