GIS examiners need GPU-backed Horizon desktops for parcel maps. Where does that special desktop hardware live?
Select an answer to reveal the explanation.
Short Explanation
The GPU is a seat in the hypervisor, not a checkbox on a phone MDM profile. GIS desktops get graphics because vSphere hosts the VM with a vGPU or graphics profile. DEM printers and UAG encoding are not that hardware.
Full Explanation
GIS examiners who need GPU-backed Horizon desktops for parcel maps get that special desktop hardware on the vSphere hypervisor that hosts the desktop VM, typically as a vGPU or graphics profile. Graphics acceleration for municipal GIS is a host and VM hardware profile concern on the civic cluster, not a phone MDM setting or a DEM printer mapping trick. A Workspace ONE UEM MDM profile that installs a GPU driver on phones does not create GPU-backed Horizon Windows desktops. Dynamic Environment Manager does not map a GPU as if it were a printer. Unified Access Gateway encodes and proxies display protocols but does not replace host GPU resources required for GIS workloads inside the guest. Exam caveat: UAG and protocol choices affect remote display efficiency, but the GPU itself is still provisioned on the vSphere host for the desktop VM that runs the parcel-map software. Operational check: confirm the GIS pool’s VMs have the intended vGPU or graphics profile in vCenter, launch a parcel-map workload that stresses graphics, verify UEM profiles and DEM settings were not used as the GPU source, and update the GIS desktop standard build document. Keep civic diagrams labeled so help-desk and network teams do not swap these products during incidents.