Re: Terminal server licensing - bug??

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

Hi Anthony - did this change in a service pack or hotfix? the last time i
setup a 2003 (pre sp1&2) TS in Per User mode it didnt decrement. Would be
great if it did.
Microsoft said this in the article I referenced at that time.. "A Windows
Server 2003-based Terminal Server Licensing Server that is running in TS
User CAL licensing mode does not decrement the number of available Windows
Server 2003 TS CALs when each user connects to the terminal server. This
limitation does not remove the responsibility from administrators to make
sure that a valid TS CAL is obtained for each connected user, per the End
User License Agreement (EULA)." http://support.microsoft.com/kb/823313

Thanks,
Coraleigh Miller

"Anthony" <anthony.spam@xxxxxxxxxxxxxx> wrote in message
news:Ok4Db%23d9HHA.3940@xxxxxxxxxxxxxxxxxxxxxxx
JD,
I think this is just an artefact of your testing.
You need to be aware of the different license requirements for different
versions of client and server. Also, the TS will allocate a temporary
license if it can't contact the licensing server for 90 days after you set
it up, but then it will stop.
You should certainly see all the licenses decremented on the licensing
server,
Anthony
http://www.airdesk.co.uk




"JayDee" <dopamine@xxxxxxxx> wrote in message
news:1189549841.137164.77180@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
In an effort to allow more than two terminal server connections to a
couple of our servers, we built a terminal server licensing server and
applied a license that allocated 50 CAL's - so on the terminal server,
we see 50 licenses total and 50 available (we configured per-user
licenses). We then went to the servers on which we want more than 2
connections, and pointed them to the licensing server - we tried both
auto-detect and specifying the IP address of the licensing server. As
expected, we were then able to create more than two TS connections.

Now for the weird part. On the licensing server itself (The one we're
pointing both servers to), it continues to say "50 licenses total and
50 available" regardless of how many TS connections we make.

So... it appears that we're getting the additional TS connections (in
testing, we got 4 TS connections on each server), but the licensing
server is not acknowledging any of those connections.

Any ideas??

Thanks,
-jd





.

Relevant Pages

  • Re: Terminal Services Licensing question
    ... But do you have free TS CALs available? ... MCSE, CCEA, Microsoft MVP - Terminal Server ... past...earlier today....."The Terminal Server Licensing server ...
    (microsoft.public.windows.terminal_services)
  • RE: Terminal Server Licensing after the 120 day temporary license..
    ... I understand that you have some terminal server ... Each SBS 2003 client access license also authorizes you to access any ... How to configure licensing on an additional Windows server in an SBS network ...
    (microsoft.public.windows.server.sbs)
  • Re: Terminal Service Licence Problems
    ... Licensing problems basically come in 2 flavours: ... Configuration - Server Settings ... 822134 - The Function of Terminal Server CALs in Windows Server ... > But now I can't make anymore connections to my Terminal ...
    (microsoft.public.win2000.termserv.clients)
  • Re: Remove Terminal Server Temporary licences
    ... The temporary Per Device TS CALs that you see in the TS Licensing ... MCSE, CCEA, Microsoft MVP - Terminal Server ... Check in Administrative tools - Terminal Server Licensing ...
    (microsoft.public.windows.terminal_services)
  • Re: Allowing terminal server access to all internally, but only to a select few externally.
    ... access control line that allows access to the terminal server via the ... use tscc.msc to have the default RDP-Tcp connections to use nic1, ... Create a new local user group say 'TS Internet Users', ...
    (microsoft.public.windows.terminal_services)