Licensing Protocol Error

[b***@nc.rr.com]

This began happening as I rolled out laptops with a new xp pro image.
I've tried deleting the mslicensing key on the client and various
suggested keys on the server. It looks as though one client is holding
on the temporary lic. Any ideas?

[b***@nc.rr.com]

Post by b***@nc.rr.com
This began happening as I rolled out laptops with a new xp pro image.
I've tried deleting the mslicensing key on the client and various
suggested keys on the server. It looks as though one client is holding
on the temporary lic. Any ideas?

Here are the error message on the terminal server:
The terminal services license grace period has expired and the service
has not registered with a license server.
A terminal services license server is required for continuous
operation.
A terminal server can operate w/o a license for 90 days after initial
install.

Also this error
The terminal server cannot issue a license

The license server is on a dc. This is strictly a windows 2000
environment with a combination of 2000 and xp and a couple of
powerbooks on the client side.

There is no temp key available. And that particular user is a
powerbook user. I am wondering if not having the apple cal has caused
this issue but no new connection can be created. Existing connections
are still allowed.

I've done registry key deletion on the client and server to no avail.

I cannot choose activate either from the license server.

If this did indeed expire it last much more than 90 days. I've been
here since October and it was put in place by my predeccessory.

[Vera Noest [MVP]]

Are there any EventLog errors on the DC (the Licensing Server)?
Since the problem seems to be with the Licensing Server itself, or
possibly between the Terminal Server and the Licensing Server, it
makes sense that deleting the licensing key on the client doesn't
help. It also means that your other clients will probably stop
functioning once their current license expires.

Since the LS is running on the DC, discovery should not be a
problem. But I would check it anyway. Maybe the preferred license
server was hardcoded into the registry, and is pointing to the
wrong server? Check this article for the registry key to examine,
note that you should *not* need this key at all:

239107 - Establishing Preferred Windows 2000 Terminal Services
License Server
http://support.microsoft.com/?kbid=239107

If that doesn't fix things, I would try the following:

A) Deactivate and then reactivate the Licensing Server
Assuming that this procedure can be completed without errors (check
the EventLog on both TS and LS), delete the licensing key from a
client and try to connect *twice*. The first connection should
issue a temporary license, the second connection should records a
"Existing Windows 2000 TS CAL" in the Licensing Server Manager.

306578 - HOW TO: Deactivate or Reactivate a License Server Using
Terminal Services Licensing
http://support.microsoft.com/?kbid=306578

B) If plan A doesn't work, you might have to uninstall the LS
completely, delete the licensing database, reboot, and install the
LS again. If you have any purchased TS CALs, you will have to phone
the Clearinghouse to get them re-issued, so make sure you make a
note of the number of purchased TS CALs and dig out your license
agreement paperwork before you uninstall the LS.

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---

Post by b***@nc.rr.com

Post by b***@nc.rr.com
This began happening as I rolled out laptops with a new xp pro
image. I've tried deleting the mslicensing key on the client
and various suggested keys on the server. It looks as though
one client is

holding

Post by b***@nc.rr.com
on the temporary lic. Any ideas?

The terminal services license grace period has expired and the
service has not registered with a license server.
A terminal services license server is required for continuous
operation.
A terminal server can operate w/o a license for 90 days after
initial install.
Also this error
The terminal server cannot issue a license
The license server is on a dc. This is strictly a windows 2000
environment with a combination of 2000 and xp and a couple of
powerbooks on the client side.
There is no temp key available. And that particular user is a
powerbook user. I am wondering if not having the apple cal has
caused this issue but no new connection can be created.
Existing connections are still allowed.
I've done registry key deletion on the client and server to no
avail.
I cannot choose activate either from the license server.
If this did indeed expire it last much more than 90 days. I've
been here since October and it was put in place by my
predeccessory.