Remote Desktop multi-user access is one of the most common requirements when running business apps or shared workloads on a server, but it’s also one of the easiest setups to get wrong. In this guide, you’ll learn the core Remote Desktop Services (RDS) components, what each role actually does, and the most common configuration mistakes to avoid during a Windows VPS RDS setup, so your deployment supports multiple users reliably and stays stable over time.

Starting with the basics helps you avoid problems later. Follow the steps below, and you will have a working multi-user RDS setup on your Windows VPS.

Prerequisites for Windows VPS RDS Setup

Before starting the Windows VPS RDS setup, you need a Windows Server VPS from PerLod Hosting or any provider with full Administrator access so you can install server roles and reboot when required.

• You need network access to the server over RDP from your local PC with a stable internet connection.
• RDS components ready to install: You will set up RD Session Host and RD Licensing on the server to enable multi-user RDP.
• A licensing plan: You need a valid RDS license key and CALs, and if your server is standalone, you should plan to use Per Device licensing, not Per User.
• User accounts to assign access and clarity on how many simultaneous users and sessions you need.

Once you have completed these prerequisites, follow the steps below to complete the Windows VPS RDS setup.

Install RDS Roles on Windows VPS

To support multiple user sessions, you need to install the RD Session Host and RD Licensing roles. To do this, run PowerShell as an administrator and execute the following command:

Install-WindowsFeature -Name RDS-RD-Server, RDS-Licensing -IncludeManagementTools

After the installation is completed, you need to restart the server to apply the roles:

Restart-Computer

Configure RDS Licensing Mode on Windows VPS

If your server is not joined to a domain, you must use Per Device licensing; Per User licensing will not work in a Workgroup setup. You can force the server to look at itself for licenses and set the correct mode by using the following PowerShell commands:

$path = "HKLM:\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services"
if (!(Test-Path $path)) { New-Item -Path $path -Force }
New-ItemProperty -Path $path -Name "LicenseServers" -Value "127.0.0.1" -PropertyType String -Force
New-ItemProperty -Path $path -Name "LicensingMode" -Value 2 -PropertyType DWord -Force

• LicenseServers: Points the server to the local loopback address so it knows where to check for available licenses.
• LicensingMode: Setting the value to 2 configures the server for Per Device mode, which is for Workgroup environments.

Assign Remote Desktop Permissions

By default, standard user accounts do not have permission to connect via RDP. You must add your users to the local Remote Desktop Users group. To do this, you can use the following PowerShell command:

Add-LocalGroupMember -Group "Remote Desktop Users" -Member "YourUsername"

Common Mistakes to Avoid in RDS Setup on Windows VPS

Even with a correct installation, a few mistakes can break your RDS deployment or expose it to serious security risks. These are the most common mistakes admins run into and how to avoid them:

1. Ignoring the 120-Day Grace Period: RDS gives you a 120-day grace period before it requires a valid license. Once that window expires and no CALs are installed, all users will be blocked from connecting.

2. Mismatched Licensing in a Workgroup: Using Per-User licenses without an Active Directory Domain Controller is a critical error. The server will fail to validate the licenses, resulting in a warning that sessions will disconnect in 60 minutes.

3. Exposing Port 3389 to the Public: Opening the default RDP port directly to the internet is a security risk that invites brute-force attacks. Always secure the connection using a VPN, a strict firewall, IP whitelisting, or an RD Gateway.

FAQs

Conclusion

Setting up RDS for multiple users is straightforward when you install the correct roles, configure Per Device licensing, and add your users. Just remember to activate your licenses before the 120-day trial expires and keep your RDP connection secure. Once done, your Windows VPS will easily handle multiple concurrent remote desktop sessions.

We hope you enjoy the Windows VPS RDS setup. Subscribe to our X and Facebook channels to get the latest updates and articles on Windows VPS Hosting.

For further reading:

Automate Server Tasks on Windows VPS with PowerShell and Task Scheduler