TS Requirements

  • Thread starter Thread starter siskokid480
  • Start date Start date
S

siskokid480

Guest
We are looking at doing a pilot/test Terminal Server environment with thin
clients. I am trying to put together a list of all the basic items that we
will need to perform this test.

I basically am planning on having 25 thin clients connect to a Terminal
Server. What components would I need and what licenses will I need to
purchase.

Thanks!
 
Re: TS Requirements

I'm not sure what you mean with components, other than the obvious
(server + clients + network).

Licensing requirements:

* Server OS license - comes usually with the OS
* one server CAL for every connecting user or client
* one TS CAL for every connecting user or client
* optional: licensing for the applications which you deploy through
TS
_________________________________________________________
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?c2lza29raWQ0ODA=?=
<siskokid480@discussions.microsoft.com> wrote on 16 okt 2007 in
microsoft.public.windows.terminal_services:

> We are looking at doing a pilot/test Terminal Server environment
> with thin clients. I am trying to put together a list of all the
> basic items that we will need to perform this test.
>
> I basically am planning on having 25 thin clients connect to a
> Terminal Server. What components would I need and what licenses
> will I need to purchase.
>
> Thanks!
 
Re: TS Requirements

Vera Noest [MVP] wrote:
> I'm not sure what you mean with components, other than the obvious
> (server + clients + network).
>
> Licensing requirements:
>
> * Server OS license - comes usually with the OS
> * one server CAL for every connecting user or client
> * one TS CAL for every connecting user or client
> * optional: licensing for the applications which you deploy through
> TS
> _________________________________________________________
> 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?c2lza29raWQ0ODA=?=
> <siskokid480@discussions.microsoft.com> wrote on 16 okt 2007 in
> microsoft.public.windows.terminal_services:
>
>> We are looking at doing a pilot/test Terminal Server environment
>> with thin clients. I am trying to put together a list of all the
>> basic items that we will need to perform this test.
>>
>> I basically am planning on having 25 thin clients connect to a
>> Terminal Server. What components would I need and what licenses
>> will I need to purchase.
>>
>> Thanks!
Note that you can run a pilot like this, with no TSCALs for up to 210
days as you have 120 days to get a licensing server up and running and
then 90 days grace period for the TSCALs.
So if this is a test and you are ok on testing for 210 days, I would not
buy any TS related license (as your test may not be as good as expected
and you may decide to drop TS).

--
Cláudio Rodrigues
CEO, TSFactory Inc.

Microsoft MVP
Windows Server - Terminal Services
http://www.tsfactory.com
 
Re: TS Requirements

Would a TS Licensing Server be required and is that a seperate license.

Thanks!

""Cláudio Rodrigues [MVP]"" wrote:

> Vera Noest [MVP] wrote:
> > I'm not sure what you mean with components, other than the obvious
> > (server + clients + network).
> >
> > Licensing requirements:
> >
> > * Server OS license - comes usually with the OS
> > * one server CAL for every connecting user or client
> > * one TS CAL for every connecting user or client
> > * optional: licensing for the applications which you deploy through
> > TS
> > _________________________________________________________
> > 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?c2lza29raWQ0ODA=?=
> > <siskokid480@discussions.microsoft.com> wrote on 16 okt 2007 in
> > microsoft.public.windows.terminal_services:
> >
> >> We are looking at doing a pilot/test Terminal Server environment
> >> with thin clients. I am trying to put together a list of all the
> >> basic items that we will need to perform this test.
> >>
> >> I basically am planning on having 25 thin clients connect to a
> >> Terminal Server. What components would I need and what licenses
> >> will I need to purchase.
> >>
> >> Thanks!
> Note that you can run a pilot like this, with no TSCALs for up to 210
> days as you have 120 days to get a licensing server up and running and
> then 90 days grace period for the TSCALs.
> So if this is a test and you are ok on testing for 210 days, I would not
> buy any TS related license (as your test may not be as good as expected
> and you may decide to drop TS).
>
> --
> Cláudio Rodrigues
> CEO, TSFactory Inc.
>
> Microsoft MVP
> Windows Server - Terminal Services
> http://www.tsfactory.com
>
 
Re: TS Requirements

As Cláudio pointed out, you can test during a grace period of 120
days without a TS Licensing Server at all. After that, you must
install a TS Licensing server, which will issue temporary licenses
to your clients. They will last you another 90 days.
After that, you need to buy and install TS CALs on the TS Licensing
Server.
The TS Licensing Server itself is just a Windows component which
you can install on any 2003 server in the domain. It doesn't need a
separate license to run a TS Licensing server.

Windows Server 2003 Pricing and Licensing FAQ
http://www.microsoft.com/windowsserver2003/howtobuy/licensing/pricl
icfaq.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?c2lza29raWQ0ODA=?=
<siskokid480@discussions.microsoft.com> wrote on 17 okt 2007 in
microsoft.public.windows.terminal_services:

> Would a TS Licensing Server be required and is that a seperate
> license.
>
> Thanks!
>
> ""Cláudio Rodrigues [MVP]"" wrote:
>
>> Vera Noest [MVP] wrote:
>> > I'm not sure what you mean with components, other than the
>> > obvious (server + clients + network).
>> >
>> > Licensing requirements:
>> >
>> > * Server OS license - comes usually with the OS
>> > * one server CAL for every connecting user or client
>> > * one TS CAL for every connecting user or client
>> > * optional: licensing for the applications which you deploy
>> > through TS
>> > _________________________________________________________
>> > 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?c2lza29raWQ0ODA=?=
>> > <siskokid480@discussions.microsoft.com> wrote on 16 okt 2007
>> > in microsoft.public.windows.terminal_services:
>> >
>> >> We are looking at doing a pilot/test Terminal Server
>> >> environment with thin clients. I am trying to put together a
>> >> list of all the basic items that we will need to perform
>> >> this test.
>> >>
>> >> I basically am planning on having 25 thin clients connect to
>> >> a Terminal Server. What components would I need and what
>> >> licenses will I need to purchase.
>> >>
>> >> Thanks!
>> Note that you can run a pilot like this, with no TSCALs for up
>> to 210 days as you have 120 days to get a licensing server up
>> and running and then 90 days grace period for the TSCALs.
>> So if this is a test and you are ok on testing for 210 days, I
>> would not buy any TS related license (as your test may not be
>> as good as expected and you may decide to drop TS).
>>
>> --
>> Cláudio Rodrigues
>> CEO, TSFactory Inc.
>>
>> Microsoft MVP
>> Windows Server - Terminal Services
>> http://www.tsfactory.com
 
Re: TS Requirements

Note that this is likely a violation of the EULA.

The fact that the server has a grace period within which
no TS licensing server is required and a temporary TS
CAL is valid for 90 days is an *implementation* detail.

The EULA makes no mention that purchased licenses
are not required for the first xxx days.

-TP

"Cláudio Rodrigues [MVP]" wrote:
> Note that you can run a pilot like this, with no TSCALs for up to 210
> days as you have 120 days to get a licensing server up and running and
> then 90 days grace period for the TSCALs.
> So if this is a test and you are ok on testing for 210 days, I would
> not buy any TS related license (as your test may not be as good as
> expected and you may decide to drop TS).
 
Re: TS Requirements

That works... thanks for everyone's help and input. Much appreciated.

"Vera Noest [MVP]" wrote:

> As Cláudio pointed out, you can test during a grace period of 120
> days without a TS Licensing Server at all. After that, you must
> install a TS Licensing server, which will issue temporary licenses
> to your clients. They will last you another 90 days.
> After that, you need to buy and install TS CALs on the TS Licensing
> Server.
> The TS Licensing Server itself is just a Windows component which
> you can install on any 2003 server in the domain. It doesn't need a
> separate license to run a TS Licensing server.
>
> Windows Server 2003 Pricing and Licensing FAQ
> http://www.microsoft.com/windowsserver2003/howtobuy/licensing/pricl
> icfaq.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?c2lza29raWQ0ODA=?=
> <siskokid480@discussions.microsoft.com> wrote on 17 okt 2007 in
> microsoft.public.windows.terminal_services:
>
> > Would a TS Licensing Server be required and is that a seperate
> > license.
> >
> > Thanks!
> >
> > ""Cláudio Rodrigues [MVP]"" wrote:
> >
> >> Vera Noest [MVP] wrote:
> >> > I'm not sure what you mean with components, other than the
> >> > obvious (server + clients + network).
> >> >
> >> > Licensing requirements:
> >> >
> >> > * Server OS license - comes usually with the OS
> >> > * one server CAL for every connecting user or client
> >> > * one TS CAL for every connecting user or client
> >> > * optional: licensing for the applications which you deploy
> >> > through TS
> >> > _________________________________________________________
> >> > 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?c2lza29raWQ0ODA=?=
> >> > <siskokid480@discussions.microsoft.com> wrote on 16 okt 2007
> >> > in microsoft.public.windows.terminal_services:
> >> >
> >> >> We are looking at doing a pilot/test Terminal Server
> >> >> environment with thin clients. I am trying to put together a
> >> >> list of all the basic items that we will need to perform
> >> >> this test.
> >> >>
> >> >> I basically am planning on having 25 thin clients connect to
> >> >> a Terminal Server. What components would I need and what
> >> >> licenses will I need to purchase.
> >> >>
> >> >> Thanks!
> >> Note that you can run a pilot like this, with no TSCALs for up
> >> to 210 days as you have 120 days to get a licensing server up
> >> and running and then 90 days grace period for the TSCALs.
> >> So if this is a test and you are ok on testing for 210 days, I
> >> would not buy any TS related license (as your test may not be
> >> as good as expected and you may decide to drop TS).
> >>
> >> --
> >> Cláudio Rodrigues
> >> CEO, TSFactory Inc.
> >>
> >> Microsoft MVP
> >> Windows Server - Terminal Services
> >> http://www.tsfactory.com
>
 
Back
Top