Skip to content
Remote Desktop Services · /// Multi-session

Validate RD Gateway, slot counts, and logon storms — before Monday morning.

LoadGen ships a dedicated 8-step RDS wizard with native RD Gateway support. Full agents (port 4840) drive every multi-session desktop with batch Logon / Logoff / Lock / Unlock / Reboot / Reset operations.

/New RDP Profile
Mode: Basic Online
AD
admin
Administrator

New RDP Profile

Step 1: Set profile name and basic settings

Remote Desktop Protocol
Basics
Users & Agents
Connection
Gateway
Display
Scenario
Advanced
Review

Profile Basics

Configure the basic settings for your RDP load profile.

A unique name to identify this profile

Profile is active

Enable or disable this profile

Test User
Workload
LoadGen Agent
RDP Host
Session
© 2026 LoadGen. All rights reserved.  |  v1.0.0.11771
DocumentationSupportCreate Ticket

The Problem

RDS isn’t boring — it’s under-tested.

Multi-session is mature, which is exactly why teams stop measuring it. The questions auditors ask about Gateway capacity and slot counts are answered by guessing.

RD Gateway is a single point of failure nobody load-tests.

Without measured Gateway throughput under real concurrency, the first time it bends is on Monday morning when the whole field engineering team logs in.

Multi-session farms run on outdated slot estimates.

Slot counts authored years ago, never re-validated against current Office or line-of-business apps — silent overshoot, silent undershoot.

Logon storms surface in production, not in pre-prod.

A 30-user pilot proves nothing about an 800-user 9 a.m. logon storm. Without measured ramp on the actual farm, the storm hits prod first.

How LoadGen handles RDS

Connect · Author · Execute · Validate.

Four motions, every one RDS-aware — from the Gateway URL down to the per-host slot count.

Connect

The 8-step RDS wizard ships with native RD Gateway support. Auth, gateway URL, and farm membership captured in minutes.

Author

Workload-based scenarios map to multi-session desktops. Display, scenario, and Full-agent strategy authored in the same wizard.

Execute

Full agents (port 4840) drive every session — Logon, Logoff, Lock, Unlock, Reboot, Reset, Install, Uninstall as batch ops on the farm.

Validate

Per-host slot saturation, Gateway throughput, and continuous E2E UX monitoring tracked on the same audit trail as the load test.

Live · 8-step RDS Wizard

Gateway-aware. Multi-session-aware. Slot-aware.

Author once, run on the farm, validate the slot count against measured concurrency. The wizard captures every RDS-specific signal — Gateway, broker, host pool, session.

RD Gateway support
Native gateway auth, public-facing URL, internal farm address — captured once, replayed everywhere.
Multi-session orchestration
Logon, Logoff, Lock, Unlock, Reboot, Reset land per-session — Full agents handle every batch op on the farm.
Slot saturation
Per-host slot counts measured against actual Office / LOB workloads — silent overshoot becomes loud measurement.
Continuous UX validation
E2E Monitoring re-runs the same scenario between releases — drift surfaces before users notice.

Outcomes · before / after

Right-size the farm. Survive the logon storm.

Drawn from teams that ran the dedicated RDS wizard against real concurrency before the next refresh cycle.

Time to first RDS test

Before

6 days

After

4 hrs

−97 %
Slot count accuracy

Before

±35 %

After

±5 %

−86 %
Logon storm incidents / qtr

Before

4

After

0

zero
Sessions tested per Full agent

Before

40

After

120

+200 %

Test the farm before Monday tests it for you.

Run the 8-step RDS wizard this afternoon. Capture a Gateway throughput baseline this week. Resize the farm on a measurement next quarter.

LoadGen Official Logo