Re: Windows CAL Licensing Mode and Terminal Server

Vera, Thanks for the definitive response. I have in fact changed the Windows
CAL mode to per device or user, in line with our purchasing history.

Thanks

"Vera Noest [MVP]" wrote:

When in doubts about licensing, the best you can do is to contact
your local Microsoft representative. They will be able to give you
an authorative answer.
That said, there's no need to worry or change your server's
licensing mode.

The licensing mode for the server OS (Windows CALs) is completely
independent of the licensing mode of the Terminal Server.

For Windows CALs, you can choose between 2 licensing modes:
a) Per Server licensing
b) Per User/Per Device licensing

Both licensing modes can be used with either Per User CALs or Per
Device CALs.

See:
Windows Server 2003 R2 Client Access Licensing Overview
http://www.microsoft.com/windowsserver2003/howtobuy/licensing/calov
erview.mspx

For Terminal Services, you can choose between 2 licensing modes:
a) Per Device licensing mode - with Per Device TS CALs
b) Per User licensing mode - with Per User TS CALs

See:
Windows Server 2003 Pricing and Licensing FAQ
http://www.microsoft.com/windowsserver2003/howtobuy/licensing/pricl
icfaq.mspx

So the EULA wants to point out that there is no "Per Server"
licensing mode for Terminal Services. That's all!

Just go ahead and license your server OS for the TS and the TS
Licensing Server in Per Server mode for the Server CALs, and
whatever licensing mode you think is best for TS CALs.

_________________________________________________________
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?UGF0aCBwcm9ibGVtIHVzaW5nIHRlbXBsYXRlcy9JbmNsdWRlcw==?=
<PathproblemusingtemplatesIncludes@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote on 22 apr 2007 in
microsoft.public.windows.terminal_services:

I am not the only person who has spent a lot of time trying to
understand how to set up my servers for Terminal
Services.......and am still confused.

Can someone please help me...

Firstly, I have read Newsgroup responses and cannot find a
definitive piece of information that clarifies this.

For me the problem stems from the statement in the 2003 Server
EULA para e. item (ii). this states that 'Windows sessions are
not allowed in Per Server mode', for Types of TS CALs.

If Per Server mode is only for Windows CALs , then why is it
mentioned in the TS Cals section of the EULA?

I have not read anywhere that therefore if you are going to
install a Terminal Server 2003 you must set the Licensing mode
during installation of 2003 server to Per Device or Per User
Mode to allow sessions.

The responses on newsgroups indicate that you can run Per Server
mode for Windows CALS when using Terminal Services
???????????????? Not according to the EULA?? Where is the
problem???

The TSCAL options are per Device or per User. There is no Per
Server.

Maybe this is where the confusion is........................

Also, I want to install a separate License Server 2003.

So, as I have a standard windows domain with other 2000/2003
servers how do I configure the Windows CALs for the TS and the
LS ?

Currently they are both set to Per Server. I know that I can
change this to per Device or per User , but it's a once only
change, so I want to be sure!

We are purchasing the TS CALS as needed.

I am stuck with this so please help me.

.

Relevant Pages

  • Re: Pricing Confusion.
    ... You need CALs for authenticated access. ... Note the following general exception to Windows CAL requirementsWindows ... CALs are not required when access to the server software is ... So, in your case, with the "plain text authentication" (I assume you mean ...
    (microsoft.public.inetserver.iis)
  • Re: ASP.NET great technology but unaffordable?
    ... for older sqlserver's there is a connection license, for 2005 you pick the no cals server process license. ... server you'll need an unlimited amount of Windows CALs or the external ... External Connector licence. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Cal Question
    ... >>> Client Access Licensing for Windows Small Business Server 2003 ... >>> Small Business Server 2003. ... As with previous Windows Server licensing ... you also receive five CALS. ...
    (microsoft.public.windows.server.sbs)
  • Re: CAL question
    ... Client Access Licensing for Windows Small Business Server 2003 ... cost-effective options for licensing Windows ... when you purchase additional CALs for Windows Small Business Server. ...
    (microsoft.public.windows.server.sbs)
  • Re: Problem with Licensing and A Flaw in TS Client
    ... > server has been issuing them to people. ... Either you have "Per Device" TS CALs, which are issued to devices, ... 822134 - The Function of Terminal Server CALs in Windows Server ... Maybe the licensing mode of the TS? ...
    (microsoft.public.windows.terminal_services)
Quantcast