kb 187614



Hallo,

wir haben TC, die per RD auf einen W3k TS zugreifen.

Ab und zu kommt event id 1028.

Meine Frage gibt es eine "saubere" (elegantere) Lösung für dieses Problem
als unten beschrieben?

Gruß Ingo


#######################################################################################################

Die Lösung:

Anonymous (Last update 8/12/2004):
Just delete the registry key
"HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing" and try again. Details
can be found in M187614.

Die KB: http://support.microsoft.com/kb/187614/de

sagt:

Removing Terminal Server licenses from an RDP client
View products that this article applies to.
Article ID : 187614
Last Review : October 11, 2007
Revision : 6.3

This article was previously published under Q187614
Important This article contains information about how to modify the
registry. Make sure that you back up the registry before you modify it. Make
sure that you know how to restore the registry if a problem occurs. For more
information about how to back up, restore, and modify the registry, click
the following article number to view the article in the Microsoft Knowledge
Base:
256986 (http://support.microsoft.com/kb/256986/) Description of the
Microsoft Windows registry
SUMMARY
If an unlicensed client connects to a Terminal Server for the first time,
the Terminal Server issues the client a temporary Terminal Server Client
Access License (CAL) token. After the user has logged into the session, the
Terminal Server instructs the License Server to mark the issued temporary
Terminal Server CAL token as being validated. The next time the client
connects, an attempt is made to upgrade the validated temporary Terminal
Server CAL token to a full Terminal Server CAL token. If no license tokens
are available, the temporary Terminal Server CAL token will continue to
function for 90 days. The license is stored in the client's registry.

Thirty-two bit RDP clients store their license under the key
HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing.

Warning Serious problems might occur if you modify the registry incorrectly
by using Registry Editor or by using another method. These problems might
require that you reinstall the operating system. Microsoft cannot guarantee
that these problems can be solved. Modify the registry at your own risk.

To clean the client's license cache, just delete this key and its subkeys.
The next time the client connects to the server, it will obtain another
license.

For 16-bit RDP clients, run regedit /v. Then delete the keys under
"\Software\Microsoft\MSLicensing" to clean the client's license cache. You
can also delete the BIN files from \Windows\System\Regdata.

The RDP client for Macintosh stores the license in a file on the local
computer in the folder hierarchy under /users/Shared/Microsoft/RDC Crucial
Server Information/. To clean the Macintosh client's license cache, delete
the contents of this folder. The client will try to obtain a new license
from the server the next time that it connects.

If you delete the HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing subkey
on a client that is running Windows Vista or a later version, later attempts
to connect to a Terminal Server may fail. Also, you receive the following
error message:
An Error occurred in the Licensing Protocol
To resolve this problem, right-click the Remote Desktop Connection shortcut,
and then click Run as Administrator. By default, the remote desktop
connection runs as a user with the lowest user permissions. By default, a
restricted user does not have permission to write registry entries to
HKEY_LOCAL_MACHINE. Therefore, attempts to rewrite the MSLicensing key fail.
Starting Remote Desktop Connection with administrative credentials provides
the permissions that are necessary to write the needed registry keys.


.



Relevant Pages

  • Re: "The client could not connect to the remote computer. Remote connections..." - Server 2003
    ... then the certificate on the terminal server might be ... On each terminal server and client, ... create a backup of the registry. ... If you need to restore this registry subkey in the future, ...
    (microsoft.public.windows.server.networking)
  • RE: Dont know what to head this?????
    ... MCSE, CCEA, Microsoft MVP - Terminal Server ... it, but surface to say the license server gets it wrong, so ... But in the K8 management app each terminal ... option and choose to load their client as the explorer. ...
    (microsoft.public.windows.terminal_services)
  • Re: per Device CAL
    ... >>> from a non-authorized client. ... >>> Let me give you an example: assume that you have 10 TS CALs, ... >>> thanks to its temporary license. ... >>> Noest MCSE, CCEA, Microsoft MVP - Terminal Server ...
    (microsoft.public.windows.terminal_services)
  • Re: Licensing problem
    ... Have you tried to delete the temporary license from the client (by ... Terminal Server from Your WBT Device ... TS licensing server shows a valid licence ...
    (microsoft.public.win2000.termserv.apps)
  • RE: Event 1004 Terminal Server Cannot issue a client license
    ... CAL user F will be granted a temporary license. ... client, which is good for 30 days. ... You must first buy and install TS CALs for your CE thin clients. ... MCSE, CCEA, Microsoft MVP - Terminal Server ...
    (microsoft.public.win2000.termserv.apps)

Loading