Does anyone know terminal server licensing?

Hi guys,

I'm trying to determine when my devices won't be able to connect to the
terminal server any longer. I haven't purchased any CALS, but have the
Terminal Server Licencing Server installed. I noticed that some of my
devices temporary licenses have expired on December 5th. They are still
able to access the Terminal Server no problem - but won't they be able
to connect. I've asked this question before, but sadly got no reply.
Please guys, I need your help.

Thanks in advance,
Cyp.

http://www.brianmadden.com/content/content.asp?id=154

Found via 5 second google search for Microsoft Terminal Server licensing...

"Cyphos" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ups.com...
> Hi guys,
>
> I'm trying to determine when my devices won't be able to connect to the
> terminal server any longer. I haven't purchased any CALS, but have the
> Terminal Server Licencing Server installed. I noticed that some of my
> devices temporary licenses have expired on December 5th. They are still
> able to access the Terminal Server no problem - but won't they be able
> to connect. I've asked this question before, but sadly got no reply.
> Please guys, I need your help.
>
> Thanks in advance,
> Cyp.
>

> 9. The user's credentials are validated. If the user successfully authenticates, the >Terminal Server contacts the license server a second time. This time around, the >Terminal Server informs the license server that the TS CAL that was sent to the client >should be marked as "valid." If the user did not successfully authenticate, (i.e. the >connection was from an inappropriate user), the Terminal Server will not contact the >license server, and the li-cense that was sent out will not be marked "valid."
> 10. The next time that client device connects, it presents its
90-day temporary TS >CAL to the Terminal Server.
> 11. The Terminal Server contacts the license server. Since the
licensing server >marked the CAL as valid the first time the user
authenticated, the client device's >temporary CAL is up-graded to a
full CAL. If, for some reason, all of the license servers >have
depleted their in-ventories of TS CALs, the client device keeps its
temporary >90-day TS CAL certificate. As long as the 90-day certificate
has not expired, the client >device can still connect, even with no
available licenses on any license servers.

>An unlicensed client device will always be granted a temporary 90-day TS CAL at the >ime of its first connection. Only after successful authentication and a second logon is >the temporary TS CAL upgraded to a full TS CAL. This two-stage licensing process is >used to ensure that TS CALs are only assigned to authenticated users. Previously >(before hotfix 287687 or Windows 2000 Ser-vice Pack 3) any user that connected was >assigned a full TS CAL, even if he did not belong on the system. The full TS CAL >certificate was granted at connection time, before the logon screen even popped up. If >a user thought, "Oops, I don't belong on this system!" it was too late-his client device >had already received a full TS CAL certificate, even if the administrator never meant for >him to access the system. This circumstance often led to license servers running out >of TS CALs.

My licensing server is activated. So my devices will never be denied
access?

You need to install licenses for TS, not just run the service.


"Cyphos" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) oups.com...
> > 9. The user's credentials are validated. If the user successfully
authenticates, the >Terminal Server contacts the license server a second
time. This time around, the >Terminal Server informs the license server that
the TS CAL that was sent to the client >should be marked as "valid." If the
user did not successfully authenticate, (i.e. the >connection was from an
inappropriate user), the Terminal Server will not contact the >license
server, and the li-cense that was sent out will not be marked "valid."
> > 10. The next time that client device connects, it presents its
> 90-day temporary TS >CAL to the Terminal Server.
> > 11. The Terminal Server contacts the license server. Since the
> licensing server >marked the CAL as valid the first time the user
> authenticated, the client device's >temporary CAL is up-graded to a
> full CAL. If, for some reason, all of the license servers >have
> depleted their in-ventories of TS CALs, the client device keeps its
> temporary >90-day TS CAL certificate. As long as the 90-day certificate
> has not expired, the client >device can still connect, even with no
> available licenses on any license servers.
>
> >An unlicensed client device will always be granted a temporary 90-day TS
CAL at the >ime of its first connection. Only after successful
authentication and a second logon is >the temporary TS CAL upgraded to a
full TS CAL. This two-stage licensing process is >used to ensure that TS
CALs are only assigned to authenticated users. Previously >(before hotfix
287687 or Windows 2000 Ser-vice Pack 3) any user that connected was
>assigned a full TS CAL, even if he did not belong on the system. The full
TS CAL >certificate was granted at connection time, before the logon screen
even popped up. If >a user thought, "Oops, I don't belong on this system!"
it was too late-his client device >had already received a full TS CAL
certificate, even if the administrator never meant for >him to access the
system. This circumstance often led to license servers running out >of TS
CALs.
>
> My licensing server is activated. So my devices will never be denied
> access?
>