Re: License Expiration on TS
- From: "Vera Noest [MVP]" <vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 20 Apr 2005 13:03:39 -0700
This is by design. Nothing to worry about.
"Permanent" TS CALs have an expiration date of 52-89 days after
issueing. This is to avoid a situation were the license is
permanently issued to a client, and therefor permanently lost when
the client is discarded or re-installed from scratch.
The client will automatically try to renew the license, starting 7
days before the expiration date. If the client doesn't connect to
the Terminal Server within this 7 day period, the license expires
and is automatically returned to the Licensing Server.
--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---
"=?Utf-8?B?REM=?=" <DC@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 20 apr
2005 in microsoft.public.win2000.termserv.clients:
> I may have a licensing issue. Previously I had problems with
> clients using Temporary Licenses (HP thin clients), and then
> they expired after something like 90 days. So I just went and
> had the customer purchase some Terminal Server CAL's which
> installed fine, but now it shows up with an "Expiration Date" of
> almost exactly 90 days from when the previous Temporary Client
> licenses expired. Does it do like a recheck every 90 days?
> Should I be concerned? (Does the licensing work like a DHCP
> lease?) Should I be using User mode vs. Seat mode?
>
> Thanks a bunch in advance!
.
- Follow-Ups:
- Re: License Expiration on TS
- From: DC
- Re: License Expiration on TS
- References:
- License Expiration on TS
- From: DC
- License Expiration on TS
- Prev by Date: Help with the TS WEB Connections Hanging
- Next by Date: Re: License Expiration on TS
- Previous by thread: License Expiration on TS
- Next by thread: Re: License Expiration on TS
- Index(es):
Relevant Pages
|