Re: Event ID 1004 - Windows 2000 Terminal Server - Windows Ce.Net Clie

Tech-Archive recommends: Fix windows errors by optimizing your registry

Check in the EventLog on the Terminal Server if you see any Event
1010 indicating the that TS cannot locate the LS. If you have
those, check your DefaultLicenseServer parameter.

But I assume that you won't find Event 1010, only Event 1004, and
that you see in TS Licensing manager that the client has received
a temporary license, which is now expired.
If that's the case, the problem lies in the client, not in the
terminal Server or the TS Licensing Server.

There are a number of problems with license renewal, which are
specific for thin clients. This is what you can try:
* update the firmware of your client to the latest version.
* delete the locally stored expired license from the clients
registry. If your clients doesn't have an option to delete the
license key, you can reset it to the factory defaults to achieve
this.

If that doesn't help, check the following KB articles:

825027 - Terminal Services Licensing Denies Your Connection to
Your Terminal Server from Your WBT Device
http://support.microsoft.com/?kbid=825027

827355 - Event ID 1004 is logged when a thin client tries to
obtain a Terminal Services license
http://support.microsoft.com/?kbid=827355

_________________________________________________________
Vera Noest
MCSE,CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
*----------- Please reply in newsgroup -------------*

"=?Utf-8?B?R3VzdGF2byBSaW5nZWw=?="
<GustavoRingel@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 12 jul 2005:

> Hi, I have worked in the 90 day test period without problems
> with a CE.NET thin client and a 2000 Terminal Services Server.
> I bought two licenses now to keep doing tests from my Handheld
> Terminal. I activated the server and installed the licenses by
> phone.
>
> Now I'm able to enter to the server from my desktop computer but
> the CE.NET is getting the message "This client could not connect
> to the remote computer" and on the server i see event 1004, "The
> terminal server cannot issue a client license. "
>
> In terminal services licensing i see that i have 2 licenses
> available and no license issued...
>
> I tried reinstalling, activating again by the internet, by
> phone...setting the DefaultLicenseServer parameter...i don't
> know what else to tray...
>
> Gustavo.
.

Relevant Pages

  • 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)
  • kb 187614
    ... Just delete the registry key ... If an unlicensed client connects to a Terminal Server for the first time, ... Access License token. ...
    (microsoft.public.de.german.windows.terminaldienste)
  • Re: Office Licencing on TS Server
    ... MCSE, CCEA, Microsoft MVP - Terminal Server ... Office runs locally on the client or inside a TS session on the ... correctly license Office on a Terminal Services Server. ... server with say 25 office licences so that 25 users can ...
    (microsoft.public.windows.terminal_services)