windows 2003 远程桌面连接数限制防止和解决方法（Windows 2003 remote desktop connection limit prevention and resolution）.docVIP

windows 2003 远程桌面连接数限制防止和解决方法（Windows 2003 remote desktop connection limit prevention and resolution） Windows 2003 remote desktop connection limit Windows 2003 server remote desktop connection limit has been bothering for a long time, causing trouble for routine maintenance. Since Microsoft will not fundamentally solve the problem, there are other ways to reduce the probability of the problem. First, the processing method at the server side is as follows: (only when the connection number is limited and the following methods are not available): 1. sets the broken session end time limit so that the session is disconnected but still occupies an Session Start computer operation Gpedit.msc configuration management module - Windows template terminal services: session, select the right side of the window to open the session to set a time limit - select enabled , choose a time Start computer operation Gpedit.msc configuration management module - Windows template terminal services: session, select the right window arrival time limit when the session termination - select enabled. 2. connect the session indefinitely to facilitate remote control and share the data of the session at any time, that is, the status of the remote desktop that you shared at any time: Start - management tools - Terminal Services Configuration - server configuration - restricts the use of a session by each user 3., develop good habits, quit the connection, do not directly shut down, but the use of cancellation. Two, if more than one connection already exists 1., the connection can be broken by command, and this method is also available in the 2000 system; if the method is written off in the task managers user: 1. in Command Line mode: enter command query user C:\query user USERNAME, SESSIONNAME, ID, STATE, IDLE, TIME, LOGON, TIME dfsadmin 0, Disc. 7/23/2007, 7:53 PM Mrsadmin rdp-tcp#10 1 Active. 7/24/2007 9:31 AM ID 0 is a local user login, user login ID 1 is 3389, is in operation, but still occupy sys