Windows licensing for remote desktop is confusing, and the rules affect how many people can use a server at once. This is a plain-language overview of what a typical Windows RDP server includes and where extra licences come in. Always check Microsoft's current licensing terms for your exact case.
Two kinds of remote access
- Remote administration. Windows Server allows a small number of simultaneous remote sessions meant for managing the server itself. By default this is two administrative sessions.
- Remote Desktop Services (RDS). The role used when many users need their own desktops or apps on the same server. It requires the RDS role and RDS client access licences (CALs).
What this means for a typical RDP server
A standard RDP server plan is built for one person, or a very small team, to run Windows software remotely: a trading terminal, browser automation, testing or a personal desktop. That fits the administrative sessions.
If you want many users to log in at the same time as separate users, that is an RDS deployment, and you must license it properly with RDS CALs bought from Microsoft or a reseller. We do not sell CALs, so plan for that cost and ask support whether the plan you want fits your use before you build on it.
Things that are easy to confuse
- Windows client versions (like Windows 11 Pro) allow one remote session at a time. A new connection from another user can disconnect the current one.
- Windows Server allows more sessions, but within the licence rules above.
- Your own software licences are separate. Office, trading platforms and other applications have their own terms.
Check your session limits
query user # list current sessions
quser /server:localhost
qwinsta # session names, states and IDsIf a user is stuck in a disconnected session, log it off with logoff SESSION_ID.
Staying within the rules
- Decide how many people need to connect at the same time.
- For one or two administrative users, a normal server is fine.
- For more, plan an RDS deployment with CALs, or use several servers.
- Keep your own application licences in order.
This is general information, not licensing or legal advice. Microsoft's licensing terms change, so read the current ones.