How do I set up Remote Desktop Services licensing for multiple concurrent RDP users in an Amazon EC2 Windows instance?

Short description

By default, Windows Server allows only two simultaneous Remote Desktop sessions for administrative purposes. EC2 Windows instances adhere to this configuration.

To allow multiple concurrent users to connect through RDP, you must deploy Remote Desktop Services and purchase client access licenses. Then, configure a Remote Desktop Services licensing.

Or, use AWS License Manager with subscriber access licenses instead of client access licenses so that License Manager automatically provisions the required licensing infrastructure. License Manager also automatically integrates the licensing with AWS Directory Service for Microsoft Active Directory.

Note: By default, AWS doesn't provide or manage Remote Desktop Services client access licenses for Windows instances.

Resolution

Manually configure Remote Desktop Services

Deploy Remote Desktop Services

Complete the following steps:

1. Install the Remote Desktop Session Host role. For instructions, see Add roles and features to Windows Server on the Microsoft website.
   Note: For Server Selection, select your instance.

2. Install the Remote Desktop Licensing role. For instructions, see Add roles and features to Windows Server on the Microsoft website.
   Note: For Server Selection, select your instance.

3. To open the Remote Desktop Licensing Manager, run the following command:

   rdlicmgr.msc.

4. Open the context (right-click) menu for the server name, and then choose Activate Server.

5. Complete the fields in the Activate Server wizard.

6. Install the Remote Desktop Services client access licenses based on your preferred licensing mode, such as Per user or Per device.

Note: The Remote Desktop Session Host role has a licensing grace period of 120 days. You must configure your Remote Desktop Services licensing before the grace period ends.

Configure the Remote Desktop Services licensing

Complete the following steps:

1. To open the Local Group Policy Editor, run the following command:

   gpedit.msc.

2. Configure the Use the specified Remote Desktop license servers and Set the Remote Desktop licensing mode Group Policy settings. For instructions, see Configure licensing for an RDS deployment that includes only the RD Session Host role and the RD Licensing role on the Microsoft website.
   Note: For License servers to use, enter your license server hostname. Under Specify the licensing mode for the Remote Desktop Session Host server, choose Per Device or Per User based on your client access license. The client access license and licensing mode must match.

3. To apply the policy changes, run the following command:

   gpupdate /force

   Note: If prompted, then restart the instance.

4. To verify that your licensing configuration is correct, run the following command to open the Remote Desktop Licensing Diagnoser:

   lsdiag.msc.

   If you can't launch the Remote Desktop Licensing Diagnoser, then run the following command to validate your licensing mode:

   wmic /namespace:\\root\cimv2\TerminalServices PATH Win32_TerminalServiceSetting GET LicensingType

   Note: In the output, 2 refers to Per Device licensing, and 4 refers Per User licensing. If you see 1, then you must still configure the licensing mode.

5. In the Remote Desktop Licensing Diagnoser, make sure that the licensing mode and server are correct.

Use License Manager to configure Remote Desktop Services

Use License Manager with subscriber access licenses to configure Remote Desktop Services.

Related information

How do I resolve the "remote session was disconnected" error that I receive when I use RDP to connect to an Amazon EC2 Windows instance?