How to Enable the Remote Desktop Services (RDS) Feature Locally on Windows Server

Remote Desktop Services (RDS) is a powerful feature in Windows Server that allows multiple users to access and use a server remotely. Unlike standard Remote Desktop, which supports only one user at a time, RDS enables multiple simultaneous remote sessions, making it ideal for enterprises, shared computing environments, or centralized application deployment.

In this guide, we’ll walk through everything you need to enable and configure RDS locally — step by step — ensuring that the setup is clean, correct, and ready for production use.

What is RDS and Why Do You Need It?

Enabling Remote Desktop Services (RDS) allows users to:

• Connect to a centralized server

• Run applications remotely

• Get isolated desktop experiences

• Support multiple user sessions simultaneously

This is different from the basic Remote Desktop feature on Windows, which only allows one user to access a system at a time.

Prerequisites

Before proceeding, ensure:

• You are on a Windows Server OS (like Server 2016, 2019, or 2022).

• You are logged in as a local administrator.

• The server has a static IP and is reachable on the network.

Step-by-Step: Enable RDS Locally

Step 1: Install RDS Roles

1. Open Server Manager.

2. Click on Manage > Add Roles and Features.

3. Choose Remote Desktop Services installation (very important — don’t choose Role-based installation).

4. Select the deployment type:

   • Choose Quick Start for testing/lab.

   • Choose Standard Deployment for production.

5. Select the server from the pool.

6. Choose the RDS role services:

   • Remote Desktop Session Host (RDSH)

   • Remote Desktop Licensing

   • Remote Desktop Connection Broker (optional for large setups)

7. Complete the wizard and install.

8. Restart the server when prompted.

Step 2: Post-Install Configuration

After reboot, if you see:

"A Remote Desktop Services deployment does not exist in the server pool."

This means you didn’t use the Remote Desktop Services installation path in the wizard. Re-run the wizard and explicitly choose RDS installation, not role-based.

Step 3: Configure Licensing

Once RDS is deployed, you'll likely see:

"Remote Desktop licensing mode is not configured."

To fix this:

1. Open Server Manager > Remote Desktop Services > Overview.

2. Click Tasks > Edit Deployment Properties.

3. Go to the Licensing tab.

4. Set the licensing mode:

   • Per Device

   • Per User

Per Device vs Per User – What to Choose?

Choose based on how your users access the system.

5. In the same tab, specify your license server.

How to Find Your Server Name

You can find your server name by:

• Running hostname in Command Prompt.

• Or, right-click This PC > Properties, and look under Computer name.

Use this name to register the license server in the deployment settings.

How to Provide Remote Desktop Access to Users

To allow a user to access the machine remotely:

1. Go to: Settings > System > Remote Desktop

2. Enable Remote Desktop.

3. Click Select users that can remotely access this PC.

4. Click Add, and enter the username.

How to Know the Username to Add

To view existing users:

• Open Command Prompt, run:

    net user
  

• You’ll see a list of all local users. Add the appropriate one for RDP access.

Ensure RDP is Allowed Through Firewall

Check and allow RDP:

1. Open Control Panel > Windows Defender Firewall.

2. Click Allow an app through Windows Firewall.

3. Ensure Remote Desktop is checked for Private and Public networks.

Verifying That Everything Works

You can verify the setup by:

• Opening Remote Desktop Connection (mstsc.exe) from another PC.

• Enter the IP address or hostname of the server.

• Login using the username you enabled for RDP.

• Ensure you can connect and get a desktop session.

If multiple users can connect at once and licensing shows no warning, you’re all set!

Bonus: Testing the Licensing Server

To validate the RDS license server:

1. Open RD Licensing Diagnoser from Server Manager.

2. It will show any configuration issues and suggest fixes.

3. Ensure:

   • Licensing mode is set.

   • License server is installed.

   • CALs are activated (optional if testing).

Final Thoughts

Enabling and configuring RDS locally is a powerful way to create centralized, scalable remote environments. It’s perfect for:

• Enterprise deployments

• Virtual application hosting

• Shared office setups

• Labs and training centers

Just make sure to choose the correct installation method, configure licensing properly, and test connections thoroughly.