Multiple Users on One Windows VPS: Sessions, RDS and CAL Licensing Explained

A common plan: rent one Windows VPS, install the accounting or ERP app once, and let a small team work on it over Remote Desktop. Windows Server can do this. But how many people can work at the same time depends on two things that are easy to mix up: what Windows allows technically, and what the licence allows. This guide covers both, in plain terms.

What you get by default: two administrative sessions

Out of the box, Windows Server runs in "Remote Desktop for Administration" mode. It allows up to two concurrent remote sessions, and they need no Remote Desktop Services (RDS) client access licences. Microsoft describes these sessions as being for administering the server. They are meant for you and maybe a colleague managing the machine, not for a team doing daily work in a business application.

Each person should still have their own account. Create a local user and allow it to sign in over RDP:

New-LocalUser -Name "sara" -FullName "Sara" -Password (Read-Host -AsSecureString "Password")
Add-LocalGroupMember -Group "Remote Desktop Users" -Member "sara"

To see who is signed in right now, and in which state:

quser

The output lists each session with its ID and state, Active or Disc (disconnected). By default Windows also limits each user to one session, so the same account cannot open two desktops at once.

What happens when a third person connects

When both sessions are in use, the next person sees "Select a user to disconnect so that you can sign in." If they pick someone, that person's session is disconnected. Their apps keep running in the background, but they lose the screen.

Disconnected sessions count toward the limit. People who close the RDP window with the X instead of signing out leave a session behind. You can sign out stale sessions with logoff <ID>, or set a time limit so Windows does it for you. In gpedit.msc go to Computer Configuration, Administrative Templates, Windows Components, Remote Desktop Services, Remote Desktop Session Host, Session Time Limits, and set "Set time limit for disconnected sessions". Warn users first: a signed-out session closes open apps, and unsaved work is lost.

More concurrent users: the RDS Session Host role plus RDS CALs

To let more than two people work at the same time, or to run the server for regular users rather than administration, you install the Remote Desktop Session Host role. On a standalone server you also install the Remote Desktop Licensing role on the same machine:

Install-WindowsFeature RDS-RD-Server, RDS-Licensing -IncludeManagementTools
Restart-Computer

After the role is installed, Windows gives you a 120-day grace period. During that time, users can connect without a licence server. When it ends, each connection needs an RDS client access licence (CAL) issued by an activated licence server. If none is available, users see "There are no Remote Desktop License Servers available to provide a license" and cannot sign in.

Per User or Per Device CALs

• Per User: one CAL per named person, who can connect from any number of devices. Microsoft documents that Per User CALs cannot be tracked in a workgroup, so this mode fits servers joined to Active Directory.

• Per Device: one CAL per client device, whoever uses it. It works without a domain, which is why it is the usual choice on a standalone VPS. It also fits shift work, where several people share the same office PCs.

You set the licence server and mode with two policies under Remote Desktop Session Host, Licensing: "Use the specified Remote Desktop license servers" and "Set the Remote Desktop licensing mode". To check what the server is using and how many grace days remain, run this in Windows PowerShell:

$obj = Get-WmiObject -Namespace "Root/CIMV2/TerminalServices" Win32_TerminalServiceSetting
$obj.GetGracePeriodDays()
$obj.GetSpecifiedLicenseServerList()
$obj.LicensingType

The RD Licensing Diagnoser (lsdiag.msc) shows the same information with plain-language warnings. Guides that "reset the grace period" through the registry are not a licensing solution. Microsoft does not recommend it, and running production users that way leaves you unlicensed.

Licensing on a hosted VPS: confirm this first

This is the part most guides skip. On a rented server, the Windows Server licence usually comes from the hosting provider under Microsoft's licensing programme for service providers. RDS access for hosted servers is often licensed through the provider as well, on a monthly basis. Whether you can buy RDS CALs yourself and use them on a rented server depends on your agreement with Microsoft and its current terms. Some agreements allow it and others do not.

So before you install the RDS role, open a ticket with your provider and ask three questions: which RDS licensing options exist for your plan, what they cost, and who activates the licence server. IM HOST support can confirm the options for your plan before you start. Do not assume RDS licences are included with a Windows VPS unless your provider confirms it in writing.

Sizing a multi-user server

Every session loads its own profile, desktop and copy of each app. Memory grows with every user. As a rule of thumb for light office and accounting work, plan around 2GB for Windows itself plus 0.5 to 1GB per active user. A user with a busy web browser or a heavy ERP client can need more. These are starting points, not limits. Measure on your own workload:

• Open Task Manager, Users tab, during a normal working hour. It shows memory and CPU per user.

• If memory stays near the top for long periods, sessions will slow down for everyone. Add RAM before you add users.

• Watch the disk too. User profiles and temp folders grow over time on the system drive.

A practical setup checklist

1. One account per person. Never share the Administrator account. Separate accounts give you an audit trail and let you reset one password without disrupting everyone.

2. Give regular users Remote Desktop Users membership only, not Administrators.

3. Restrict RDP to known IP addresses or a VPN. A multi-user server has more passwords that can be guessed.

4. Set time limits for disconnected and idle sessions, and tell users to sign out at the end of the day.

5. Keep shared company files in one folder with NTFS permissions per group, not on individual desktops.

6. Back up the application data and test a restore. More users means more data that changes every day.

Avoid tools that patch Windows system files to allow more sessions. They break the licence terms, and Windows updates often break them too, usually at a bad moment.

Run it on IM HOST

IM HOST Windows VPS RDP plans start at $8.99/month (2 cores, 4GB RAM) with full Administrator access over RDP, across 13 plans, so you can start small and move up as the team grows. Cloud VPS gives you dedicated vCPU and RAM, runs Windows or Linux, and can be upgraded anytime. Our 24/7 engineer support can confirm the licensing options for your plan before you install the RDS role. There are no setup fees, and you have a 30-day money-back guarantee.

This article is general information about Microsoft licensing, not legal advice. Microsoft's current Product Terms are the reference.