Re: terminal server that hands out licenese to other servers..
- From: "Josh Rosenberg [MSFT]" <joshrose@xxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 19 Dec 2006 15:07:05 -0800
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@xxxxxxxxxxxxxxxxxxxxxxxIn 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@xxxxxxxxxxxxxxxxxxxxxxxHi 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
.
- Follow-Ups:
- Re: terminal server that hands out licenese to other servers..
- From: Vera Noest [MVP]
- Re: terminal server that hands out licenese to other servers..
- From: DBA Dude
- Re: terminal server that hands out licenese to other servers..
- References:
- terminal server that hands out licenese to other servers..
- From: Mr. Smith
- Re: terminal server that hands out licenese to other servers..
- From: guyyardeni
- Re: terminal server that hands out licenese to other servers..
- From: DBA Dude
- terminal server that hands out licenese to other servers..
- Prev by Date: Re: Allow Users to Shadow Sessions
- Next by Date: Re: terminal server that hands out licenese to other servers..
- Previous by thread: Re: terminal server that hands out licenese to other servers..
- Next by thread: Re: terminal server that hands out licenese to other servers..
- Index(es):
Relevant Pages
|