WinServer 2016安装RDS后仍仅允许2个用户连接的问题咨询

Hey there, let's walk through the most common reasons why you're still hitting that connection limit even after setting up RDS on your Azure Windows Server 2016 VM. These are the key checks to run:

• Verify RDS CAL Licensing Setup
  Windows Server RDS doesn't lift the 2-user limit automatically—you need valid Remote Desktop Client Access Licenses (CALs) and a properly activated licensing server.

  1. Open Remote Desktop Licensing Manager on your server.
  2. Confirm your licensing server is activated and has available CALs (either User CALs or Device CALs, depending on your setup).
  3. Head to Remote Desktop Session Host Configuration and check that the session host is configured to use this licensing server (look under the "Licensing" section).

• Check RDS Deployment Completion Status
  Sometimes partial deployments can leave you stuck. Open Server Manager, go to Remote Desktop Services > Overview, and make sure all required roles (Session Host, Connection Broker, Licensing Server) are listed and showing a healthy status. If any role has an error, resolve that first—often it's a missing configuration step from the tutorial.

• Audit Local Group Policy Restrictions
  Group policy settings might override your RDS configuration:

  1. Run gpedit.msc to open Local Group Policy Editor.
  2. Navigate to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections.
  3. Ensure Restrict Remote Desktop Services users to a single Remote Desktop Services session is set to Disabled (unless you specifically want single sessions per user).
  4. Set Limit number of connections to your desired user count (e.g., 10) instead of the default 2.

• Validate Azure VM Network & Service Settings
  Even if RDS is set up correctly on the server, Azure's network rules might interfere:

  1. Check your VM's Network Security Group (NSG) to confirm port 3389 is open for all IPs that need to connect (or restrict to specific IPs for security).
  2. On the server, open Services and verify the Remote Desktop Services (TermService) is running and set to Automatic startup.

• Dig into Event Logs for Specific Errors
  When the third user tries to connect, the server logs a detailed error that can pinpoint the issue. Go to Event Viewer > Applications and Services Logs > Microsoft > Windows > RemoteDesktopServices-RdpCoreTS—look for events around the time of the failed connection. Common errors include licensing server unavailability or expired CALs, which will guide your next fix.

内容的提问来源于stack exchange，提问作者Vaethin