Solve the problem of the maximum number of terminal connections on Windows Server

If you are looking for a solution for the maximum number of terminal connections on a windows Server, only backup is required. I did not perform the test. I used logout to exit the Remote Desktop instead of directly closing the window. II. restricted the time For Disconnected Sessions. 1. Modify the Run-Tscc from the terminal service configuration. msc (terminal service configuration)-connection-double-click RDP-Tcp or right-click-properties-session-select the first replacement user setting (O) -end a disconnected session [change the default value "never" to an appropriate time, for example, 30 minutes] 2. Start from Group Policy Modification-run-gpedit. msc-Computer Configuration-management template-windows Components-Terminal Services-set the time limit for Disconnected sessions in the right window of sessions-select Enabled, select a time. 3. add up to connections. 1. Modify from terminal service configuration: Run-Tscc. msc (terminal service configuration)-connection-double-click RDP-Tcp or right-click-properties, select the "Nic" tab-change "Max connections" to your desired value, of course, this value cannot be too large, otherwise it will occupy a large amount of system resources. However, the modified value does not seem to work here. When it is set to no limit, the situation described in this article will still appear. 2. The group policy level is higher than the terminal service configuration. When the Group Policy is enabled, the corresponding options in the terminal service configuration become gray and cannot be modified.-gpedit. msc-Computer Configuration-management template-Windows Components-Terminal Service double-click "Limit connections" on the right side-select "enabled"-enter the maximum number of connections allowed -www.2cto.com-4. Change the Remote Terminal open Control Panel in mode ", double-click "add and delete programs", click "add and delete Windows components", and "components". In the Windows component wizard dialog box, select "Terminal Services", "Next", and "Application Server ", "Next", and then follow the prompts to change the terminal service mode. Windows 2000 Terminal Services have two operating modes: Remote Management Mode and Application Server mode. The remote management mode allows the system administrator to remotely manage the server, and allows only two terminal sessions to log on to the terminal server at the same time. The Application Server mode allows you to run more than one application and allow multiple users to log on to the server from the terminal. However, the application terminal service user must have terminal service authorization, that is, the terminal service authorization server must be set in this domain or working group within 90 days. Otherwise, the user must delete the application, then reinstall. 5. modify local security policy control panel, Administrative Tools, local security policies, local policies, security options, 1. First find Microsoft Network Server: the default Idle Time Required Before a session is suspended is 15 minutes, which is the time required by the user (that is, the idle time after no action is completed after login) 2. Find Network Security: Force logout after the logon time is exceeded. The default value is disabled. Make sure to change to: enabled.


This article is from BKJIA.