Windows Server 2008 R2 How to modify the number of Remote Desktop connections

Computer---Properties---remote settings---Check "Allow computer connections to run any version of Remote Desktop (less secure)" ...

First step: Open Remote Desktop:

Computer---Properties---remote settings---Check "Allow computer connections to run any version of Remote Desktop (less secure)"

Step Two: Set the maximum number of Remote Desktop connections

Control Panel--> management Tools--> Remote Desktop Services--> Remote Desktop Session Host settings--> remove the "restrict each user to only one session" check, and then double-click rdp-tcp in the connection---network adapter--Maximum number of connections modified to 2 At this point, the number of Remote Desktop connections is set to 2.

In the work, often need to remotely connect to the server, however, in the company, the boss, colleagues need to connect to the server, and the default Win2003 operating system maximum number of connections is 2, so that the problem is coming, often encountered "Terminal Server beyond the maximum number of connections", resulting in the failure of the normal landing server. Here are a few ways to solve this problem.

Workaround One: Exit the Remote Desktop by "logoff" instead of closing the window directly;

WORKAROUND two: Kick out of disconnected users;

1, first through a variety of methods to connect to the server (Telnet);

2, go up, view the landing user list. Enter command: query user;

This way you can see what's different, depending on your specific situation. The user with ID 0 is logged in locally, and in state, when the hint is disconnected, the user is disconnected and the system resources and channels are occupied so that the user can be kicked off. Enter the logoff ID, which is the user who kicked the corresponding ID.

Workaround three: Limit the time that disconnected sessions exist; (recommended)

Under normal circumstances, we can not maintain the remote server for a long time online, but the system by default, as long as the login is no longer disconnected. Therefore, we can modify this default setting and give it a time to automatically disconnect.

You can fix the problem on a Windows 2003 server by setting it up in Group Policy: Click start → run, enter gpedit.msc, open the Group Policy window after enter, and then navigate to the computer Configuration → administrative Templates →windows component → Terminal Services → session. Then, in the right window, double-click set time limit for disconnected sessions, set the end disconnected session time to 5 minutes in an open window, or disconnect when set to idle. or open the Run window on the remote server and enter the "TSCC.msc" Connection Settings window. Then double-click Rdp-tcp on the right side of the connection item, switch to the Sessions tab, select the Override user Settings option, and then set an appropriate time for end disconnected session.

Solution Four: Increase the number of connections, that is, set the maximum number of connections more;

By default, the number of remote terminal connections allowed is 2 users, and we can increase the number of users who have remote connections online at the same time as needed.

Click start → run, enter gpedit.msc to open the Group Policy Editor window, navigate to Computer Configuration → administrative Templates →windows components → Terminal Services, and then double-click the "Limit number of connections" on the right to set the maximum number of connections that the TS allows.

With the above two configurations (method three & Method IV), you can basically guarantee that a remote terminal connection is no longer restricted. However, it is still reflected that at the same time only one user to connect, but prompted beyond the maximum number of allowed links, this is why? This situation is due to improper operation. When the previous account logs on to remote Desktop and exits without logging off, instead of simply shutting down the Remote Desktop window, the session is not freed, but continues to remain on the server side, taking up the number of connections, which affects the next user's normal logon.

Workaround Five: Limit the number of user sessions;

Restrict Terminal Services so that a user can only connect once. For Windows Server 2003, in the Terminal services Configuration (Terminal services Configuration), "limit every user to only one session" (Restrict each users to One session) is set to Yes (yes). In addition, you can set the Restrict Terminal Services users to use a single remote session Group Policy to Enabled.

Note: There are different ways to solve the different versions!

A: This is because the maximum allowable connection limit is set in Windows 2003, and you may not log off after each connection, causing the number of connections to exceed the maximum number of connections. You can fix the problem on a Windows 2003 server by setting it up in Group Policy: Click start → run, enter gpedit.msc, open the Group Policy window after enter, and then navigate to computer configuration → administrative templates → Terminal Services → sessions, and then in the right window, double-click Set time limits for disconnected sessions, set the end disconnected session time to 5 minutes in an open window. The best solution is the way you log off each time you disconnect.

B: Often many people Management Server friends must have encountered when their terminals connected to the remote computer, but prompted the "terminal connection beyond the maximum connection" hint? This is because windows2003 only supports the landing of 2 end users. When this happens, most people choose to call the computer room to reboot the server. But the loss is also obvious. So what can we do to solve it? Method of course is there. We only need to run "Tsmmc.msc" on a 2003 machine to open the Remote Desktop Connection, where we add a new connection, enter each other's IP address account number and password can be successfully landed on the other side of the desktop, then you can kick the next user. You can solve the problem of exceeding the maximum number of terminal connections.

C: Start → control face version → authorization To change the number of connections.

At the command line:

MSTSC/CONSOLE/V: Your server IP: remote port

For example: mstsc/console/v:222.222.215.222:3389

WIN2K/WIN2003 Terminal Server exceeds maximum allowable number of connections the whole strategy

Why: When you log on to a terminal server with a Remote Desktop link, you often experience a "terminal server exceeding the maximum number of allowed links" error that causes a failure to log on to the terminal server properly. This problem is caused by the fact that the default number of links to Terminal Services is 2 links, and that when you log on to Remote Desktop, if you do not exit by logging off, Instead of simply shutting down the Remote Desktop window, the conversation is not released, but continues to remain on the server side, which takes up the total number of links, which appears when the number reaches the maximum allowable value.

How to avoid it?

One, logout to exit the remote desktop instead of directly close the window two, limit the time that a disconnected session exists

1. Modify from Terminal Services Configuration

Run-tscc.msc (Terminal Services Configuration)-Connect-double-click Rdp-tcp or right-click-Properties-session-Select the first alternate user setting (O)-end a disconnected session [change the default value from never to an appropriate time, such as 30 minutes]

2. Modify from Group Policy

Start-run-gpedit.msc-Computer Configuration-Administrative Templates-windows components-Terminal Services-sessions

Right window select Set time limit for disconnected sessions-select enabled, select a time