Skip to content

RDS · /// Remote Desktop Services Load Testing

Right-size RDS host density with measured concurrency.

LoadGen ships an RDP wizard with native session-host discovery — RD Gateway authentication, multi-session host density, logon-storm scenarios. Same scenario engine as Citrix / AVD. €1,099 / week from 50 vUsers.

Multi-session host validationRD Gateway auth capturedLogon-storm scenarios

RDP wizard — RD Gateway · session host density · multi-session.

The Problem

RDS lives on. Capacity planning doesn’t.

Many enterprises still run RDS for specific apps or back-office workflows. The capacity-planning toolchain assumes Citrix or AVD — leaving RDS teams with PsExec scripts and hand-curated spreadsheets.

Native Windows tools don’t scale.

Perfmon, PsExec, and ad-hoc PowerShell scripts can model a few sessions; they don’t model a 500-user logon storm. Capacity claims live on slide decks, not on measured data.

Logon storms surface in production, not pre-prod.

Multi-session host density is fine at steady state — until a Monday-morning logon storm hits. Generic load tools don’t simulate the storm; production discovers it first.

RD Gateway adds an auth tier most tools ignore.

RD Gateway authentication, certificate handling, and gateway PoP routing add latency that generic HTTP samplers miss. Sessions stall before the user even sees an app.

Why LoadGen for RDS

Same engine. RDS-aware authoring.

The same wizard model that captures Citrix HDX and AVD ARM scenarios captures RDS configurations natively — RD Gateway auth, session-host density, multi-session scenarios.

RDP-native session capture

The wizard captures the RDP session, RD Gateway authentication, and multi-session host configuration once — replayed every test, without hand-scripted PowerShell.

Full agents per session host

Per-session Activate / Reset / Kill operations land on every RDS session host — actual host pressure measured, not thread-based abstractions.

Same scenario engine as Citrix / AVD

The .lgs workload runs across RDS, Citrix, AVD, Horizon. One authoring model — useful when planning RDS modernization toward newer VDI stacks.

SUT Monitoring

RD Connection Broker + Gateway counters, bound to every test.

Multi-session host density doesn’t fail in isolation — it fails because the broker is saturated, the gateway is bottlenecked, or the session-host SKU was wrong. SUT Monitoring binds the infra counters to every test execution.

  • RD Connection Broker, RD Gateway, RD Session Host counters bound to every test.
  • Per-host density measured during logon-storm phases.
  • Custom Windows / SQL counters wirable for app-specific signals.
  • Same SUT Monitoring used on Citrix / AVD — consistent infra-observability across stacks.

SUT Monitoring — RDS infra counters per test execution.

Outcomes

What RDS performance testing delivers.

Time to first RDS test

Before

Days

After

Hours

faster
Slot-count accuracy

Before

Estimated

After

Measured

real
Logon-storm readiness

Before

Production-found

After

Pre-prod

shift-left
Sessions per Full agent

Before

40

After

120

+200 %

See it in action

Three operational surfaces for RDS.

RDP wizard

RD Gateway + multi-session host configuration.

Live orchestration

vUsers ramp + logon-storm phase.

Live cockpit

Per-step latency + host density.

Test your RDS host density in 4 hours.

Bring your RDP target URL, RD Gateway, and a workload sketch. We’ll author the .lgs scenario on a call, fire it from Full agents, and show you host density under a logon storm — live.

Questions

Frequently asked.

Does LoadGen support RD Gateway authentication flows?

Yes — the RDP wizard captures RD Gateway authentication, certificate handling, and gateway routing once. Replayed every test without hand-scripted automation.

How is LoadGen different from running PsExec / WinRM load scripts?

Native Windows tools can model a few sessions but don’t scale to logon-storm scenarios at production scale. LoadGen ships per-session Full agents (actual session-host pressure), bound infra counters via SUT Monitoring, and live cockpit visibility — at 50–25,000 vUsers.

Can LoadGen test RemoteApp scenarios as well as full RDS desktops?

Yes. The scenario engine handles both: full-desktop scenarios capture the connection-broker + Windows-session login path; RemoteApp scenarios capture per-app launch and interaction. Both run on the same Full agents.

How does LoadGen measure logon storm capacity?

Spike-phase load profiles simulate Monday-morning logon storms — measured against host-pool density. Per-step latency, broker queue depth, and session-host CPU visible during the storm phase.

What does RDS load testing cost?

€1,099 per week at the 50-vUser tier, scaling to 25,000 vUsers. Same published pricing as Citrix and AVD load testing — no protocol-specific upcharge.

Can we test RDS alongside AVD migration in one engagement?

Yes. The same .lgs scenario runs on RDS, AVD, and Citrix. Useful for organisations planning RDS modernization — baseline RDS, target AVD, compare login latency and host density on one chart.

LoadGen Official Logo