Harborview library Blast sessions drop only on one thin-client model; other models and fat clients stay connected to the same catalog pool. Which logs should the operator collect first?
Select an answer to reveal the explanation.
Short Explanation
When only one thin-client model blinks off, start at that model's Horizon Client, not at a healthy desktop everyone else is already using. Endpoint-specific display drops are a client-log problem first.
Full Explanation
A Blast failure isolated to one thin-client model points to the Horizon Client stack, firmware, or protocol path on that endpoint. Collect Horizon Client logs from a representative unit of the failing model before assuming the catalog pool's Horizon Agent is broken. Agent logs from clones that other models use successfully do not explain a model-specific drop. Intelligent Hub and Workspace ONE Web logs belong to UEM productivity apps, not native Horizon Blast on a thin client.