How many people can connect to my Windows VPS at once?

What this is#

Out of the box, Windows Server allows two simultaneous Remote Desktop sessions. A third person connecting gets "Too many users are signed in" and is asked to pick an existing session to disconnect. Two related behaviors that look like bugs but aren't:

• The same account takes over its own session. If you log in with an account that's already connected, Windows hands you that session and the other device sees "Your Remote Desktop Services session has ended, another user connected." That's per-account behavior by design, give each person their own Windows user account instead of sharing Administrator, and the two of you can genuinely work side by side.
• The limit counts sessions, not attempts, two colleagues on two accounts is fine; the third concurrent desktop is where the wall is.

Where the limit comes from#

This is Microsoft licensing, not a VPSDime restriction. The Windows Server Datacenter license included with your VPS covers the two administrative sessions. Concurrent desktops beyond that require Remote Desktop Services (RDS): the RD Session Host role plus RDS CALs (client access licenses, per-user or per-device) which you purchase yourself from Microsoft or a licensing reseller and install with the RD Licensing role. Setting RDS up is standard Windows administration, and like everything inside the OS it's self-managed territory, we don't sell or provision CALs.

Before you buy CALs: cheaper ways to share a server#

Match the solution to what people actually need:

• They need to see or assist, not own a desktop: screen-sharing tools, TeamViewer, AnyDesk, RustDesk (open source, self-hostable), or Chrome Remote Desktop, share the existing session with any number of viewers, need no extra Windows licenses, and are the right tool for support sessions, demos, and pair work.
• Each person needs their own simultaneous desktop: that's what RDS CALs are for, or, often simpler and cleaner, a separate Windows VPS per user: no RDS plumbing, no license administration, full isolation, and predictable cost.
• They only need the application or its data: serving it as a web app or letting them connect to the service directly (a database, an API) needs no desktop sessions at all.

Managing the sessions you have#

• See who's connected: Task Manager → Users tab, or query session in a terminal.
• Free a slot: sign out a session from that Users tab (right-click → Sign off), or logoff <session id>. Signing out ends their programs; disconnecting merely detaches and keeps consuming the slot.
• Locked out because both slots are taken by stale sessions? Connect once more with one of the same accounts, you'll take over its session rather than needing a third.

Still need help?#

You can open a support ticket. So we can help on the first reply, it's worth mentioning:

• the VPS hostname or IP,
• how many people need to be connected at once,
• whether they need their own desktops or just to see one screen.

Related questions#

• "How many RDP users can connect to my Windows VPS at the same time?"
• "What does 'too many users are signed in' mean?"
• "Why does my RDP session end when a colleague logs in?"
• "Do I need terminal services / RDS CALs, and where do I get them?"
• "Is there a way to share a Windows VPS without buying licenses?"
• "How do I sign out another RDP session?"