Front-counter kiosks in the licensing lobby have no local Windows OS; dedicated firmware speaks Blast or PCoIP only. Which VDI client type is that?

Front-counter kiosks with no local Windows OS and dedicated firmware speaking Blast or PCoIP only are zero clients. 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: A fat client has a full municipal Windows image—opposite of firmware-only. Distractor concept: A thin client runs a minimal OS plus Horizon Client; that is not firmware-only. Distractor concept: Workspace ONE Boxer is a mail client endpoint concept, not a VDI zero client. Exam caveat: No general-purpose OS, protocol firmware only = zero client; thin still has an OS. Operational check: Inventory the lobby units: confirm firmware-only protocol stack and no local Windows/Linux OS image to patch as a PC. 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: A zero client is a puck that only knows how to talk display protocol — firmware, not a little Windows box and not a full PC. If a local OS and Horizon Client are installed, that is thin, not zero. Boxer is the Workspace ONE email app, not a kiosk class.