The remote session is interrupted because this computer does not have a Terminal Server Client Access License.

Solution: Use Terminal Server authorization to determine the number of ECSS left in the license server. To enable Terminal Server authorization, click Start and Program "," Administrator tool ", and then point to" Terminal Server authorization ". If no remaining Cal is issued to the client on the license server, purchase and install another Cal as needed.

For more information, see: purchase a client access license; install a client access license; purchase and install a client access license on the terminal server license server.

Cause: the terminal server authorization mode on the terminal server may be set to "per device", while the License Server may only have "per user Cal ". In this case, the license server will issue only temporary licenses, which cannot be upgraded. When the temporary license is about to expire in a few days, "event ID 26, source: Application pop-up message" is displayed in the Application Event Log on the client. The event message indicates how many days the temporary license will expire. Similarly, "event ID 1011, source termservice" is displayed in the Application Event Log On the terminal server.

Solution: Change the terminal server authorization mode from "per device" to "per user ".

Key Points

The terminal server does not monitor each user's Cal. This means that even if the License Server database has only one per-user Cal, each user's Cal will not be reduced when it is used. It does not remove the administrator from the End User License Agreement (EULA) request to provide a valid Terminal Server Cal for each user. If you are not using the Cal of each device but cannot obtain one Cal for each user, this is a violation of EULA. See the following text, which is selected from the EULA of Windows Server 2003:

"You can use two different ts CAL:" device "and" user ". Each ts device Cal allows one device (used by any user) to execute Windows sessions on any server. Each ts user Cal allows a user (using any device) to execute Windows sessions on any server. You can mix the TS device cal with the TS user Cal and use it with the server software in the environment. You can have the terminal server request a license for each user or device (default), but you cannot request two licenses at the same time ."
For more information, see configure Terminal Server authorization mode.
Cause: the terminal server may not be able to find the license server.

Solution:

Perform the following steps:

1. confirm that the license server is correctly installed.

2. Check whether the terminal server authorization service is running on the license server.

3. Verify that the Domain Name System (DNS) is correctly configured on each computer, and the client, Terminal Server, and license server can communicate with each other. To complete the preceding operations, run the ping command on each computer by IP address, FQDN, and NetBIOS name. If any ping command fails, verify the DNS configuration on the network.

4. On the terminal server, set a preferred authorization server to be connected. You can use the registry, WMI script, or group policy settings or terminal server configurations in Windows Server 2003 with Service Pack 1.

See also: Install terminal server authorization; set the preferred terminal server license server; Terminal Server License Server role

Solution: if the previous solution cannot solve this problem, create a backup of the mslicensing registry key and its subkeys on the client, and then perform the following operations to delete the original and subkeys:

1. on the client, navigate to the following registry subitem: HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ mslicensing.

2. Click mslicensing.

3. On the registry menu, click Export registry file ".

4. In the "file name" box, type mslicensingbackup and click "save ". To restore this registry entry in the future, double-click mslicensingbackup. Reg.

5. Click "delete" on the "edit" menu, and then click "yes" to delete the mslicensing registry subitem.

6. Close the Registry Editor and restart the computer. When the client restarts, the missing registry key is re-created.

Warning

Improper registry editing may seriously damage your system. Back up any valuable data on the computer before changing the registry.

See: How to Use the restrictanonymous registry value (http://go.microsoft.com/fwlink/ in Windows 2000? Linkid = 38561)
For more information, see:
Terminal Server authorization grace period;
Install terminal server authorization;
Activate the terminal server license server;
Purchase a client access license;
Install the client access license;
Purchase and install the client access license on the terminal server license server;
Activate the terminal server license server.

Other reference solutions:

Change the "Authorization mode" in "terminal service configuration" to "per user ". To do this, follow these steps:

1. Click Start, point to administrative tools, and click Terminal service configuration ". 2.

2. Click "Server Settings" and double-click "Authorization mode ".

3. Change "Authorization mode" to "per user", and click "OK ".

Currently, window Server 2003 does not manage "User Cal ". This means that even if there is a "User Cal" in the License Server database, it will not be used less. In this way, the Administrator will not be deleted according to the requirements of the "End User License Agreement" (EULA) so that each user has a valid Terminal Server (TS) Cal. If the "device Cal" is not used, if not every user has a "User Cal", it will violate the EULA.

1. There are three methods to avoid this situation:

1. Set the Group Policy on the Windows 2003 Server: Click Start> Run and enter gpedit. MSC, press enter, and open the Group Policy window. Then, choose computer configuration> Manage template> Terminal Service> session ", in the window on the right, double-click "set time limit for Disconnected Sessions" and set the "End disconnected session" Time to 5 minutes.

2. Start → Control Panel → authorize and change the number of connections.

3. The ultimate solution is also the best solution: log out every time you disconnect the remote server.

2. How can I log on to a terminal that exceeds the maximum connection:

Windows supports login by only two end users by default. If the "terminal connection exceeds the maximum connection", you can:

1. Call the IDC administrator to restart the server. '.

2. Use a dedicated remote connector.

3. Run mstsc/V: IP/console and connect to the remote system's 0 session.

4. Run "tsmmc. MSC, open the Remote Desktop Connection, add a new connection, enter the IP address of the remote server, remote login account and password, and log on to the remote server desktop (Figure 1 ), then you can use the Terminal Service Manager to cancel unnecessary users and immediately solve the problem.