A client computer does not receive a permanent Per Device CAL from a Windows Server 2003-based license server

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.

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.

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:

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

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

Windows Server 2003, x64 editions

Windows Server 2003, for Itanium-based systems

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.

For more information, click the following article number to view the article in the Microsoft Knowledge Base: