Why Server 2022 for RDP workloads
Windows Server 2022 is Microsoft’s long-term servicing channel release, which makes it the default recommendation for any RDP server you plan to keep running for years. Extended support runs into the 2030s, so a Server 2022 RDP host bought today won’t force an OS migration halfway through its useful life. Under the hood it brings meaningful improvements for remote workloads: better TLS defaults for RDP connections, stronger default cipher suites, and virtualization and container features that matter if your RDP server also hosts test environments or application servers.
Just as important is what Server 2022 doesn’t do: it doesn’t change the RDP fundamentals. The client you connect with is the same mstsc on your PC, the port is still 3389 by default, and the session experience is the familiar Windows desktop. Choosing 2022 is about longevity and security posture, not relearning how remote desktop works.
Enabling RDP on Windows Server 2022
Remote administration over RDP is available on Server 2022 but not always switched on, depending on how the machine was provisioned. On a rented RDP server it typically arrives already enabled with credentials emailed to you — for example, providers like RDP Temple deliver servers with full admin RDP access preconfigured. If you are setting up your own machine:
- Open Server Manager → Local Server and click the Remote Desktop row, or open Settings → System → Remote Desktop.
- Enable Remote Desktop and confirm. Choose “Allow remote connections to this computer” with Network Level Authentication required (the default and recommended option).
- Verify the firewall rule. Enabling RDP normally creates the “Remote Desktop” inbound rule for TCP 3389 automatically — confirm it exists in Windows Defender Firewall with Advanced Security.
- Confirm your admin account has a strong password. Server editions enforce password complexity for new accounts; don’t weaken that.
- Connect from your PC with
mstsc, entering the server’s IP, and sign in with the administrator credentials. - Run Windows Update immediately. A fresh server image is rarely fully patched on day one.
Concurrent sessions and RDS licensing, explained
This is the part that costs people money when misunderstood. Here is the plain-English version of Microsoft’s rules:
- Remote administration: 2 sessions, no extra licenses. Windows Server 2022 allows up to two simultaneous remote sessions for administration purposes without any additional licensing. Two admins can be logged in at once doing admin work — installing software, configuring services, managing the box.
- More than that — or non-admin users working on the server — needs RDS. The moment you want three or more concurrent sessions, or you want regular users running applications on the server (a true multi-user remote desktop), you must install the Remote Desktop Services (RDS) role and buy RDS Client Access Licenses (CALs) for each user or device.
- There is no free loophole. The 120-day RDS grace period lets you evaluate multi-session RDS, not run production on it indefinitely. After it expires, unlicensed sessions stop working.
For a typical rented single-purpose RDP server — one person (or one automation account) using the desktop — the built-in two-session allowance is all you ever touch, and no CALs enter the picture. The licensing question only bites when you plan a shared multi-user environment, at which point budget for CALs alongside the server itself.
Hardening checklist for a Server 2022 RDP host
Server 2022 ships with better defaults than its predecessors, but an internet-facing RDP host still deserves deliberate hardening:
- Enforce long, unique administrator passwords and consider renaming the built-in Administrator account — automated attacks try “Administrator” first.
- Enable account lockout policy: a handful of failed logins should temporarily lock the account, which neuters password-guessing bots.
- Restrict RDP at the firewall to known IP ranges where possible; if the server must be reachable from anywhere, a VPN gateway in front of RDP is the stronger design.
- Keep NLA required — never downgrade to the less-secure compatibility mode to accommodate an ancient client; update the client instead.
- Patch on a schedule. Server 2022’s cumulative updates include RDP security fixes; “set and forget” servers are how breaches happen.
- Review who can log on remotely via the Remote Desktop Users group — membership should be minimal and audited.
Server 2022 vs older releases for RDP
| Server 2016 | Server 2019 | Server 2022 | |
|---|---|---|---|
| Support horizon | Extended support ends January 2027 | Extended support until January 2029 | Supported well into the 2030s |
| RDP security defaults | Older TLS defaults | Improved over 2016 | Strongest defaults of the three |
| Best fit | Legacy apps that won’t run elsewhere | Stable general-purpose RDP hosts | New deployments, long-lived servers |
| Admin session limit | 2 (same rule) | 2 (same rule) | 2 (same rule) |
The session and licensing rules are identical across all three — Microsoft hasn’t changed that model in years. The differences are support lifetime and security defaults, which is why 2022 wins for anything new.
When Server 2022 is the right call
Choose Windows Server 2022 for your RDP host when the server will live for years, when it faces the internet (strongest security defaults matter most there), or when you run current applications that expect a modern OS. Stick with 2019 only if a specific application is certified against it and not yet validated on 2022; choose 2016 only for legacy software that genuinely won’t run on anything newer — and plan that migration now, because its support clock is nearly out.
One more practical point in 2022’s favor: client compatibility is a non-issue. Every current RDP client — the built-in Remote Desktop Connection on Windows 10 and 11, Microsoft’s free apps for macOS, Android, and iOS, and the newer Windows App — connects to Server 2022 with full feature support, including modern authentication and the latest display protocol improvements. You get the longest support runway and the broadest client compatibility in the same package, which is a rare combination in infrastructure decisions.
If you’d rather not build and maintain the server yourself, rented plans remove the OS decision from your plate: RDP Temple’s Shared ($6/month), Virtual ($28/month, featured), and Dedicated ($165/month) plans each include a dedicated IP, full admin RDP, 24/7 support, and a 3-day money-back guarantee. You can also read the provider FAQ for plan specifics — and whatever OS you run, the two-session admin rule and the hardening checklist above apply equally.
Ready for your own RDP server?
Full admin access, dedicated IP, 24/7 support and a 3-day money-back guarantee on every plan. Pay by credit/debit card, bank transfer, Bitcoin or altcoins.
3-day money-back guarantee · Instant setup · 30+ server locations · 99% uptime SLA
Windows Server 2022 RDP: FAQ
Open Server Manager, go to Local Server, and click the Remote Desktop row — or open Settings, then System, then Remote Desktop — and turn it on with Network Level Authentication required. Windows creates the firewall exception for TCP port 3389 automatically. Verify the firewall rule exists, set a strong administrator password, run Windows Update, and connect from your PC with mstsc using the server's IP.
Windows Server 2022 allows two simultaneous remote sessions for administration without additional licensing. If you need more than two concurrent sessions, or non-administrator users running applications on the server, you must install the Remote Desktop Services role and purchase RDS Client Access Licenses (CALs) for each user or device.
No. A typical single-purpose RDP server used by one person or one automation account stays within the built-in two-session allowance for remote administration, so no RDS CALs are needed. CALs only enter the picture when you build a multi-user environment with more than two concurrent sessions or regular users working on the server.
For new deployments, yes — mainly because of its longer support horizon (well into the 2030s versus 2029 for 2019) and stronger RDP security defaults. The session limits and licensing rules are identical across versions. Choose 2019 only if a specific application is certified for it and not yet validated on 2022.
Use long unique administrator passwords, keep Network Level Authentication required, enable an account lockout policy against brute-force attempts, restrict RDP at the firewall to known IPs where possible, patch on a regular schedule, and keep the Remote Desktop Users group minimal. For internet-facing servers, a VPN gateway in front of RDP is the strongest design.
Yes. The built-in Remote Desktop Connection (mstsc) on Windows 10 and 11 connects to Windows Server 2022 with no extra software — enter the server's IP address and sign in with your administrator credentials. Microsoft's free Remote Desktop apps for macOS, Android, and iOS work as well.
