A 311 agent's Horizon session feels sluggish and Task Manager inside the desktop shows high CPU. Where should the operator look first for per-session performance?
Select an answer to reveal the explanation.
Short Explanation
High CPU inside a VDI session is a noisy copier in one cubicle, not a cluster fire alarm. Open Horizon Help Desk or the dashboard for that agent's session CPU, protocol, and latency. vCenter HA, NSX cookies, and Carbon Black isolate are different errands.
Full Explanation
Per-session performance — CPU, memory, protocol, and latency — is a Horizon dashboard and Help Desk monitoring task. vCenter HA admission control protects host failover; it is not the first click for one sluggish 311 session. NSX load-balancer persistence and Carbon Black isolation are sibling-product consoles, not Horizon session metrics. Start with Help Desk on that user, then escalate if the host really is in trouble.