Windows 2003 Terminal Services Licensing

  • Thread starter Thread starter MShawRMTD
  • Start date Start date
M

MShawRMTD

Guest
Hello,

I am an inhouse support technician for a Transit agency. We currently have
a Windows 2000 Terminal Server hosting our backoffice software to our remote
offices.

We are currently looking at getting two new servers. But I am unsure of
what licenses I would need to setup for these. I have been told that for
every TS CAL i will need a Local CAL. Is this correct?

Example:
20 Local Workstations = 20 Local CALS
25 Remote Workstations = 25 TS CALs + 25 Local Cals
for a total of 45 Local CALs and 35 TS CALs
 
Re: Windows 2003 Terminal Services Licensing

By "Local CAL" do you mean "Windows Server CAL"? Then yes, that's the case.
Every workstation that accesses the TS needs both a TS CAL and a Windows
Server CAL.

Rob

"MShawRMTD" <MShawRMTD@discussions.microsoft.com> wrote in message
news:ECFC648B-A931-4068-80FF-A8ECF5AC4651@microsoft.com...
> Hello,
>
> I am an inhouse support technician for a Transit agency. We currently
> have
> a Windows 2000 Terminal Server hosting our backoffice software to our
> remote
> offices.
>
> We are currently looking at getting two new servers. But I am unsure of
> what licenses I would need to setup for these. I have been told that for
> every TS CAL i will need a Local CAL. Is this correct?
>
> Example:
> 20 Local Workstations = 20 Local CALS
> 25 Remote Workstations = 25 TS CALs + 25 Local Cals
> for a total of 45 Local CALs and 35 TS CALs
 
Re: Windows 2003 Terminal Services Licensing

Yes, I mean Windows Server CAL. Thank you for that.

Now my question is if two servers both have Terminal Services installed in
Application Mode, and have 20 users connecting to both, will we need 20 TS
CALs for both servers or will 20 TS CALs installed on the licensing server
give the user access to each Terminal Server installation?

Matthew Shaw

"Rob Leitman [MS]" wrote:

> By "Local CAL" do you mean "Windows Server CAL"? Then yes, that's the case.
> Every workstation that accesses the TS needs both a TS CAL and a Windows
> Server CAL.
>
> Rob
>
> "MShawRMTD" <MShawRMTD@discussions.microsoft.com> wrote in message
> news:ECFC648B-A931-4068-80FF-A8ECF5AC4651@microsoft.com...
> > Hello,
> >
> > I am an inhouse support technician for a Transit agency. We currently
> > have
> > a Windows 2000 Terminal Server hosting our backoffice software to our
> > remote
> > offices.
> >
> > We are currently looking at getting two new servers. But I am unsure of
> > what licenses I would need to setup for these. I have been told that for
> > every TS CAL i will need a Local CAL. Is this correct?
> >
> > Example:
> > 20 Local Workstations = 20 Local CALS
> > 25 Remote Workstations = 25 TS CALs + 25 Local Cals
> > for a total of 45 Local CALs and 35 TS CALs

>
>
 
Re: Windows 2003 Terminal Services Licensing

One TS CAL is sufficient to connect to all of your Terminal
Servers.

There's something else that you have to decide, though: whether you
need Per User or Per Device TS CALs. In W2K, there exists only one
type of TS CAL, which is always Per Device. In 2003, you can
choose. The possibilities to change license type after you have
bought them are limited, so it's important to make the right
decision from the beginning.
Here's how to choose:

* if you have more users than clients (like in a classroom or
multiple shift situation, where several people connect to the TS
from shared workstations), then Per Device licensing is cheaper.

* if you have more clients than users (users connect from multiple
clients, i.e their office PC, a laptop and their home PC), then Per
User licensing is cheaper.

_________________________________________________________
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?TVNoYXdSTVRE?= <MShawRMTD@discussions.microsoft.com>
wrote on 20 nov 2007 in
microsoft.public.windows.terminal_services:

> Yes, I mean Windows Server CAL. Thank you for that.
>
> Now my question is if two servers both have Terminal Services
> installed in Application Mode, and have 20 users connecting to
> both, will we need 20 TS CALs for both servers or will 20 TS
> CALs installed on the licensing server give the user access to
> each Terminal Server installation?
>
> Matthew Shaw
>
> "Rob Leitman [MS]" wrote:
>
>> By "Local CAL" do you mean "Windows Server CAL"? Then yes,
>> that's the case. Every workstation that accesses the TS needs
>> both a TS CAL and a Windows Server CAL.
>>
>> Rob
>>
>> "MShawRMTD" <MShawRMTD@discussions.microsoft.com> wrote in
>> message
>> news:ECFC648B-A931-4068-80FF-A8ECF5AC4651@microsoft.com...
>> > Hello,
>> >
>> > I am an inhouse support technician for a Transit agency. We
>> > currently have
>> > a Windows 2000 Terminal Server hosting our backoffice
>> > software to our remote
>> > offices.
>> >
>> > We are currently looking at getting two new servers. But I
>> > am unsure of what licenses I would need to setup for these.
>> > I have been told that for every TS CAL i will need a Local
>> > CAL. Is this correct?
>> >
>> > Example:
>> > 20 Local Workstations = 20 Local CALS
>> > 25 Remote Workstations = 25 TS CALs + 25 Local Cals
>> > for a total of 45 Local CALs and 35 TS CALs
 
Re: Windows 2003 Terminal Services Licensing

Will we need a Windows Server CAL for both servers or just the one to pair
with the TS CAL for each Terminal Server User.

Let me see if I grasp this correctly.
If we have two servers, both running Terminal Services in Application Mode,
with 30 Remote Users at Maximum, and 20 Local Intranet Users. We would nee 30
TS CALs, and 100 Windows Server CALs.

or would we only need 70 Windows Server CALs?

Thanks again.
MShawRMTD

"Vera Noest [MVP]" wrote:

> One TS CAL is sufficient to connect to all of your Terminal
> Servers.
>
> There's something else that you have to decide, though: whether you
> need Per User or Per Device TS CALs. In W2K, there exists only one
> type of TS CAL, which is always Per Device. In 2003, you can
> choose. The possibilities to change license type after you have
> bought them are limited, so it's important to make the right
> decision from the beginning.
> Here's how to choose:
>
> * if you have more users than clients (like in a classroom or
> multiple shift situation, where several people connect to the TS
> from shared workstations), then Per Device licensing is cheaper.
>
> * if you have more clients than users (users connect from multiple
> clients, i.e their office PC, a laptop and their home PC), then Per
> User licensing is cheaper.
>
> _________________________________________________________
> 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?TVNoYXdSTVRE?= <MShawRMTD@discussions.microsoft.com>
> wrote on 20 nov 2007 in
> microsoft.public.windows.terminal_services:
>
> > Yes, I mean Windows Server CAL. Thank you for that.
> >
> > Now my question is if two servers both have Terminal Services
> > installed in Application Mode, and have 20 users connecting to
> > both, will we need 20 TS CALs for both servers or will 20 TS
> > CALs installed on the licensing server give the user access to
> > each Terminal Server installation?
> >
> > Matthew Shaw
> >
> > "Rob Leitman [MS]" wrote:
> >
> >> By "Local CAL" do you mean "Windows Server CAL"? Then yes,
> >> that's the case. Every workstation that accesses the TS needs
> >> both a TS CAL and a Windows Server CAL.
> >>
> >> Rob
> >>
> >> "MShawRMTD" <MShawRMTD@discussions.microsoft.com> wrote in
> >> message
> >> news:ECFC648B-A931-4068-80FF-A8ECF5AC4651@microsoft.com...
> >> > Hello,
> >> >
> >> > I am an inhouse support technician for a Transit agency. We
> >> > currently have
> >> > a Windows 2000 Terminal Server hosting our backoffice
> >> > software to our remote
> >> > offices.
> >> >
> >> > We are currently looking at getting two new servers. But I
> >> > am unsure of what licenses I would need to setup for these.
> >> > I have been told that for every TS CAL i will need a Local
> >> > CAL. Is this correct?
> >> >
> >> > Example:
> >> > 20 Local Workstations = 20 Local CALS
> >> > 25 Remote Workstations = 25 TS CALs + 25 Local Cals
> >> > for a total of 45 Local CALs and 35 TS CALs

>
 
Re: Windows 2003 Terminal Services Licensing

First of all: Terminal Services licensing (TS CALs) are *not* per
concurrent usage, it is per specific user or device. So if all of
your 30 remote users/devices and 20 local users/devices connect to
the TS, you would need 50 TS CALs, not 30. But maybe your 20 local
intranet users don't connect to the TS?

Windows Server CALs:

There are 2 different licensing modes for server CALs: "Per
Server" mode and "Per Device or Per User" mode (used to be called
"Per Seat" in W2K).
As long as you have only a single server, it doesn't matter much
which licensing mode your server is in. Since you have 2 servers
(and maybe more, don't you have a separate DC?), the licensing mode
becomes important.

"Per Device or Per User": you need one (1) server CAL for every
user or client; this gives them the right to connect to any number
of servers with a single server CAL.
This is most likely the licensing mode that you want on your
servers. It becomes cheaper, the more servers you have.

"Per Server": on *each* server, you need as many server CALs as the
the maximum number of *simultaneous* connections to the server.
This licensing mode is cheaper if you have a high number of clients
or users, but a low number of *concurrent* clients / users.

Details here:

Licensing Overview for Windows Server 2003
http://www.microsoft.com/windowsserver2003/howtobuy/licensing/overv
iew.mspx

_________________________________________________________
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?TVNoYXdSTVRE?= <MShawRMTD@discussions.microsoft.com>
wrote on 21 nov 2007 in
microsoft.public.windows.terminal_services:

> Will we need a Windows Server CAL for both servers or just the
> one to pair with the TS CAL for each Terminal Server User.
>
> Let me see if I grasp this correctly.
> If we have two servers, both running Terminal Services in
> Application Mode, with 30 Remote Users at Maximum, and 20 Local
> Intranet Users. We would nee 30 TS CALs, and 100 Windows Server
> CALs.
>
> or would we only need 70 Windows Server CALs?
>
> Thanks again.
> MShawRMTD
>
> "Vera Noest [MVP]" wrote:
>
>> One TS CAL is sufficient to connect to all of your Terminal
>> Servers.
>>
>> There's something else that you have to decide, though: whether
>> you need Per User or Per Device TS CALs. In W2K, there exists
>> only one type of TS CAL, which is always Per Device. In 2003,
>> you can choose. The possibilities to change license type after
>> you have bought them are limited, so it's important to make the
>> right decision from the beginning.
>> Here's how to choose:
>>
>> * if you have more users than clients (like in a classroom or
>> multiple shift situation, where several people connect to the
>> TS from shared workstations), then Per Device licensing is
>> cheaper.
>>
>> * if you have more clients than users (users connect from
>> multiple clients, i.e their office PC, a laptop and their home
>> PC), then Per User licensing is cheaper.
>>
>> _________________________________________________________
>> 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?TVNoYXdSTVRE?= <MShawRMTD@discussions.microsoft.com>
>> wrote on 20 nov 2007 in
>> microsoft.public.windows.terminal_services:
>>
>> > Yes, I mean Windows Server CAL. Thank you for that.
>> >
>> > Now my question is if two servers both have Terminal Services
>> > installed in Application Mode, and have 20 users connecting
>> > to both, will we need 20 TS CALs for both servers or will 20
>> > TS CALs installed on the licensing server give the user
>> > access to each Terminal Server installation?
>> >
>> > Matthew Shaw
>> >
>> > "Rob Leitman [MS]" wrote:
>> >
>> >> By "Local CAL" do you mean "Windows Server CAL"? Then yes,
>> >> that's the case. Every workstation that accesses the TS
>> >> needs both a TS CAL and a Windows Server CAL.
>> >>
>> >> Rob
>> >>
>> >> "MShawRMTD" <MShawRMTD@discussions.microsoft.com> wrote in
>> >> message
>> >> news:ECFC648B-A931-4068-80FF-A8ECF5AC4651@microsoft.com...
>> >> > Hello,
>> >> >
>> >> > I am an inhouse support technician for a Transit agency.
>> >> > We currently have
>> >> > a Windows 2000 Terminal Server hosting our backoffice
>> >> > software to our remote
>> >> > offices.
>> >> >
>> >> > We are currently looking at getting two new servers. But
>> >> > I am unsure of what licenses I would need to setup for
>> >> > these. I have been told that for every TS CAL i will need
>> >> > a Local CAL. Is this correct?
>> >> >
>> >> > Example:
>> >> > 20 Local Workstations = 20 Local CALS
>> >> > 25 Remote Workstations = 25 TS CALs + 25 Local Cals
>> >> > for a total of 45 Local CALs and 35 TS CALs
 
Back
Top