Below is the support article regarding LoadGen Director sessions hanging when starting new AVD Omnissa Horizon sessions:
LoadGen Director Appears Hung During AVD / Omnissa Horizon Session Launch
Issue:
When initiating new AVD or Horizon sessions, the LoadGen “Launching Agent” may appear stuck, causing the session to hang indefinitely.
Cause
This behavior typically occurs due to a failure in establishing a network connection between the VDI Agent (running on the LoadGen VDI host) and the Director. Without this connection, the Director cannot send the workload to the Agent, and the process stalls.
Troubleshooting Steps
- Open PowerShell on the LoadGen VDI Agent host (where the Agent is installed).
While the session is hanging, run:
Test-NetConnection -ComputerName <DirectorHost> -Port 4841- Replace
<DirectorHost>with the actual hostname or IP of your LoadGen Director.
- Replace
- Analyze the result:
- If it succeeds (TcpTestSucceeded = True), the network path is clear.
- If it fails, it indicates a broken or blocked connection from the Agent to the Director.
Resolution
- Check firewalls, proxies, or network ACLs to ensure traffic on port 4841 is allowed from the VDI Agent to the Director.
- Validate network routing between the LoadGen VDI Agent host and the Director (e.g., no DNS misconfiguration or VLAN isolation).
- After ensuring connectivity, retry your workload—LoadGen should proceed past the “Launching” state successfully.
Why It Matters
This stage is critical because the Director must actively communicate with the Agent to hand off workload instructions. Without an open port 4841 connection, the process cannot continue.
Summary
- Symptom: LoadGen “Launching” Agent hangs during session start.
- Check by: Running
Test‑NetConnection -ComputerName DirectorHost -Port 4841. - Fix: Ensure port 4841 connectivity from VDI Agent to Director.
Let us know if you're still experiencing issues after confirming network connectivity—we're happy to assist further!