RDS: The RD Session Host server should be configured to allow an adequate number of simultaneous connections

Updated: April 27, 2010

Applies To: Windows Server 2008 R2, Windows Server 2012

This topic is intended to address a specific issue identified by a Best Practices Analyzer scan. You should apply the information in this topic only to computers that have had the Remote Desktop Services Best Practices Analyzer run against them and are experiencing the issue addressed by this topic. For more information about best practices and scans, see Best Practices Analyzer.


Operating System

Windows Server 2008 R2, Windows Server 2012


Remote Desktop Services





The maximum number of simultaneous connections is configured for less than 5 users.

If the maximum number of simultaneous connections is less than the required number of users, some users may not be able to log on to the Remote Desktop Session Host server.

Increase the maximum number of simultaneous connections by configuring the "Limit number of connections" Group Policy setting.

You can limit the number of simultaneous remote desktop connections by using Group Policy. Setting the maximum number of simultaneous connections to a number less than five is not recommended. To increase the maximum number of simultaneous connections, use the Local Group Policy Editor.

Membership in the Administrators local group, or equivalent, is required to complete this procedure.

  1. Log on to the RD Session Host server by using a user account that is a member of the local Administrators group.

  2. Click Start, type gpedit.msc in the Search box, and then press ENTER.

  3. Navigate to the following path: Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Connections.

  4. Double-click Limit number of connections.

  5. In the RD Maximum Connections allowed box, type a number that is greater than or equal to the maximum number of simultaneous connections for the RD Session Host server, and then click OK.

If this Group Policy setting is managed through Active Directory, you must update the Group Policy setting by using the Group Policy Management Console.

See Also

Community Additions