Article ID: 911288
Article Last Modified on 10/11/2007
APPLIES TO
- Microsoft Windows Server 2003 SP1
- Microsoft Windows Server 2003, Web Edition
- Microsoft Windows Server 2003, Standard Edition (32-bit x86)
- Microsoft Windows Server 2003, Enterprise Edition
- Microsoft Windows Server 2003, Standard x64 Edition
- Microsoft Windows Server 2003, Enterprise x64 Edition
- Microsoft Windows Server 2003, Datacenter x64 Edition
- Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
- Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
SYMPTOMS
Consider the following scenario. A client computer connects to a Microsoft Windows 2000-based computer that has Terminal Services enabled. Additionally, the following conditions are true:
- The client computer is running an earlier operating system, such as Microsoft Windows 98.
- You have a mixed Terminal Services Licensing environment that has both Windows 2000 Server-based and Windows Server 2003-based license servers.
- The Windows 2000 Server-based license servers do not have any permanent CALs available.
- The Windows Server 2003-based license servers do have permanent CALs available.
In this scenario, the client computer does not receive a permanent Per Device client access license (CAL) from a Windows Server 2003-based license server.
Note You experience this problem intermittently. Sometimes, the client computer that has the earlier operating system installed may receive a permanent Per Device CAL from a Windows Server 2003-based license server.
CAUSE
There is a problem in the Windows Server 2003 version of the Lserver.exe program. This problem prevents Windows 2000 Server-based license servers from detecting a valid Per Device CAL that exists on a Windows Server 2003-based license server. Therefore, when a Windows 2000 Server-based license server has no permanent Per Device CALs available, this license server does not forward the CAL request to the Windows Server 2003-based license servers in the mixed Terminal Services environment.
In a mixed Terminal Services environment, the Windows 2000-based computer that is running Terminal Services may sometimes contact a Windows 2000 Server-based license server to obtain a Per Device CAL. In this situation, the client computer does not receive a permanent Per Device CAL even when a valid Per Device CAL exists on a Windows Server 2003-based license server. Instead, the client computer receives a temporary license from a Windows 2000 Server-based license server.
RESOLUTION
Service pack information
To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
889100 How to obtain the latest service pack for Windows Server 2003
Hotfix information
Prerequisites
No prerequisites are required to apply this hotfix.
Restart requirement
You do not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Windows Server 2003, 32-bit editions
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Lserver.exe | 5.2.3790.2587 | 349,184 | 08-Dec-2005 | 03:22 | x86 |
Windows Server 2003, x64 editions
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Lserver.exe | 5.2.3790.2587 | 538,112 | 08-Dec-2005 | 05:32 | x64 |
Windows Server 2003, for Itanium-based systems
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Lserver.exe | 5.2.3790.2587 | 996,352 | 08-Dec-2005 | 05:33 | IA-64 |
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2.
MORE INFORMATION
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Additional query words: TS legacy
Keywords: kbbug kbfix kbqfe kbtermserv kbpubtypekc kbhotfixserver kbwinserv2003sp2fix KB911288
