Re: Licenses not being issued from 2003 Terminal License Server

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

LSreport and LSview from the Resource Kit.

After you have fixed the detection of the LS by the TS, check the
following as well:
Is the Terminal Server (not the Licensing Server!) set to use "Per
User" licensing? The default is "Per Device".
You can check this from Administrative Tools - Terminal Services
Configuration - Server Settings - Licensing Mode
If it's set to Per Device mode, it will look for a Device TS CAL
and will not issue your Per User TS CALs.

Check this article, it explains that even after you have
switched licensing mode on the TS, your Per User TS CAL count will
not be decremented:

822134 - The Function of Terminal Server CALs in Windows Server
2003
http://support.microsoft.com/?kbid=822134

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

"Ofer B. Ho" <ho@xxxxxxxxxxxxxxxxx> wrote on 12 apr 2005 in
microsoft.public.win2000.termserv.clients:

> We have a Windows 2003 terminal service with a separate 2003
> Server that acts as a license server. I went ahead and manually
> added the License Server to the registry of the Terminal Server
> in order to make sure that it gets its licenses from the correct
> license server.
>
> We have an issue now where our remote users attempt to terminal
> in and get an expired license notice. I checked the 2003
> License Server and could not find any licenses issued to them,
> either Temporary or permanent. None of the permanent User CALs
> are assigned, they are all available.
>
> Is there a tool that will tell us what license server a Terminal
> Server is using and what license server has asssigned a license
> to a client? I think I recall reading somewhere a tool that can
> be run on the client that will tell us this information.
>
> --
> Ofer B. Ho
> Network Administrator
> AeroVironment Inc.
.

Relevant Pages

  • Re: recommended TS license setup
    ... This is not a supported scenario with Per User TS CALs, ... MCSE, CCEA, Microsoft MVP - Terminal Server ... suggested to make a stand alone license server function. ... Most of my machines are members of the ad.nicc domain. ...
    (microsoft.public.windows.terminal_services)
  • Re: Windows CAL Licensing Mode and Terminal Server
    ... I have in fact changed the Windows ... The licensing mode for the server OS (Windows CALs) is completely ...
    (microsoft.public.windows.terminal_services)
  • Re: TS Taking from wrong CAL
    ... You can force the LS to only issue Win2000 CALs to Win2000 TSs by setting this policy: ... A license server attempts to provide the most appropriate Client Access License for a connection. ... a license server provides a Windows 2000 TS CAL token for clients connecting to a terminal server running Windows 2000 and a Windows Server 2003 Family Per Device TS CAL token for a connection to a terminal server running Windows Server 2003. ...
    (microsoft.public.windows.terminal_services)
  • Re: TS Taking from wrong CAL
    ... You can force the LS to only issue Win2000 CALs to Win2000 TSs by setting ... A license server attempts to provide the most appropriate Client Access ... Windows 2000 TS CAL token for clients connecting to a terminal server ...
    (microsoft.public.windows.terminal_services)
  • Re: Windows Server 2003 Terminal Server Licensing
    ... All you need is a license server up and running and the ... terminal servers must be able to find the license server. ... We have a project coming up that will require us to up our TS CALs as well ...
    (microsoft.public.windows.terminal_services)