Re: Per User Cals
- From: "Vera Noest [MVP]" <vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 04 Sep 2006 14:28:47 -0700
Sorry for replying so late, been away for a week.
You have to switch you Terminal Servers to use the Per user
licensing mode (in TS Configuration - Server - licensing).
Since Per User licenses are currently unmanaged, no license will be
issued at all, and the Issued count in the Licensing manager will
show "N/A" (not applicable).
_________________________________________________________
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=?=
<OwenDavies@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 28 aug 2006 in
microsoft.public.windows.terminal_services:
Hi,.
Believe me this is a very strange setup and what I have told you
is not the half of it. There are only the admins working on
them. Good to hear that the per user licenses will do fine.
Just another quick question. I downloaded one of the test aps
from the Resource Kit (tsctst.exe) and have run it on all the
admin's systems. They are currently all showing temporary der
device cals. I have since installed the Per User CALs. When
can I expect to see the licences change over to the permant
ones?
Thanks again, you have been a great help.
"Vera Noest [MVP]" wrote:
Yes, if you have installed terminal Services, then it's a full-
blown TS, and if you need more than 2 concurrent connections,
that's also what you want.
There's no general problem at all with using Per User licenses,
I just wanted to point out that you cannot use 2 different
types of licenses on a single Terminal Server.
So if you have 200 regular users connecting to these 10
terminal Servers, and these 200 users are licensed Per Device,
then you cannot have your 15 administrators connect with a Per
user license.
But if you only have these 15 remote Administrators and no
other users at all, then per user licensing is fine.
I'm probably just seeing problems which don't exist, because I
cannot really imagine a situation where you would need more
than 2 concurrent Administration connections.
_________________________________________________________
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=?=
<OwenDavies@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 24 aug 2006 in
microsoft.public.windows.terminal_services:
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.
- Prev by Date: One workgroup, two 2003 Servers sharing licenses?
- Next by Date: Re: One workgroup, two 2003 Servers sharing licenses?
- Previous by thread: One workgroup, two 2003 Servers sharing licenses?
- Next by thread: Re: Trouble with user software installation on TS
- Index(es):
Relevant Pages
|
