Allow or block multiple RDP sessions for one user

By default, Windows Server gives each user one Remote Desktop session. If you connect from a second PC with the same account, you land in your existing session and the first PC is kicked off. This guide explains that behaviour, how to change it with the single-session policy, and what limits still apply.

Before you start

• A Windows VPS running Windows Server 2019, 2022 or 2025, with an Administrator account.
• Your connection details from your VPS provider's control panel. Connect on 203.0.113.10:3389.
• A clear reason to change the default. For most single-person servers the default is the right choice.

How sessions work by default

Windows Server, without the Remote Desktop Session Host role and its licences, allows two simultaneous remote sessions for administration. On top of that, the single-session rule is on by default:

• One session per user. When admin connects from a laptop while already connected from a desktop, Windows reconnects the laptop to the same session. The desktop shows a message that another user connected.
• Two sessions per server. Two different accounts can be signed in at once, for example admin and deploy. A third person is asked to disconnect someone.

This is why the default suits most people: you can move from one PC to another and pick up exactly where you left off, with every window still open.

Check the current setting

Read the setting from the registry in an elevated PowerShell window:

Get-ItemProperty 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server' -Name fSingleSessionPerUser

• fSingleSessionPerUser: 1 means each user is limited to one session (the default).
• fSingleSessionPerUser: 0 means one user can open separate sessions.

A Group Policy setting overrides this value. Check it as well:

Get-ItemProperty 'HKLM:\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services' -ErrorAction SilentlyContinue |
  Select-Object fSingleSessionPerUser

If this returns a value, the policy is in control and you should change it in Group Policy, not in the registry.

Change the policy

1. Press Win + R, type gpedit.msc and press Enter.
2. Go to Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Session Host → Connections.
3. Open Restrict Remote Desktop Services users to a single Remote Desktop Services session.
4. Choose:

• Enabled to keep one session per user.
• Disabled to allow the same user to open a new, separate session from each connection.

1. Click OK and refresh policy:

   gpupdate /force

1. Sign out of every session and connect again. Existing sessions keep the old behaviour until they end.

On the same Connections page, Limit number of connections caps how many sessions the server accepts. Leave it Not Configured unless you have a specific reason. Without the Session Host role, the two-session admin limit still applies.

Safe settings for teams

• One person, several PCs: keep the single-session rule enabled. You always return to the same desktop.
• Two people sharing a server: give each person their own account. With the single-session rule on, each has one session and neither can steal the other's.
• One shared account used by several people: avoid this. Each new login takes over the session someone else is using. Create separate accounts instead.
• More than two people at once: this needs the Remote Desktop Session Host role and RDS client access licences (CALs) from Microsoft. Check Microsoft's current licensing documentation before you plan it.

Check it works

1. From PC A, connect to 203.0.113.10:3389 as admin and open Notepad.
2. From PC B, connect with the same account.
3. List sessions on the server:

   quser

• With the single-session rule enabled, there is one admin line, and Notepad appears on PC B.
• With it disabled, there are two admin lines with different session IDs, and PC B shows a fresh desktop.

Troubleshooting

• "The number of connections to this computer is limited": both admin sessions are in use. Sign out an old session, or see Sign out a stuck or disconnected RDP session.
• Change has no effect: a domain or local policy still sets the value. Run gpresult /h C:\gp-report.html and look under Connections for the winning policy.
• Someone keeps getting kicked off: two people are sharing one account. Give each their own user.
• You need a third simultaneous user: that is a licensing question, not a policy switch. Do not use patched system files to bypass it.

Next steps

• Understand the server's built-in limit: The two-session RDP limit on Windows Server.
• Give each person their own login: Create a Windows user with RDP access.
• Help a colleague inside their own session: View or control another user's RDP session.