Terminal Services Clients Consume Multiple Terminal Services CALs Because of Storage Issues (294729)
The information in this article applies to:
- Microsoft Windows 2000 Server SP2
- Microsoft Windows 2000 Server SP1
- Microsoft Windows 2000 Advanced Server SP2
- Microsoft Windows 2000 Advanced Server SP1
This article was previously published under Q294729 SYMPTOMS
Windows-based terminals or Windows clients may consume multiple Terminal Services CAL tokens because of local storage issues.
CAUSE
Windows-based terminals may consume multiple Terminal Services CAL tokens if the Terminal Services CAL token is not flushed to flash memory before the device is turned off. For example, if a Windows-based terminal
connects for the first time and there are no Terminal Services CALs available, it will be issued a temporary Terminal Services CAL token. This temporary Terminal Services CAL token will allow the Windows-based terminal to connect for 90 days from issuance. After full Terminal Services CALs are available, the WBT will be issued one. If the device is turned off before the full Terminal Services CAL token has been flushed to flash memory, it will be issued a second full Terminal Services CAL token the next time it connects.
Windows clients may also experience this problem. For example, if a Microsoft Windows 98 client that has been issued a full Terminal Services CAL token does not work and is restored from a backup that was taken during the time that it had been issued a temporary Terminal Services CAL, the Windows 98 client will be issued a second full Terminal Services CAL token the next time it connects.
RESOLUTIONA supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows 2000 service pack that contains this hotfix. To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site: NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this fix should have the following file attributes or later:
Date Time Version Size File name
-------------------------------------------------------
05/30/01 06:50PM 5.0.2195.3649 122,640 Icaapi.dll
05/29/01 12:19PM 5.0.2195.3649 93,456 Licmgr.exe
05/30/01 06:48PM 5.0.2195.3657 330,000 Lserver.exe
05/30/01 06:50PM 5.0.2195.3649 26,384 Mstlsapi.dll
05/29/01 12:19PM 5.0.2195.3649 141,584 Termsrv.exe
05/30/01 06:50PM 5.0.2195.3649 23,312 Tls236.dll
The updated files to correct this problem are also contained in Microsoft Security Update MS01-52. For additional information, click the article number below
to view the article in the Microsoft Knowledge Base:
307454 MS01-052: Invalid RDP Data Can Cause Terminal Services Failure
Microsoft recommends that you read the Security Update bulletin, and then apply the fix that is available as a download from the bulletin if you determine that your computer may be at risk. This will also correct the problems that are described in this article.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Windows 2000 Service Pack 3.
| Modification Type: | Minor | Last Reviewed: | 10/12/2005 |
|---|
| Keywords: | kbHotfixServer kbQFE kbWin2000sp3fix kbbug kbenv kbfix kbQFE kbWin2000PreSP3Fix KB294729 |
|---|
|