Microsoft KB Archive/834651

= Terminal Services licensing mode changes from Per User or from Per Device to an invalid value after you add or remove a Windows component =

Article ID: 834651

Article Last Modified on 7/24/2007

-

APPLIES TO


 * Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems

-





Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry



SYMPTOMS
An invalid setting in the registry may be set in the  subkey on your Microsoft Windows Server 2003-based computer that is configured as a terminal server using a Per User or Per Device licensing setting. This may unexpectedly change the terminal server licensing mode and cause the terminal server to obtain only temporary licenses.



CAUSE
This problem occurs when you use the Windows Components Wizard in Add/Remove Programs to add or to remove a Windows component.

The value of the PolicyAcOn registry entry changes from either 2 for Per Device mode or 4 for Per User mode to an invalid value of 0. Because of this invalid value, the terminal server is not aware of the type of licenses it should obtain. Therefore, the terminal server starts trying to obtain temporary, Per Device licenses. The terminal server configuration shows only Per Device as the licensing mode setting. Therefore, to determine whether the problem described here has occurred, examine the value of the PolicyAcOn registry entry.



Hotfix information
A supported hotfix is now 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 service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Prerequisites
No prerequisites are required.

Restart requirement
You do not have to restart your 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
  Date         Time   Version       Size     File name 13-Jan-2004 18:17  5.2.3790.118  135,168  Tsoc.dll

Windows Server 2003, 64-Bit Editions
  Date         Time   Version       Size     File name  Platform --  13-Jan-2004  18:15  5.2.3790.118  303,616  Tsoc.dll   IA-64

Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

After you apply the hotfix, you must reset the PolicyAcOn registry entry to the correct setting of either 4 (Per User) or 2 (Per Device) to configure the licensing mode.

NoteWhen you change the value in the registry as described in the following steps, you will not change the setting that is shown in the Terminal server configuration interface.

To reset the registry values, follow these steps:  Click Start, click Run, type regedit, and then click OK. Locate and then click the following registry subkey:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\LicensingCore

 Right-click the PolicyAcOn registry entry, and then click Modify. In the Value data box, type 4, and then click OK.

Note A setting of 2 indicates a Per Device configuration. A setting of 4 indicates a Per User configuration. Quit Registry Editor.</li></ol>

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

<div class="moreinformation_section">

MORE INFORMATION
For additional information about terminal server licensing, click the following article number to view the article in the Microsoft Knowledge Base:

294716 Microsoft Windows Server 2003 Terminal Server Licensing white paper is now available

For additional information about the standard terminology that is used to describe Microsoft software updates, 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

Keywords: kbhotfixserver kbqfe kbbug kbfix kbqfe kbwinserv2003presp1fix KB834651

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.