Re: TermServ CAL issued to "Unknown" is locking one of my CALs!



A few comments:

* Renaming the accounts machine to "Unknown" is not going to solve
you problem. The Licensing Server doesn't go after computernames.

* Since a first connection always works with a temporary license,
and a permanent license is issued on the second connection, it is
absolutely sure that the connection was made by someone with a
valid user account (maybe from someones homePC?). You might ask
your users, and warn them not to use a TS connection from any other
client than the ones they should use.

* You cannot revoke issued TS CALs.
TS CALs have an expiration date of 52-89 days after issueing.
Licenses that are not used (because the client does not
connect to the TS anymore) will automatically be returned to the LS
after the expiration date. In the meantime, new clients will get a
temporary TS CAL, which is valid for 90 days.

Note that these time periods are choosen to make sure that a
temporary license lasts long enough for the old license to become
available again. So replacing one client with another can never
cause a licensing problem.
Since you are reaching the end of the 90 day temporary license
period without having TS CALs available, it means that the
connection from the "Unknown" client has not been a one-time event,
it must have been used under an extended period of time.

The only thing you can do is to wait until the license issued to
"Unknown" expires (which means you must make sure that users stop
connecting from unauthorized clients).

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"news" <news@xxxxxxxx> wrote on 16 aug 2005 in
microsoft.public.windows.terminal_services:

> I have a Win2k3 standard server with 7 Terminal Server Per
> Device CALs installed.
>
> The Terminal Server Licensing application shows that the 6 of
> the 7 licenses have been issued to machine names that I
> recognize. But one CAL has been issued to "Unknown". Because
> this per device cal has been issued to "Unknown" my 7th client
> machine (named "Accounts", fwiw) cannot connect to the TermServ.
> They receive the error that
>
> How can I recover this license that has been issued to "Unknown"
> and properly issue it to my accounts machine? (I guess I could
> rename the "accounts" machine to "unknown" and see what happens
> but that would be lame.)
>
> Should I reactivate the license server?
>
> Btw, I have been having no problems for 4 or 5 months until just
> yesterday.
>
> Thanks in advance
>
> john at benjaminconsulting dot com
.



Relevant Pages

  • Re: Terminal Server 2000 in Workgroup to 2003 Domain
    ... state office kept logging on without pulling CALS or Built In Licenses. ... The MS Support person was not able to fix the problem of XP Pro clients ... Now we have an existing client with a temporary license. ... MCSE, CCEA, Microsoft MVP - Terminal Server ...
    (microsoft.public.windows.terminal_services)
  • RE: Event 1004 Terminal Server Cannot issue a client license
    ... by default Windows 2000 client/XP does not require license to connect ... MCSE, CCEA, Microsoft MVP - Terminal Server ... Per User TS CALs, so don't buy those. ... is issued to the client, which is good for 30 days. ...
    (microsoft.public.win2000.termserv.apps)
  • Re: Terminal Service License Server in sbs 2003
    ... You can also get free TS CALs for 2003 for every XP Pro for which ... a Terminal Server running windows 2000 without have to have purchase a TS ... temp license expires, which is why your clients work...for now. ...
    (microsoft.public.windows.server.sbs)
  • Re: Confused about CALs
    ... You mention that the 5 CALs that come with the server do not ... Terminal Services client connection. ... License Server must be activated within 120 days of using the ...
    (microsoft.public.windows.terminal_services)
  • Re: OWA does not respond after login
    ... The restriction of license will limit the users to logon when the CALs are insufficient. ... server to still accept the new users/clients if it is exceeding the CAL limit is aiming to protect your business system; ... it is not a guaranteed feature and we cannot say you can always successfully logon with exceeding the CAL limit. ...
    (microsoft.public.windows.server.sbs)

Loading