Latency first: no amount of tuning fixes distance. RDP feels local under ~40ms — which is why the desktop experience starts with a node in the same country. Within a metro, our Delhi NCR and Mumbai nodes put most users in the ~5–30ms band; a US-hosted box starts at ~200ms before a single setting is touched.
1. Make sure UDP transport is actually working
Modern RDP runs a TCP+UDP dual transport — UDP (port 3389) carries the display update stream and is what makes scrolling and video smooth over lossy links. It's enabled by default on current Windows Server builds, but both ends of the path need it permitted:
New-NetFirewallRule -DisplayName "RDP-UDP" -Direction Inbound -Protocol UDP -LocalPort 3389 -Action Allow
Check the result from the client side: in the RDP session, open Connection Info (the signal-bars icon in the title bar) — "The quality of the connection to the remote computer is good/excellent and UDP is enabled" confirms the transport. If UDP is blocked, you silently fall back to TCP-only and lose the smoothness.
2. Group Policy graphics settings
Open gpedit.msc → Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Session Host → Remote Session Environment:
- Prioritize H.264/AVC 444 graphics mode for Remote Desktop connections: Enabled — keeps text sharp instead of letting the encoder blur it. This setting exists and works on Server 2022 and 2025.
- Configure compression for RemoteFX data: still present in the policy templates on current builds — set "Optimized to use less network bandwidth" on constrained links. (The RemoteFX vGPU feature was removed in newer releases, but the compression codec policy remains valid for session data.)
3. Remove the background noise
A desktop-as-a-service doesn't need consumer features indexing themselves:
- Windows Search indexing — disable the service (
WSearch) on machines where nobody browses files by search; it stops the periodic disk-I/O storms on your SSD pool. - Unneeded scheduled tasks and consumer apps — Server builds ship leaner than desktop Windows, but Xbox/consumer components still arrive via updates; remove what the machine doesn't use.
- Startup creep — the same discipline as a physical PC:
Task Manager → Startup apps, keep the session lean for the RAM you paid for.
4. Honest sizing for RDP desktops
The workload is a remote Windows session, so size like a real desktop — ~1GB RAM per concurrent user plus the apps:
- Single user, Tally/accounting/browsing: Cottage 4GB (₹475/mo).
- 2–4 concurrent sessions or heavier ERP: Bungalow 8GB (₹836/mo).
- Reports while others work, bigger teams: Manor 16GB (₹1,854/mo).
Every tier ships licensed Windows Server 2022 or 2025 — you install, you administrator it. Full tiers on the VPS & RDP page.