Building-department plans examiners need AutoCAD-class GPU locally and must work disconnected in a job-site trailer. Which client type fits?

Plans examiners needing AutoCAD-class GPU locally and disconnected trailer work require a fat Windows PC that runs local apps and can also run Horizon Client when online. 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 zero-client puck with PCoIP firmware only cannot run local CAD offline. Distractor concept: A thin client that only launches Horizon Client fails without the WAN/session. Distractor concept: Unified Access Gateway does not belong in the trailer as the client type. Exam caveat: Offline + local GPU/heavy apps = fat client; zero/thin need connectivity to the desktop. Operational check: Provision trailer fat PCs with local CAD and Horizon Client, and test a disconnect scenario before field use. 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: When the work has to survive a dead WAN and needs a real GPU on the desk, you hand out a fat PC — a full Windows box that can still fire up Horizon Client later. A zero or thin box is helpless offline, and UAG does not belong in a trailer.