Re: terminal server that hands out licenese to other servers..

Hmmm, interesting. Well, I'm still a little bit confused here.

I have 100 servers. And I have 19 Terminal Services licenses. I wanted to
spread that across my 100 servers so that if one of my 10 users connect to
ANY of the 100 servers, (and two existing free connections are already
taken), then I want them to be able to log into any of those 100 servers,
therby using one of my 19 terminal server licenses, dymantically.

Is this possible? To dymantically allocate terminal services license to any
of the users that need them while connecting to any of my 100 servers? I
hope I am explaining this clearly enough, as I may not be.

So, if 100 servers are in use, and both free TS sessions are being used, I
want to be able to allow a 3rd or 4th connection on any of the 100 servers,
dymanitcally.

Can Terminal Services work this way?

Thank you again for you help.

Brian


"Josh Rosenberg [MSFT]" <joshrose@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:7E386FBD-31AC-4336-9D91-3D828BBC4D39@xxxxxxxxxxxxxxxx
Application Mode is irrelevant to this. The rule is:
1. If you don't have Terminal Services installed, you are limited to two
connections, ostensibly for remote administration of the machine. No CALs
are involved, so if one of the two sessions ends, that frees up a slot for
another user to login, even if they are using a different machine with a
different user name.
2. If you do have Terminal Services installed, you need licenses on either
a per user or per device basis.
a. In per user mode, a single CAL goes to a single username. Once the
user logs in once, the CAL is theirs. Even if they subsequently
disconnect, the CAL is not reassigned to another user. But if one user
wants to login from 15 different machines, they can do that.
b. In per device mode, you have a set number of devices which obtain
CALs. In theory, every new machine should require an additional CAL. In
practice, per device licensing is not in full effect yet, so you are on
the honor system to obtain the requisite CALs.

In both cases, I believe there is a way to reclaim CALs so expunged users
and/or devices can have their CALs reused, but I'm not familiar with the
details. I'm not 100% on our licensing, so someone else can correct me if
I've left anything out here.

--
Josh Rosenberg [MSFT]
SDE - Terminal Services


"DBA Dude" <Brainb@xxxxxxxxx> wrote in message
news:%23hmvB17IHHA.5104@xxxxxxxxxxxxxxxxxxxxxxx
Hi, I've also been curious about this!

Does that mean you have to install all terminal services in "application
mode" on all servers that will need more than two connections?

Also, when that user disconnects from their TS/RD session, does that free
up the license for another user on another machine?

Thanks ahead of time.

Brian


"guyyardeni" <guyyardeni@xxxxxxxxxxxxxxxxxx> wrote in message
news:Oc6Deh7IHHA.420@xxxxxxxxxxxxxxxxxxxxxxx
In order to have more than 2 people connect to the server, you need to
install Terminal Services using the Add/Remove Programs Control Panel.
To provide licenses for the user connections, install the Terminal
Server Licensing component on a domain controller (also using Add/Remove
Programs) and use the Terminal Server Licensing administration tool to
activate your licenses. Once the licenses are active on a licensing
server, they are available to any terminal server that was configured to
use that licensing server - this is configured when you install Terminal
Services.

--
Guy Yardeni
Remove 9s to email me


"Mr. Smith" <MrSmith@xxxxxxxxx> wrote in message
news:OvVKuL7IHHA.2236@xxxxxxxxxxxxxxxxxxxxxxx
Hi All

I'm trying to figure out how to add my terminal server to allow it to
automatically hand out Terminal services licenses on the fly, as people
need them when connecting via TS/Remote Desktop to other servers in the
domain?

Is the configuration possible? I have 20 licenses (domain), and have a
need to allow more than two people to connect to my windows 2003
servers at any one time.

Is this even possible with terminal services?

Thanks for your help.

M. Smith







.

Relevant Pages

  • Re: Problems with the Windows 2003 License Server
    ... all clients connecting to the 2003 TerminalServerwill use a Per ... CALs Tokens)". ... W2k3) was equipped with 400 TS Cals, terminal servers ... that a licenses will be pulled - Can I make a test ...
    (microsoft.public.windows.terminal_services)
  • Re: Windows 2003 Terminal Licensing Server not issuing licenses
    ... When those existing licenses expire, ... since W2K Terminal Servers cannot use Per ... If you have Software Assurance on your TS CALs, ... > Previously I had 3 Windows 2000 Terminal Servers with each one ...
    (microsoft.public.windows.terminal_services)
  • Re: terminal server that hands out licenese to other servers..
    ... As Josh and others in this thread have explained, TS licenses are ... all servers, install TS Licensing Server, install your 19 TS CALs ... And I have 19 Terminal Services licenses. ...
    (microsoft.public.windows.terminal_services)
  • Re: dummy licenses
    ... Do MSDN subscriptions include CALs for Terminal Services? ... Terminal Services Licensing Instructions for MSDN, ... the licenses so I don't get the error that in 105 days Terminal ...
    (microsoft.public.windows.terminal_services)
  • Re: Terminal Service Licencing problem
    ... Windows 2000/XP client computers do not need TS CAL when connecting to ... days for TS CAL to return back to a pool of available licenses. ... Make sure you have enough per-device TS CALs to cover all pre-W2K devices ... The Terminal Services licensing server CAPTAIN1 has no license ...
    (microsoft.public.windows.terminal_services)