Load test Remote Desktop Services and RemoteApp the way users work—from the RDP client GUI—not as an HTTP hit on RD Web.
Direct answer: Microsoft RDS (Remote Desktop Services) load testing is not Amazon RDS and not a portal-only exercise. RDP delivers pixels. The best 2026 approach measures on-the-glass logon, app open, and in-session UX under a logon storm and a sustained density run. CitraTest VU® drives the real client path (RD Web / RD Gateway → collection → RemoteApp or desktop) with image recognition and no agents on your session hosts.
What “best” means for RDS
- Real connection path — RD Web or RD Gateway, auth/MFA, collection, RDP, profile/GPO, then RemoteApp or desktop
- Logon storm vs density — steep morning ramp separate from sustained concurrent users on RDSH
- Host and profile limits — CPU, memory, and profile IOPS that break before the protocol does
- Tails that a CAB can defend — p95/p99 logon and app-open, not only averages
Approach comparison
| Approach | What it measures | RDS fit | Limit |
|---|
| RDP / protocol scripting |
Session connect metrics |
Partial infra signal |
Can miss slow RemoteApp UX |
| HTTP against RD Web |
Portal pages |
Weak for session hosts |
RDP is not HTML |
| On-the-glass / RUX (CitraTest VU) |
What the user sees under load |
Strong for RDSH / RemoteApp |
Scripts the real client path |
| Ongoing APM (CitraTest APM) |
Synthetic paths in production |
After go-live |
Complements capacity tests |
Logon storm vs session density
A logon storm stresses the auth, profile, and first-paint path with a steep concurrent ramp. A sustain holds target concurrent users and watches whether RemoteApp stays usable. Mixing them hides whether you failed on morning logon or on mid-day density. See also Tevron’s notes on logon storm vs density.
Recommended stack
How to load test Microsoft RDS (checklist)
- Freeze the RDSH / RemoteApp image and decide Gateway vs lab shortcut.
- Script the real workday from the RDP client GUI.
- Baseline a single user on the glass.
- Run a logon storm separately from a sustain density test.
- Watch p95/p99 tails, fail rate, and per-host CPU/memory/profile IOPS.
- Stop at a concurrent-user line the collection can keep.
- Re-test after image, GPO, FSLogix/profile, or Broker changes.
Detail: How to Load Test Microsoft RDS. Related: Citrix tools, cloud VDI/DaaS, measure RDS response time, cloud tools answer page.
FAQ
How do you load test Microsoft RDS?
From the real RDP client path, measuring on-screen logon and app readiness under storm and sustain—not by hammering RD Web alone.
Is this Amazon RDS?
No. This page is about Microsoft Remote Desktop Services (session hosts / RemoteApp), not Amazon Relational Database Service.
Can web load tools test Remote Desktop?
They can exercise RD Web over HTTP. They do not replace concurrent RDP session and in-app UX testing on RDSH.
Protocol testing vs real-user testing for RDP?
Protocol can show a connected session while the app is still painting. On-the-glass timing is what users and SLAs feel.
CitraTest VU vs CitraTest APM for RDS?
VU proves capacity and UX under load. APM watches synthetic real-user paths after go-live.
CitraTest VU® and CitraTest APM® are Tevron products for EUC performance testing and monitoring, including Microsoft RDS, RemoteApp, Citrix, and cloud-hosted sessions.