Win2003 server exceeds maximum connection + force reboot server (method) _win Server

The first approach: Download the 3389 Windows Terminal Connector to S.jb51.net (resolve the problem of excessive number of terminals)

The second method: Run---mstsc/console/v by start---: Server name or IP or domain name
such as mstsc/console/v:111.158.11.132

Then you can use your own account to force the landing server!

Windows2003 only 2 users are allowed to connect by default.

Workaround.
Query user t off an admin logoff * * Number login ID for account

This machine is connected to 0
Mstsc/console/v IP
INDOWS2003 only 2 users are allowed to connect by default.

Method III (Best practices-recommended): Limit the time that a disconnected session exists
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.

force Terminate process:
However, there are times when we find that a program or process that cannot be closed is a critical process of the server or is indispensable to the operation, and then it is not enough to remove the process corresponding to the previous method, and instead to do so by forcing the shutdown command.
In Windows 2003 server
There is a file called Shutdown.exe, he is mainly responsible for restarting the computer, logging off the computer, shutting down the computer work, through which he can complete the operation. And the joy of it is that the command provides parameters that enable you to force the shutdown of a process that prevents the computer from restarting.
The first step is to enter command line mode through Windows 2003 Server's "start-> running-> input cmd".
Step Two: Enter the shutdown in the command line mode and return. (Figure 1)

Figure 1 Click to see the big picture
The third step: the default without parameters is unable to achieve any operation, the following simple introduction to the shutdown command of the common parameters.
/?—— Display Help information
/l--logoff
/s--shut down the computer
/r--shutdown and restart the computer
/a--cancels the operation that discards the system shutdown.
/h--Hibernate the local computer.
/T xxx--the timeout before the shutdown is xxx seconds, and no xxx defaults to 30 seconds.
The key to this article is that/f--forces a running application to shut down without warning the user beforehand.

Fourth step: Execute "shutdown-r-f-t 1"
(without quotes) The command completes our forced Restart computer operation, and a process or program that does not automatically shut down will be forced to close. The-r parameter in this command is a reboot,-F is the force to shut down processes and programs, and "-T 1" is 1 seconds to set closing down.