Re: Vera - you're a star!!

From: Stephen Russell (srussell_at_nospam.idi.org.au)
Date: 02/10/05


Date: Fri, 11 Feb 2005 10:01:27 +1100

Hi Vera,

Resetting the thin clients worked!!!! Luckily, we only have 4 in operation
here.

I'll now check out the link for resetting the remote users. But just a
quick look at the article shows that its for Win2K. I know some users have
XP Pro and even Win98. Are the procedures much the same?

Thanks again for your help. And the few hairs left on my head thank you as
well!!!

Stephen

"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message
news:Xns95F9ECD343D36veranoesthemutforsse@207.46.248.16...
If you upgraded from W2K to 2003 a couple of months ago, and your
licensing was initially configured incorrect (Per User TS CALs
instead of Per Device), then it is understandable that your clients
received a temporary license.
These should start to expire by now, which they are doing. So far
everything is by the book. My point with the above is, that the
replacement of the Terminal Server has probably nothing to do with
the expiration of the licenses. It seems to be pure coincidence
that it happened around the same time.

Now for the real problem. Have you checked the EventLog on your
Terminal Server? Can the TS locate the LS? If the EventLog doesn't
give you the reason for the problem, I would delete the temporary
license from at least one client, and see what happens in the LS
Manager. Make sure that you connect at least twice after deleting
the license, since the first connection *always* uses a temporary
license.
For a thin client: reset it to the factory default. For a the W2K
Pro clients:

187614 - Removing Terminal Server Licenses from an RDP Client
http://support.microsoft.com/?kbid=187614

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

"Stephen Russell" <srussell@nospam.idi.org.au> wrote on 10 feb
2005 in microsoft.public.windows.terminal_services:

> Hi All,
>
> Have checked through the posts here and haven't been able to
> find anything that will directly relate to (fix) my problem.
>
> I have 2 servers (Window 2003) - the DC has the TS licensing
> info on it but is only set to Remote desktop for admin. The
> other member server is what users connect into. I have recently
> (within the past few months) upgraded from 2000 to 2003 (both
> servers). I installed the CAL's through MS after we upgraded to
> 2003. I replaced the member server 2 nights ago with a clean
> install of Windows 2003. The next morning we noticed Terminal
> sessions were receiving the message that their temporary licence
> was about to expire in 7 days. I went in and checked the
> licensing detail on the DC and it showed 30 unused CALs in per
> User mode and 20 temporary licenses in per Device CALs. The
> member server was set to Per Device. I checked our Open
> licence agreement and it showed we had 30 Cals per Device - so I
> thought it would be an easy fix to change the CALs from per User
> to Per Device and that would fix the problem. Called MS,
> explained the situation and we removed the per User CALs and
> installed the equivelent per Device CALs.
>
> Unfortunately, it didn't fix the problem. People logging in to
> TS sessions still receive the temporary license is about to
> expire message. And NO licenses are being showed in the DC's TS
> licensing module.
>
> Internal users are accessing the server through thin clients and
> external users are accessing the server through the old Windows
> 2000 TS client software (just thought that have an
> influence...).
>
> Has anyone got any ideas? (And sorry for the long-winded
> explanation but I wanted to give all the details up front).
>
> Cheers,
>
> Stephen
>
> International Diabetes Institute



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: Licensing
    ... a 2nd LS on another server, and then my primary license server ... clients, in which case a dedicated LS could be wise. ... Permanent TS CALs expire after 52-89 days, ...
    (microsoft.public.windows.terminal_services)
  • Re: Licensing
    ... a 2nd LS on another server, and then my primary license server ... clients, in which case a dedicated LS could be wise. ... Permanent TS CALs expire after 52-89 days, ...
    (microsoft.public.windows.terminal_services)
  • Re: Licensing
    ... a 2nd LS on another server, and then my primary license server ... clients, in which case a dedicated LS could be wise. ... Permanent TS CALs expire after 52-89 days, ...
    (microsoft.public.windows.terminal_services)
  • Re: Licensing Process
    ... but why should an activated license server issue a temporary license to ... If a client connects to ...
    (microsoft.public.windows.terminal_services)