Workaround for Remote Desktop exceeding maximum number of connections

"Workaround"
1. Find a machine that can connect to the network windows2003
2. Start – Run – Enter "Tsmmc.msc" and jump out of a remote Desktop console
3, right click on the left "Remote Desktop", select "New Remote Desktop", as required to fill in the virtual host to connect the IP, user name, password, domain name, and then click "OK"
4, click on the new Remote Desktop, you can log on to the remote virtual host
"mop up work"
1, login to the remote virtual host, open "Task Manager", select "User", kicked off the 2 users left in the system
2. Start-run-gpedit.msc-Computer Configuration-Administrative Templates-windows component-Terminal Services-session, right window select "Set time limit for disconnected sessions"-select enabled, set a time
Win2k/win2003 the terminal server exceeds the maximum allowable number of connections
first, log out of the Remote desktop instead of closing the window directly

Ii. 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 alternative 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 component-Terminal Services-Session right window select Set time limit for disconnected sessions-select enabled, select a time

third, increase the maximum number of links
1, modify from Terminal Services Configuration: Run-tscc.msc (Terminal Services Configuration)-Connect-double-click Rdp-tcp or right-click-Properties, select "Network Card" tab-Modify "Maximum number of connections" To change the value you want, of course, this value can not be too large, otherwise it will occupy more system resources. However, the value modified here does not seem to work, and when set to No limit, the situation described in this article will still occur.
2, Group Policy level is higher than Terminal Services configuration, when Group Policy is enabled, the corresponding options in the Terminal Services configuration will be grayed and non-modifiable
Run-gpedit.msc-Computer Configuration-Administrative Templates-windows component-Terminal Services double-click the limit number of connections to the right-select enabled-fill in the maximum number of connections allowed
Four, change the remote terminal mode
Open Control Panel, double click Add Remove Programs, click Add Remove Windows Components, components, in the Windows Components Wizard dialog box, select Terminal Services, Next, Application Server, Next, and then follow the prompts to change the Terminal Services mode.
Windows 2000 Terminal Services has 2 modes of Operation: Remote Administration mode and Application Server mode. Remote Administration mode allows the system administrator to remotely administer the server and allow only 2 terminal sessions to log on to the Terminal server at the same time. Application Server mode allows users to run more than one application, allowing multiple users to log on from the terminal to access the server. However, the user who applies Terminal Services must have Terminal Services licensing, that is, the Terminal Services Licensing server must be set up within 90 days in this domain or workgroup, or the user will need to remove the application before reinstalling it.
v. Modifying the local Security policy
Control Panel >> Administrative Tools >> Local Security policy >> Local Policies >> security options >>
1, first find >>microsoft network server: The idle time required before suspending the session defaults to: 15 minutes, instead of their own time required (that is, no action idle after landing after more than a few hours after the automatic disconnection)
2. Then find >> Network security: Force logoff after logon hours are exceeded. The default is: Disabled, be sure to change to: Enabled
If a workaround has occurred:
1, first you can telnet to this host (regardless of which method you use), of course, if you can directly operate the machine better, but the direct operation does not have to use the command line, it is of course to know the machine Super Administrator's password, you can use Opentelnet to open the remote server telnet port.
2, Telnet up, first look at the user login:
Input command: Query user
System returns:
C:>query User

It may be different at this point, depending on the situation. Find the users who are disconnected but still occupy the system resources and channels, we want to kick it off. Proceed as follows.
Input command: Logoff 1
3. If the server shuts down the Telnet feature (which is the default), you can also extend the stored procedure via SQL Server xp_cmdshell, using the format: Master.dbo.xp_cmdshell '
Command content ', the rest can refer to the second step. Permission to access xp_cmdshell is required in this way
The above solution is basically not used later when I use the server Terminal Server exceeds the maximum allowable number of connections, previously considered cold start the server, but this must run a trip to the engine room, recently sent
Now the best way is to enter: mstsc/console/v: Your server IP: Remote port on the Run command line

Workaround for Remote Desktop exceeding maximum number of connections