Re: Terminal Services Licensing question

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



But do you have free TS CALs available? You wrote that 10 TS CALs are
installed and used, and 6 temporary TS CALs. If all permanent TS CALs
are in use, then new clients get a temporary license, but only *once*
per client. After that, they need a permanent one.

Alternatively, assuming that you do *not* run SP1, this could be an
indication that you have the problem described here (is fixed in
SP1):

834651 - Terminal Services licensing mode changes from Per User or
from Per Device to an invalid value after you add or remove a Windows
component
http://support.microsoft.com/?kbid=834651

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
SQL troubleshooting: http://sql.veranoest.net
*----------- Please reply in newsgroup -------------*

=?Utf-8?B?Y2hpbnpl?= <chinze@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on
31 mar 2006:

I just tried it and got this Error Message at the client "The
remote computer has ended the connection." I didn't see
anything new in the Event Viewer of the server, but I did find
this error message related to Terminal Services from the
past...earlier today....."The Terminal Server Licensing server
CA02 has no permanent licenses for product 'Windows Server 2003
- Terminal Server Per Device CAL Token'. Use Terminal Server
Licensing administrative tool to register more licenses. The
Terminal Server '67.52.51.101' was refused licenses of type
'Windows Server 2003 - Terminal Server Per Device CAL Token' due
to this condition."...EventID 21 TermServLicening.

Is this an activation issue and if so, why would hit hand out 10
permenant licenses and 6 temp if it wasn't activated? I don't
understand the TS licensing very well. Your help is greatly
appreciated.

"Vera Noest [MVP]" wrote:

And what does the EventLog say?
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
SQL troubleshooting: http://sql.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?Y2hpbnpl?= <chinze@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
on 30 mar 2006 in microsoft.public.windows.terminal_services:

Sorry for the confusion. The licensing was done before I
took over this account. From the looks of it it's licensed
on a Per Device basis, so I have changed the configuration
setting back to Per Device.

I did remove the temp license from one of the clients that
was having a problem ans was still unable to connect to TS on
that server. It is able to connect to other TS servers in
other locations.

"Vera Noest [MVP]" wrote:

Just to cover the basics:
the TS CALs which you installed on the TS Licensing Server
are "Per User" TS CALs, correct?
And you have changed the licensing mode on the Terminal
server to use the "Per User" licensing mode as well (in TS
Configuration)?

Which Event is logged in the EventLog on the TS when the
clients are refused?

I would start to delete the locally stored temporary license
from one of the clients that can't connect:

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

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

=?Utf-8?B?Y2hpbnpl?= <chinze@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote on 30 mar 2006 in
microsoft.public.windows.terminal_services:

Thanks for that info. I'm having a license problem
though. I have three computers that connect through VPN
and have been issued temporary TS licenses in the past
that are not expired, but they are unable to make the TS
connection even though the VPN connection works fine. Any
new computers that attempt to gain TS access through the
VPN have no problem. Any ideas? There are 10 TS licenses
installed and being used and 6 temporary licenses listed
on the licensing server.


"Vera Noest [MVP]" wrote:

Since your terminal Server runs on 2003, the TS Licensing
Service must also run on 2003. So it's running on the
right server.

The licensing mode of the server must match the type of
licenses that you bought and installed on the TS
Licensing Server.
_________________________________________________________
Vera Noest MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
SQL troubleshooting: http://sql.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?Y2hpbnpl?= <chinze@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote on 23 mar 2006 in
microsoft.public.windows.terminal_services:

I have a similar situation, only in reverse. My 2000
SBS is the domain controller, while the 2003 Server is
the Terminal Server with the applications installed.
The 2003 Server is also acting as the VPN or Remote
Access Server and currently has the Terminal Server
Licensing installed with 10 licenses issued and 6 temp
licenses issued. We've been having problems with some
former clients gaining access while some new clients
have been given access to TS.

My question is two fold. Which Server should be
running the TS licensing? After reading the other
posts, I think I understand the temp licensing based on
the random time alottment for expiration. However, I
have changed the licensing to Per User from Per Device.
Do I need to restart the 2003 Server or deactivate and
reactivate the licensing in order for this to change?

Thanks for the help.
.



Relevant Pages

  • Re: Remove Terminal Server Temporary licences
    ... And which type of TS CALs have you installed, ... Check in Administrative tools - Terminal Server Licensing ... And does the Terminal Server Licensing Manager find the TS ...
    (microsoft.public.windows.terminal_services)
  • Re: TS Licensing - per-device to per-user
    ... User licensing mode, none of your licenses will ever be issued, ... To use User and Device TS CALs simultaneously on one ... Terminal Server, the server must be configured for Per User TS ...
    (microsoft.public.windows.terminal_services)
  • Re: Windows 2000 terminal servers in 2003 domain
    ... Server 2003 Terminal Server Licensing White paper. ... You can install your existing W2K TS CALs on a 2003 TS Licensing ...
    (microsoft.public.windows.terminal_services)
  • Re: License Service
    ... Q. What are the differences between user CALs and device CALs? ... A user CAL permits one user to access the server ... No. SBS 2003 R2 CALs are not concurrent. ... details the licensing mode is set to per server for x concurrent ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS2003 License Disappears - Now shows 1 as Maximum
    ... to use the Licensing module in Server Management to back up the CALs. ... are built-in wizards there to backup and restore your CALs. ...
    (microsoft.public.windows.server.sbs)