A Lakeside library patron uses HTML Access in the kiosk browser to reach a catalog desktop and the session fails. Which log family should the operator treat as the first collect?
Select an answer to reveal the explanation.
Short Explanation
HTML Access is still a Horizon Client—just the browser flavor. A kiosk that cannot open a catalog desktop needs that web-client log family, not Boxer mail logs from a phone in the staff room.
Full Explanation
When a Lakeside library patron uses HTML Access in the kiosk browser to reach a catalog desktop and the session fails, the first log family to collect is Horizon HTML Access or web client logs in the Horizon Client family on that kiosk. The failing component is the browser-based client path to the broker. Library kiosks locked to browsers depend on HTML Access logging discipline so staff do not wipe Content lockers while chasing a web-client broker error. Workspace ONE Boxer logs from a staff iPhone in the back office cannot explain a patron HTML Access failure on the kiosk. App Volumes Agent logs stored on the Horizon Connection Server are the wrong location and wrong symptom focus for a web-client launch failure. Workspace ONE Content locker logs for the library PDF collection address file sync, not HTML Access session setup. Exam caveat: HTML Access is still a Horizon client path; collect its web-client logs rather than mobile productivity or unrelated App Volumes artifacts. Operational check: On the failing kiosk, gather HTML Access or web client logs per documentation for the session attempt, and confirm the broker URL and entitlements before expanding collection. Keeping the civic evidence trail tied to the failing component also reduces cross-team handoffs that delay public services.