Re: Per User Cals


Hi,

Due to the network configuration most of these users will be logging into
the one machine. It is only 2 concurrent connections allowed through the
"remote admin" role. I believe they are full blown Terminal Servers as I
have installed the "Terminal Server" software taking them out of remote
administation mode. Is that correct? I would like to use a per Device method
but the users accessing often change and it would be a waste of licences.

In regards to your work around, thats seems a little complicated. I was
under the impressoin that a user could connect to a domain with a Terminal
Licensing Server and access any server under that Terminal Licensing Server
umbrella?

Thanks again.

"Vera Noest [MVP]" wrote:

Per User TS CALs are currently not managed at all.
You only have to make sure that you buy as many Per User TS CALs as
you have connecting persons (*not* concurrent, and *not* user
accounts), and all will be fine.

Just to make sure that I understand you correctly: these 15 users
do remote administration, but the 10 servers are all full blown
Terminal Servers, is that correct?
Because in Remote Administration mode you don't need any TS CALs at
all, but you will have a maximum of 2 concurrent connections.

And if the 10 servers are indeed Terminal Servers, and these 15
users are administrators, how are your regular users licensed? If
regular users are licensed Per Device, then you must have a Per
Device license for your administrators as well, since a Terminal
Server can only use one type of licenses.
Only way around this is to setup a dedicated Terminal Server in Per
user licensing mode, to which your administrators connect, and from
there let them connect to the other Terminal Servers, which are in
Per Device licensing mode. RDP over RDP. Gives a small performance
hit, but nothing too bad.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?T3dlbiBEYXZpZXM=?= <Owen
Davies@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 23 aug 2006 in
microsoft.public.windows.terminal_services:

Hi,

I am setting up a network and am having trouble with the
Terminal Services Licensing. The network needs to be setup the
following way:

I have up to 15 remote users who need to do remote adminstration
on 10 or so machines. I have purchased 15 Per User licenses as
their machines will change quite often. Ideally I would like all
of them to be able to log in at the same time on the same
account. Is this possible?? If not do teh Per User CALS link
into the Active Directory somehow and authentication of the
users can happen that way?

Thanks for youe help.

.

Relevant Pages

  • Re: Per User Cals
    ... Per User TS CALs are currently not managed at all. ... Terminal Servers, is that correct? ... Device license for your administrators as well, ... Per Device licensing mode. ...
    (microsoft.public.windows.terminal_services)
  • Re: Per User Cals
    ... cannot have your 15 administrators connect with a Per user license. ... But if you only have these 15 remote Administrators and no other ... then per user licensing is fine. ... MCSE, CCEA, Microsoft MVP - Terminal Server ...
    (microsoft.public.windows.terminal_services)
  • RE: WinXP clients can not connect to W2K TS Server
    ... the message reported by remote desktop connection can be caused ... Which mode does the problematic terminal server run in, ... Which computer does the terminal services licensing server (the server ...
    (microsoft.public.windows.terminal_services)
  • Re: Terminal Services or Remote Desktop?
    ... First of all the two modes (Remote Administration and Terminal Services) are ... This will require a licensing server where TS CALs must be available. ...
    (microsoft.public.windows.terminal_services)
  • Remote Desktop for Administration v.s. Terminal Services
    ... 2003 isn't how you do remote administration (licensing grace period ... "no licensing servers" errors when trying to connect. ... the server with Remote Desktop for Administration enabled. ...
    (microsoft.public.windows.terminal_services)
Loading