Assessors use Windows laptops, a few Macs, city iPads, and a browser kiosk in the lobby to reach the same Horizon desktop pool. What should the technician know about Horizon Client?

Assessors who use Windows laptops, a few Macs, city iPads, and a browser kiosk in the lobby to reach the same Horizon desktop pool illustrate that Horizon Client is a multi-platform family: native clients for Windows, macOS, and mobile, plus HTML Access in a browser, while some zero clients embed the protocol in firmware instead of installing a store client. Horizon Client is a family, not a single Windows MSI. The claim that Horizon Client exists only as a Windows MSI and that Macs and phones must use Intelligent Hub as the protocol fails by concept: Hub is not the display protocol, and native Horizon clients exist beyond Windows. Calling HTML Access a Workspace ONE UEM feature and not a Horizon client type fails because HTML Access is the browser-based Horizon client experience, not a UEM enrollment feature. Requiring zero clients to install the full Horizon Client from the public store before Blast will start fails because many zero clients already speak Blast or another protocol in firmware and never visit an app store. Exam caveat: platform coverage and HTML Access matter for civic lobbies and mixed fleets; choosing the wrong client type (or forcing Hub to be the protocol) is a common associate mistake. Operational check: connect to the same pool from a Windows Horizon Client, a Mac client, a mobile client, and HTML Access in the lobby browser, and confirm a zero client can connect via embedded protocol without a public-store Horizon Client install.