The remote session was interrupted _win server because this computer does not have a Terminal Server Client Access License

Solution: Use Terminal Server Licensing to determine the number of CALs remaining in the license server. To turn on Terminal Server Licensing, click Start, clicking Programs, then Administrator Tools, and then point to Terminal Server Licensing. If no remaining CALs are issued to clients on the license server, purchase and install additional CALs as needed.

See also: Purchase client access licenses; Install client access licenses; Purchase and install Client access licenses on a Terminal Server license server

Reason: The Terminal Server Licensing mode in the Terminal server may be set to Per device, and the license server may have only "Per User CALs". If this is the case, the license server will issue only temporary licenses, which cannot be upgraded. When a temporary license is about to expire in a few days, the event ID 26, Source: Application pop-up message appears in the application event log on the client. The event message indicates how many days of temporary licenses are about to expire. Similarly, event ID 1011, source TermService, will also appear in the Application event log on the Terminal server.

Solution: Change the Terminal Server licensing mode from "Per Device" to "per user".

Points

The terminal server does not monitor per User CALs. This means that even if there is only one Per User CAL in the license server database, each user CAL will not be reduced when it is used. It does not provide a valid Terminal server CAL for each user by removing the administrator from the End User License Agreement (EULA) requirement. If you are not using each Device CAL but cannot get a per-user CAL for each user, the EULA is violated. Refer to the following text, which is selected from the EULA for Windows Server 2003:

"You can use two different TS CALs: Devices and users." Each TS device CAL allows a device (used by any user) to perform a Windows session on any server. Each TS user CAL allows one user (using any device) to perform a Windows session on any server. You can mix TS Device cals and TS User CALs at the same time, and you can use them concurrently with Server Software in your environment. You can have the Terminal Server request per-user licenses or Per-device licenses (the default), but not both. ”
See also: Configuring Terminal Server Licensing Mode
Reason: The terminal server may not be able to find a license server.

Solution:

Please perform the following steps:

1. Verify that the license server is installed correctly.

2. Verify that the Terminal Server Licensing service is running on a license server.

3. Verify that the client, Terminal Server, and license server can communicate by ensuring that the domain Name System (DNS) is configured correctly on each computer. To do this, use the IP address, FQDN, and NetBIOS name on each computer to run the ping command for each of the other two computers. If any of the ping commands fail, verify the DNS configuration on your network.

4. On the terminal Server, set a preferred licensing server to connect to. You can do this by using a registry, WMI script, or by using a Group Policy setting or a Terminal Server configuration in Windows Server 2003 with Service Pack 1.

See also: Install Terminal Server Licensing; Set preferred Terminal Server license server; Terminal Server License server role

Solution: If the previous solution does not resolve this issue, create a backup of the MSLicensing registry key and its subkeys on the client, and then do the following to delete the original items and subkeys:

1. On the client, navigate to the following registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing.

2. Click MSLicensing.

3. On the Registry menu, click Export Registry Files.

4. In the File name box, type Mslicensingbackup, and then click Save. If you need to restore this registry key later, double-click Mslicensingbackup.reg.

5. On the Edit menu, click Delete, and then click Yes to confirm the deletion of the MSLicensing registry subkey.

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

Warning

Improper editing of the registry can severely damage your system. Before you change the registry, you should back up any valuable data on your computer.

See: How to use the RestrictAnonymous registry value in Windows 2000 (http://go.microsoft.com/fwlink/?LinkId=38561)
See also:
Terminal Server Licensing grace period;
Install Terminal Server Licensing;
Activate a Terminal Server license server;
Purchase client access Licenses;
Install client access Licenses;
Purchase and install Client access licenses on the Terminal Server license server;
Activate a Terminal Server license server.

Other reference solutions:

Please change the licensing mode in Terminal Services configuration to per user. To do this, follow these steps:

1. Click Start, point to Administrative Tools, and then click Terminal Services Configuration. ²

2. Click Server Settings, and then double-click Licensing mode.

3. Change the licensing mode to per user, and then click OK.

Currently, Window Server 2003 does not manage User CALs. This means that even if there is a "user CAL" in the license server database, it will not be reduced when it is used. This will not remove administrators from the requirements of the End User License Agreement (EULA) for each user to have a valid Terminal Server (TS) CAL. In the absence of a device CAL, a "User Cal" is not available for each user, and the EULA is violated.



First, to avoid such a situation again, there are 3 ways: ²

1, on the Windows 2003 server through Group Policy settings to solve the problem: Click "start → run", enter "Gpedit.msc," Open the Group Policy window, and then navigate to "Computer configuration → administrative templates → Terminal Services → sessions," and then in the right window, double-click the " Set time limits for disconnected sessions, set the end disconnected session time to 5 minutes in an open window.

2, start → control surface version → authorization, change the number of connections.

3. The ultimate solution is also the best solution or the way to log off each time a remote server is disconnected.

Two, happen to encounter terminal connection beyond the maximum connection and cause can not login solution:

Because windows2003 only supports 2 end users ' landings by default. When the "terminal connection exceeds maximum connection" situation occurs, you cannot log on:

1, to the computer room administrator calls to restart the server. ‘.

2, the use of dedicated remote connectors.

3, run Mstsc/v:ip/console, connect to the remote system 0 sessions.

4. Run "Tsmmc.msc" on a Windows2003 machine, open Remote Desktop Connection, add a new connection, enter the remote server's IP address, Telnet account and password, log on to the remote server desktop (Figure 1), and then use Terminal Services Manager Cancel out the redundant users can immediately resolve the terminal