You cannot install the Terminal Services CAL pack on Windows Server 2003-based or W...

Page 1 of 5

You cannot install the Terminal Services CAL pack on Windows Server
2003-based or Windows 2000 Server-based computers
View products that this article applies to.

On This Page
SYMPTOMS Article ID : 839878
Last Review : June 17, 2008
CAUSE
Revision : 5.0
RESOLUTION
Cause 1: You are trying to install a Windows Server 2008 CAL pack on a Windows Server 2003-based license
server
Cause 2: You are trying to install a Windows Server 2003 CAL pack on a Windows 2000-based license server
Cause 3: The Terminal Services Licensing component is corrupted or missing
Part 1: Remove the Terminal Services Licensing component
Part 2: Reinstall the Terminal Services Licensing component
Cause 4: The Terminal Services registry key has incorrect settings
MORE INFORMATION
STATUS

SYMPTOMS
When you try to install the Terminal Services client access license (CAL) pack on a Windows Server 2003-based or a
Microsoft Windows 2000 Server-based server, you may receive the following error message:

Licensing Wizard was unable to install the client license key pack. Please verify your entry and
try this operation again. Message Number 0x13A7.

Note The message number may also be 0x13A4 or 0xFA1.

The following event ID error message may be logged in the application event log:

Event ID: 41
Source: TermServLicensing
Description: Can't initialize policy module because of error 'Missing Policy module registry entry for product Microsoft
Corporation, company 004'

CAUSE
This problem may occur for one or more of the following reasons:

• Cause 1: You are trying to install a Windows Server 2008 CAL pack on a Windows Server 2003-based license
server.
• Cause 2: You are trying to install a Windows Server 2003 CAL pack on a Windows 2000-based license server.
• Cause 3: The Terminal Services Licensing component is corrupted or missing.
• Cause 4: The Terminal Services registry key has incorrect settings.

RESOLUTION

Cause 1: You are trying to install a Windows Server 2008 CAL pack on a Windows Server
2003-based license server
A Windows Server 2008-based terminal server cannot communicate with a Windows Server 2003-based Terminal
Services licensing server. However, a terminal server that is running Windows Server 2003 can communicate with a
licensing server that is running Windows Server 2008.

To resolve this problem, you must configure a Windows Server 2008-based computer as your licensing server.

Cause 2: You are trying to install a Windows Server 2003 CAL pack on a Windows 2000-
based license server
Because you cannot install a Windows Server 2003 CAL pack on a Windows 2000-based license server, you must use

http://support.microsoft.com/?id=839878 30/09/2008
You cannot install the Terminal Services CAL pack on Windows Server 2003-based or W... Page 2 of 5

one of the following options to resolve this problem:

• Install the Terminal Services Licensing component on a Windows Server 2003-based computer, and then install
the Windows Server 2003 CAL pack on the Windows Server 2003 license server.
• Keep the Terminal Services Licensing component on a Windows 2000-based license server. To do this, use one
of the following options:
• Contact the retailer if you obtained the CAL pack through a retail channel.
• Contact the Microsoft Registration Authority and Clearinghouse to downgrade the Terminal Services
License CAL pack to be compatible with Microsoft Windows 2000 Terminal Servers.

To contact the Registration Authority and Clearinghouse in the United States, call (888) 571-2048.

To access the Registration Authority and Clearinghouse from outside the United States, follow these steps:
1. Click Start, point to Programs, click Administrative Tools, and then click Terminal Services
Licensing.
2. In the Terminal Services Licensing console, right-click your license server, and then click
Properties.
3. Click Connection Method, and then click Telephone.
4. Click the appropriate country, and then click OK.
5. On the Action menu, click Install Licenses, and then click Next.
6. Call the appropriate Customer Service Center by using the telephone number that is displayed.
7. Click Cancel to exit the Terminal Services Licensing console.

Cause 3: The Terminal Services Licensing component is corrupted or missing

If the Terminal Services Licensing component (Tls236.dll) is corrupted or missing, remove the component and then
reinstall it. To do this, use the following two-part procedure.

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious
problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps
carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a
problem occurs. For more information about how to back up and restore the registry, click the following article
number to view the article in the Microsoft Knowledge Base:

322756 (http://support.microsoft.com/kb/322756/) How to back up and restore the registry in Windows

Part 1: Remove the Terminal Services Licensing component

1. Click Start, Point to Settings, and then click Control Panel.

2. Double-click Add/Remove Programs.
3. Click Add/Remove Windows Components.
4. In the Windows Components Wizard, click to clear the Terminal Services Licensing check box, and then
click Next.
5. Click Finish.
6. Rename the %windir%\System32\Lserver folder, where %windir% is the path of your Windows folder.

For example, rename %windir%\System32\Lserver to %windir%\System32\Lserver2.

7. Delete the MSLicensing subkey from the registry. To do this, follow these steps:
a. Click Start, click Run, type regedit, and then click OK.
b. Locate the following registry subkey:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing

c. Right-click MSLicensing, and then click Delete.

d. Quit Registry Editor.

Part 2: Reinstall the Terminal Services Licensing component

http://support.microsoft.com/?id=839878 30/09/2008
You cannot install the Terminal Services CAL pack on Windows Server 2003-based or W... Page 3 of 5

1. Click Start, point to Settings, and then click Control Panel.

2. Double-click Add/Remove Programs.
3. Click Add/Remove Windows Components.
4. In the Windows Components Wizard, click to select the Terminal Services Licensing check box, and then
click Next.
5. Click Your entire enterprise or click Your domain or workgroup.
6. Select the license server database location, and then click Next.
7. Click Finish.

Cause 4: The Terminal Services registry key has incorrect settings

To verify that the Terminal Services Licensing registry key contains the correct settings, follow these steps.

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious
problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps
carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a
problem occurs. For more information about how to back up and restore the registry, click the following article
number to view the article in the Microsoft Knowledge Base:

322756 (http://support.microsoft.com/kb/322756/) How to back up and restore the registry in Windows

1. Click Start, click Run, type regedit, and then click OK.
2. In Registry Editor, locate the following registry subkey:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\TermServLicensing\Policy\Microsoft Corporation\A02

3. Make sure that the registry subkey contains the following entry:
• String Name: DLL
• String Value: %systemroot%\System32\tls236.dll
4. If the DLL entry does not contain the correct value data, modify the value. To do this, follow these steps:
a. In Registry Editor, right-click DLL, and then click Modify.
b. In the Value data box, type %systemroot%\System32\tls236.dll, and then click OK.

5. If the registry subkey does not contain the DLL entry, you must manually add it. To do this, follow these
steps:
a. In Registry Editor, right-click the following registry subkey:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\TermServLicensing\Policy\MicrosoftCor
poration\A02

b. Point to New, and then click String Value.

c. Type DLL, and then press ENTER.
d. Right-click DLL, and then click Modify.
e. In the Value data box, type the following, and then click OK:

%systemroot%\System32\Tls236.dll

6. Exit Registry Editor.

7. Reactivate the license server.

For more information about how to reactivate the license server, click the following article number to view the article
in the Microsoft Knowledge Base:

814593 (http://support.microsoft.com/kb/814593/) How to deactivate or reactivate a license server by using

Terminal Services licensing

MORE INFORMATION

http://support.microsoft.com/?id=839878 30/09/2008
You cannot install the Terminal Services CAL pack on Windows Server 2003-based or W... Page 4 of 5

You can install the existing Windows Server 2003 terminal server CALs on a Windows Server 2008 licensing server.
The Windows Server 2008 licensing server issues CALs to the corresponding terminal servers based on the operating
system of the terminal server. For example, if you have both Windows Server 2008-based and Windows Server 2003-
based terminal servers in the network, a Windows Server 2008-based licensing server issues the correct CAL to each
terminal server based on the operating system that the terminal server is running.

For help in transferring your terminal server client access licenses from a down-level terminal services licensing server
to a Windows Server 2008-based terminal services licensing server, contact the Microsoft Product Activation Group at
1-888-571-2048.

The Microsoft Product Activation Group also provides help for the following Terminal Services-related tasks:

• Activate a license server

• Install licenses on a license server
• Reinstall licenses on a license server
• Downgrading licenses

STATUS
This behavior is by design.

APPLIES TO
• Microsoft Windows Server 2003, Web Edition
• Microsoft Windows Server 2003, Standard Edition (32-bit x86)
• Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
• Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
• Microsoft Windows 2000 Datacenter Server
• Microsoft Windows 2000 Advanced Server
• Microsoft Windows 2000 Server
• Microsoft Windows 2000 Professional Edition
• Windows Server 2008 Standard
• Windows Server 2008 Enterprise
• Windows Server 2008 Standard without Hyper-V
• Windows Server 2008 for Itanium-Based Systems
• Windows Server 2008 Enterprise without Hyper-V

Keywords: kbprb KB839878

Provide feedback on this information

Did this information solve your problem?

j Yes
k
l
m
n
j No
k
l
m
n
j I don't know
k
l
m
n
Was this information relevant?

j Yes
k
l
m
n
j No
k
l
m
n

http://support.microsoft.com/?id=839878 30/09/2008
You cannot install the Terminal Services CAL pack on Windows Server 2003-based or W... Page 5 of 5

What can we do to improve this information?

To protect your privacy, do not include contact information in your feedback.

Submit

Help and Support ©2008 Microsoft

http://support.microsoft.com/?id=839878 30/09/2008