TS Licensing Question

[compsosinc@gmail.com]

We currently have the following setup:

-Windows 2003 Server Std Edition as a DC
- (15) XP Clients on the Domain

We are opening another location that will have just XP Clients, and we
are adding this to the domain above:

- Windows 2003 Server Std Edition as a Application Server running
Terminal Services and acting as the Licensing Server
- Adding (10) XP Clients with multiple users at the remote location
that will be members of & login to the DC. They will also log into the
TS for the purpose of running our accounting application.

Questions:

We know we need to purchase (10) TS CALs-PER DEVICE for these remotes.
However, we are confused on what additional Windows 2003 CALs we need
to purchase, either on the DC and/or on the TS Server:

1. To support the (10) XP remote clients on the domain, do we purchase
(10) additional Windows CALs for the DC? And/Or:

2. In addition to #1, do we also purchase (10) Windows CALs with our
new member server?

If so, that would mean we have this:

- On the DC: (25) total CALs
- On the TS: (10) TS CALs and (10) Windows CALs.

This excerpt from http://www.microsoft.com/windowsserver2003/howtobuy/licensing/ts2003.mspx
is what confused us:

"Terminal Server Licensing Requirements
Windows Server License
The Windows Server 2003 R2 licensing model requires a server license
for each copy of the server software installed. Terminal Services
functionality is included in the Windows Server license.

Windows Server Client Access License
In addition to a server license, a Windows Server Client Access
License (CAL) is required. If you wish to conduct a Windows session,
an incremental Terminal Server Client Access License (TS CAL) is
required as well. A Windows session is defined as a session during
which the server software hosts a graphical user interface on a
device. For Windows sessions, a TS CAL is required for each user or
device."

Thanks!

 

[Vera Noest [MVP]]

Re: TS Licensing Question

Regarding Windows OS licensing:

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 had only a single server, it didn't matter much
which licensing mode your server was in. Now that you are adding a
second server, the licensing mode becomes important.
Assuming that the maximum number of clients connected
simultaneously are 12 (out of 15) at the main site, and 8 (out of
10) at the remote site, this is what you would need under the 2
licensing modes:

"Per Server": on each server, you need as many server CALs as the
the maximum number of simultaneous connections to the server.
On your DC: 12 server CALs for the main site clients + 8 server
CALs for the remote site clients (they authenticate to the DC).
On your TS: 8 server CALs for the remote clients.
Total server CALs: 12 + 8 + 8 = 28
If all clients connect simultaneously, this could increase to 35.

"Per Device or Per User": you need one (1) server CAL for very user
or client; this gives them the right to connect to any number of
servers with a single server CAL.
Total server CALs: 15 main site clients + 10 remote site clients =
25.
This is most likely the licensing mode that you want on both
servers. If you are currently running in the "Per Server" licensing
mode on your DC, you can change it in Control Panel - Licensing.

Regarding the TS CALs:
You always need a TS CAL for every user or device which connects,
there is no option to license per concurrent connection.
But: TS CALs are per user or per device and they give that user or
device the right to connect to any number of Terminal Servers.
So you need 10 TS CALs.
Note that you have to choose between Per User or Per Device TS
CALs. Choose Per User if you have more clients than users, i.e.
your users connect from their office PC and a laptop and their home
PC. Choose Per Device if you have more users than clients, i.e.
users work in shifts and share a workststation.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

compsosinc@gmail.com wrote on 17 okt 2007 in
microsoft.public.windows.terminal_services:

> We currently have the following setup:
>
> -Windows 2003 Server Std Edition as a DC
> - (15) XP Clients on the Domain
>
> We are opening another location that will have just XP Clients,
> and we are adding this to the domain above:
>
> - Windows 2003 Server Std Edition as a Application Server
> running Terminal Services and acting as the Licensing Server
> - Adding (10) XP Clients with multiple users at the remote
> location that will be members of & login to the DC. They will
> also log into the TS for the purpose of running our accounting
> application.
>
> Questions:
>
> We know we need to purchase (10) TS CALs-PER DEVICE for these
> remotes. However, we are confused on what additional Windows
> 2003 CALs we need to purchase, either on the DC and/or on the TS
> Server:
>
> 1. To support the (10) XP remote clients on the domain, do we
> purchase (10) additional Windows CALs for the DC? And/Or:
>
> 2. In addition to #1, do we also purchase (10) Windows CALs with
> our new member server?
>
> If so, that would mean we have this:
>
> - On the DC: (25) total CALs
> - On the TS: (10) TS CALs and (10) Windows CALs.
>
> This excerpt from
> http://www.microsoft.com/windowsserver2003/howtobuy/licensing/ts2
> 003.mspx is what confused us:
>
> "Terminal Server Licensing Requirements
> Windows Server License
> The Windows Server 2003 R2 licensing model requires a server
> license for each copy of the server software installed. Terminal
> Services functionality is included in the Windows Server
> license.
>
> Windows Server Client Access License
> In addition to a server license, a Windows Server Client Access
> License (CAL) is required. If you wish to conduct a Windows
> session, an incremental Terminal Server Client Access License
> (TS CAL) is required as well. A Windows session is defined as a
> session during which the server software hosts a graphical user
> interface on a device. For Windows sessions, a TS CAL is
> required for each user or device."
>
> Thanks!

 

[compsosinc@gmail.com]

Re: TS Licensing Question

On Oct 17, 4:07 pm, "Vera Noest [MVP]" <vera.no...@remove-
this.hem.utfors.se> wrote:
> Regarding Windows OS licensing:
>
> 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 had only a single server, it didn't matter much
> which licensing mode your server was in. Now that you are adding a
> second server, the licensing mode becomes important.
> Assuming that the maximum number of clients connected
> simultaneously are 12 (out of 15) at the main site, and 8 (out of
> 10) at the remote site, this is what you would need under the 2
> licensing modes:
>
> "Per Server": on each server, you need as many server CALs as the
> the maximum number of simultaneous connections to the server.
> On your DC: 12 server CALs for the main site clients + 8 server
> CALs for the remote site clients (they authenticate to the DC).
> On your TS: 8 server CALs for the remote clients.
> Total server CALs: 12 + 8 + 8 = 28
> If all clients connect simultaneously, this could increase to 35.
>
> "Per Device or Per User": you need one (1) server CAL for very user
> or client; this gives them the right to connect to any number of
> servers with a single server CAL.
> Total server CALs: 15 main site clients + 10 remote site clients =
> 25.
> This is most likely the licensing mode that you want on both
> servers. If you are currently running in the "Per Server" licensing
> mode on your DC, you can change it in Control Panel - Licensing.
>
> Regarding the TS CALs:
> You always need a TS CAL for every user or device which connects,
> there is no option to license per concurrent connection.
> But: TS CALs are per user or per device and they give that user or
> device the right to connect to any number of Terminal Servers.
> So you need 10 TS CALs.
> Note that you have to choose between Per User or Per Device TS
> CALs. Choose Per User if you have more clients than users, i.e.
> your users connect from their office PC and a laptop and their home
> PC. Choose Per Device if you have more users than clients, i.e.
> users work in shifts and share a workststation.
>
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> compsos...@gmail.com wrote on 17 okt 2007 in
> microsoft.public.windows.terminal_services:
>
>
>
> > We currently have the following setup:
>
> > -Windows 2003 Server Std Edition as a DC
> > - (15) XP Clients on the Domain
>
> > We are opening another location that will have just XP Clients,
> > and we are adding this to the domain above:
>
> > - Windows 2003 Server Std Edition as a Application Server
> > running Terminal Services and acting as the Licensing Server
> > - Adding (10) XP Clients with multiple users at the remote
> > location that will be members of & login to the DC. They will
> > also log into the TS for the purpose of running our accounting
> > application.
>
> > Questions:
>
> > We know we need to purchase (10) TS CALs-PER DEVICE for these
> > remotes. However, we are confused on what additional Windows
> > 2003 CALs we need to purchase, either on the DC and/or on the TS
> > Server:
>
> > 1. To support the (10) XP remote clients on the domain, do we
> > purchase (10) additional Windows CALs for the DC? And/Or:
>
> > 2. In addition to #1, do we also purchase (10) Windows CALs with
> > our new member server?
>
> > If so, that would mean we have this:
>
> > - On the DC: (25) total CALs
> > - On the TS: (10) TS CALs and (10) Windows CALs.
>
> > This excerpt from
> >http://www.microsoft.com/windowsserver2003/howtobuy/licensing/ts2
> > 003.mspx is what confused us:
>
> > "Terminal Server Licensing Requirements
> > Windows Server License
> > The Windows Server 2003 R2 licensing model requires a server
> > license for each copy of the server software installed. Terminal
> > Services functionality is included in the Windows Server
> > license.
>
> > Windows Server Client Access License
> > In addition to a server license, a Windows Server Client Access
> > License (CAL) is required. If you wish to conduct a Windows
> > session, an incremental Terminal Server Client Access License
> > (TS CAL) is required as well. A Windows session is defined as a
> > session during which the server software hosts a graphical user
> > interface on a device. For Windows sessions, a TS CAL is
> > required for each user or device."
>
> > Thanks!- Hide quoted text -
>
> - Show quoted text -

That helped claify things. We were reading too much into it.Thank you
very much!