Shulou(Shulou.com)06/02 Report--

When you remotely log in to the desktop to operate on a software program this afternoon, the software cannot be operated. I checked the database, memory, process, and configuration files respectively, and found that they were not the cause, and it was not good to restart the server.

After that, it was finally solved by logging off the remote desktop, as follows:

(1) cmd enters the console

(2) enter the following command

C:\ user\ Administrator > query user

Found that there were eight connections.

(3) killing process

C:\ user\ Administrator > logoff 3 (ID number)

Then, the remote connection will work again.

After this battle, I immediately had the idea of changing the maximum number of connections. I changed it to 3.

Here's how to modify the maximum number of remote connections:

(1) Force remote connection to server: command line input

C:\ user\ Administrator > mstsc / v:192.168.1.1/console

(2) input in the run box: gpedit.msc

(3) Open the policy editor, open "computer configuration", "Administrative template", "Windows component", remote Desktop Service, remote Desktop session Host, connection. Our server version is WindowsServer 2008R2. This step may vary slightly from server to server. Double-click to make changes. I changed it to 3.

Now the problem comes again: what if colleagues often report more than the maximum number of connections when they log in? I intend to modify the existence time of disconnected sessions.

(1) the search steps are similar to the above. Open the policy editor and open computer configuration, Administrative templates, Windows components, remote Desktop Services, remote Desktop session hosts, and session time limits.

(2) double-click to modify. I'll change it to 15 minutes here.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.