Win2003 Multi-User Telnet setting method (text) _win server

The number of remote terminal connections allowed by Windows Server 2003 by default is 2 users, and we can increase the number of users who have remote connections online at the same time as needed.

The following is a detailed description of the multiple user login Windows Server 2003 operating system steps for reference:

Install the Terminal Server build first, select Add or Remove Windows components in Add or Remove Programs under Control Panel, and choose the Terminal Server option in the pop-up dialog box (Figure 1)

Figure 1

The installer then makes a system description of the system components that you install, recommending that the user or administrator for the first installation read the details (Figure 2)

Figure 2

When you click "Next", the system will pop up as shown in Figure 3 dialog box to allow you to choose the default permissions, the permissions of remote users that are controlled by these two modes are important when they log on to the local computer, and the "Full security model" is more secure and safer, and, of course, administrators can also use Terminal Services Configuration The tool sets the detailed security options, and "Relaxed security mode" is less secure and recommends no selection.

Figure 3

Of course, Microsoft has defined this build as a fee-setting, so a query dialog box pops up at installation--well, there's a trial option, and it's a long time (Figure 4). We choose "... Within 120 days ... "

Figure 4

The following is the licensing mode when you log on to the server (Figure 5) We select "Per User licensing mode" and the system restarts after the installation completes.

Figure 5

After the installation is complete and the system restarts, we modify the maximum number of connections to expand the same way as the article begins. Click start → run, enter gpedit.msc to open the Group Policy Editor window, and then navigate to the Computer configuration (computer configuration) → Administrative Templates (Administrative Templates) →windows component ( Windows components) → Terminal Services (terminal Service), double-click the limit number of connections on the right (limit count of connections), and then double-click to open the Configuration window (limit of Connections properties), select Enabled to set the maximum number of connections allowed for its TS maximum connections allowed to the required quantity.

Of course, this only restricts the expansion of the number of connections, and for settings such as the details of the session, there is also a detailed set of methods in Group Policy, as shown in Figure 6:

Figure 6

All right, here we go. To modify the maximum number of connections The basic operation is completed, the next is the local authority assigned, the specific steps are as follows:

First establish a local account, the right size of the administrator more specific circumstances, and then add the account to the remote login group (remote Desktop users), so that users can log on to the computer through this account! As shown in Figure 7.

Figure 7

This is basically the end of the operation, but when the user remote login will find that the same account login can only have a session, how to make the same account login can have more than one session! (This applies to multiple people using the same account to log on to the server host)

In fact, you can set it in server settings under Terminal Services Configuration by setting the "Restrict each user to use one session" property to "no"! (as shown in Figure 8)

Figure 8

To really complete the multi-user login server related settings!

The problem is that, after the user logs on to Terminal Services, the system initiates a process for the user, enters the user name and password, and starts filling out the reimbursement document, which is maintained, and if the user logs off normally, the system closes the user session so that others need to be authenticated when they log in.

when the user exits Terminal Services without proper logoff, such as network interruption, client panic, direct shutdown, etc. Windows2003 Public Technical Document is the minimum 1 minutes after the system shut down the session, if in this 1 minutes, there is another user login, then the system will continue to the last person's session to the user, so this person landed after the discovery does not require a username and password has landed, Even the documents that the previous person filled out are still in.

The problem is this minute, can you shrink it?

cost a lot of money (find a genuine windows2003 license, call Microsoft, this permission can ask up to 5 questions!!! Microsoft has offered a solution:
Registry [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\winstations\rdp-tcp], modifying

Maxdisconnectiontime

Change this value to 0x3e8 (1000), which is 1000 milliseconds, not set anywhere (not configured or default) reboot machine OK

Windows 2003 remote logins for multiple users

Typically, by default, Windows 2003 can only achieve 2 remote user logons.

Search on the Internet some settings, but also personally made some settings, the network does not install the "Terminal Services" approach is not feasible.

Or just start from the beginning, insert the system disk, Control Panel-Add the removal program-Add components-add Terminal Server and Terminal Server Licensing.

Next step down to do is, you can look at the details of the online instructions.

What needs to be explained is that in a step-by-step way, the Terminal Server authorization time is 120 days, more than this time is not to be paid for it. This will have to ask the master.

Install Terminal Services on the basis of the following settings can be made to ensure that multiple users remote success.

1. Start Terminal Services: When you enter gpedit.msc in run and press ENTER, select "Computer Configuration"--"Administrative Templates"--"Windows Components"--"Terminal Services", set "limit connection Quantity" to "started", and maximum number of connections to 100, and " Allow users to use Terminal Services remote connection set to started.

2. Start-run tscc.msc

Management tools-Terminal Services Configuration-connection, set the maximum number of connections here, should be 1 set the same, may have turned gray, this step is not set.

Management tools-Terminal Services Configuration-server settings- limit each user to a session , check it out, so that all users can be superuser.