Horizon, validated past the front door.
LoadGen runs Omnissa Horizon on the generic wizard with full control over connection, display, and workloads. A Full Agent opens each desktop over Blast with the Horizon Client, and the LoadGen add-in on the desktop runs the workload inside the session.
New Load Profile
Select a technology to create a new load profile
Select Technology
Choose the connection technology for your new load profile. Each technology has its own guided wizard.
Omnissa Horizon
Omnissa Horizon. Connection server-based testing for Omnissa environments.
VDI Technologies
Citrix Enhanced - StoreFront / Gateway
Citrix Basic - Direct ICA connection
RDP - Remote Desktop Protocol
Azure Virtual Desktop - Azure Virtual Desktop
Omnissa Horizon - Omnissa Horizon
Web & Automation
Web Testing - Browser automation
Core - Command-line execution
Special Modes
Local Client - Local VDI client
vWorkspace - Dell vWorkspace
The Problem
Horizon doesn’t break at the URL - it breaks under the URL.
Connection Server queues and Horizon concurrency are where Horizon actually bends. Generic probes don’t reach either.
Connection Server bottlenecks hide under "good enough" probes.
A 200 OK on a synthetic check tells you nothing about Connection Server queue depth or vCenter latency under real concurrency.
Generic load tools can’t script Horizon.
Published apps and desktops, RDSH session pools, and Omnissa-specific delivery - generic HTTP-only tools see only the front door.
Capacity plans built without measurement age fast.
Without parity testing across Connection Server tiers, every refresh cycle re-introduces the same right-sizing question - answered the same wrong way.
How LoadGen handles Horizon
Connect · Author · Execute · Monitor.
Four motions on the same scenario engine: author, run, measure, compare.
Connect
Generic wizard with Omnissa technology - Connection Server URL, credentials, and access captured once.
Author
Workload-based scenarios run against desktops and published applications. Connection, display and scenario captured in the same wizard.
Execute
A Full Agent opens each Horizon desktop over Blast with the Horizon Client, and the LoadGen add-in in the desktop image runs the workload inside the session. The previous agent setup stays supported for existing tests.
Monitor
Continuous E2E UX validation alongside Connection Server counters bound via SUT Monitoring - same audit trail as load.
How it works
Omnissa Horizon, tested from inside the desktop.
LoadGen connects to Omnissa Horizon the way your users do. A Full Agent opens each desktop over Blast with the Horizon Client, the workload stays on the Full Agent, and the LoadGen add-in on the desktop carries out each step in your real applications: clicks on named controls, values read and checked, applications started and verified. The add-in talks over the user's own Horizon session, so nothing inside the desktop dials back to LoadGen.
Record the workload in LoadGen Studio from your own management machine: Studio opens the Horizon session itself. The built-in Horizon counter template adds Blast and PCoIP round trips, which the LoadGen Score reads for protocol latency, and your Unified Access Gateway can join the system under test with the Gateway role, so its load is judged in the access tier next to the desktops.
What you set up
The add-in in the desktop image, or pushed from LoadGen, and one allow-list entry where Horizon’s virtual channel security is on.
Nothing dials back
The add-in talks over the user’s own Horizon session. Nothing inside the desktop connects out to LoadGen.
The earlier setup keeps running
Tests on the earlier agent setup keep running, and both setups can run in one test while you move over.
Live · Generic Wizard · Horizon tab
One wizard. Every published target.
Author desktops and published applications on the generic wizard, run on Full Agents, validate against the same AVD scenarios. Horizon stops being a separate tool.
Desktops and published applications
LoadGen opens each published application from the Horizon Client, the way your users start it, and runs the workload inside it, so an application farm is load tested with the same workloads and the same add-in as a desktop pool.
Horizon desktops over Blast with the add-in are available today. Published application support arrives with an upcoming Suite and Platform release: ask us where it stands before you plan a test around it.
Horizon → Platform
Five features. One Horizon practice.
Horizon isn’t a separate tool - it’s the way these five features compose into a single VDI testing and validation loop.
Load Profile Wizard
Generic wizard with Omnissa Horizon support - published apps + desktops authored side by side.
Explore Load Profile Wizard
Agents
Full Agents open the Horizon desktops over Blast, and the LoadGen add-in in the desktop image runs the workload inside each session.
Explore Agents
SUT Monitoring
Bind any Windows performance counter through the Measure & judge step - Connection Server, host, or infra signals correlate with capacity.
Explore SUT Monitoring
End-to-End Monitoring
Continuous Horizon UX validation from the real user perspective - same scenario shape as your load tests.
Explore End-to-End Monitoring
Gateway tier and protocol counters
Add your Unified Access Gateway as the Gateway tier of the system under test, so its load is judged next to the session hosts. Blast and PCoIP round trips come with the built-in Horizon counter template.
Explore Gateway tier and protocol counters
Two focused pages go deeper than this overview: one on monitoring Horizon experience, one on moving off it.
Stop validating Horizon at the URL.
Connect to Connection Server this afternoon. Run a 200-user scenario this week. Resize Horizon on a measurement next quarter.
