Server 2003 Terminal services licensing clarification request.

[Guest xanthium1@googlemail.com]

Hi,

 

I'm in the process of setting up a Server 2003 R2 SP2 system that I

want to use as to provide Terminal Services (Remote Desktop) sessions

to for a small number (3 currently) remote workers.

 

From the packaging it appears that I've got a BIOS locked copy od

Server 2003 with 5 CALs?

 

But Terminal services doesn't seem to know anything about them. I can

activate the server but get asked for a code I don't appear to have

when trying to add the client licenses?

 

I've got a piece of paper in with the Server 2003 disks and manuals

that shows **5** Client access licenses.

 

Are these TS Client licenses? and if not can someone explain what they

are and how I use them?

 

Do I need to buy some TS client access licenses?

 

Thanks for you help,

 

Mark

[Guest TP]

Re: Server 2003 Terminal services licensing clarification request.

 

The licenses that are included with the OEM copy of

windows are Windows Server 2003 CALs. TS CALs

are *not* included; they must be purchased separately.

 

For each user/device you need both a Windows CAL

and a TS CAL.

 

Licensing Terminal Server in Windows Server 2003 R2

 

http://www.microsoft.com/windowsserver2003/howtobuy/licensing/ts2003.mspx

 

-TP

 

xanthium1@googlemail.com wrote:

> Hi,

>

> I'm in the process of setting up a Server 2003 R2 SP2 system that I

> want to use as to provide Terminal Services (Remote Desktop) sessions

> to for a small number (3 currently) remote workers.

>

> From the packaging it appears that I've got a BIOS locked copy od

> Server 2003 with 5 CALs?

>

> But Terminal services doesn't seem to know anything about them. I can

> activate the server but get asked for a code I don't appear to have

> when trying to add the client licenses?

>

> I've got a piece of paper in with the Server 2003 disks and manuals

> that shows **5** Client access licenses.

>

> Are these TS Client licenses? and if not can someone explain what they

> are and how I use them?

>

> Do I need to buy some TS client access licenses?

>

> Thanks for you help,

>

> Mark

[Guest xanthium1@googlemail.com]

Re: Server 2003 Terminal services licensing clarification request.

 

Thanks for the clarification.

 

Though as I'm from for of a Unix background, can you explain what the

purpose of needing the Windows Server 2003 CALs is, it seems to me

that you end up paying twice to allow someone remote access to the

system using TS.

 

On 11 Dec, 18:12, "TP" <tperson.knowsp...@mailandnews.com> wrote:

> The licenses that are included with the OEM copy of

> windows are Windows Server 2003 CALs. TS CALs

> are *not* included; they must be purchased separately.

>

> For each user/device you need both a Windows CAL

> and a TS CAL.

>

> Licensing Terminal Server in Windows Server 2003 R2

>

> http://www.microsoft.com/windowsserver2003/howtobuy/licensing/ts2003....

>

> -TP

>

> xanthi...@googlemail.com wrote:

> > Hi,

>

> > I'm in the process of setting up a Server 2003 R2 SP2 system that I

> > want to use as to provide Terminal Services (Remote Desktop) sessions

> > to for a small number (3 currently) remote workers.

>

> > From the packaging it appears that I've got a BIOS locked copy od

> > Server 2003 with 5 CALs?

>

> > But Terminal services doesn't seem to know anything about them. I can

> > activate the server but get asked for a code I don't appear to have

> > when trying to add the client licenses?

>

> > I've got a piece of paper in with the Server 2003 disks and manuals

> > that shows **5** Client access licenses.

>

> > Are these TS Client licenses? and if not can someone explain what they

> > are and how I use them?

>

> > Do I need to buy some TS client access licenses?

>

> > Thanks for you help,

>

> > Mark

[Guest Vera Noest [MVP]]

Re: Server 2003 Terminal services licensing clarification request.

 

Server CALs are needed as soon as you contact *any* server in the

network for authentication, receiving an IP number from a DHCP

server, access to shared files and printers, and so on.

 

To access a Terminal Server, you also need a TS CAL.

 

From the Windows Server 2003 Pricing and Licensing FAQ

http://www.microsoft.com/windowsserver2003/howtobuy/licensing/pricl

icfaq.mspx

 

Q. What is the difference between a Windows CAL and a Terminal

Server (TS) CAL?

 

A. A Windows CAL is required when a user or device is directly or

indirectly accessing a Windows server. Additionally, if the user or

device is accessing or using the terminal server functionality of

Windows Server Standard and Enterprise Editions, a TS CAL is also

required.

 

 

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

"xanthium1@googlemail.com" <m.seabourne@ncrl.co.uk> wrote on 13

dec 2007 in microsoft.public.windows.terminal_services:

> Thanks for the clarification.

>

> Though as I'm from for of a Unix background, can you explain

> what the purpose of needing the Windows Server 2003 CALs is, it

> seems to me that you end up paying twice to allow someone remote

> access to the system using TS.

>

> On 11 Dec, 18:12, "TP" <tperson.knowsp...@mailandnews.com>

> wrote:

>> The licenses that are included with the OEM copy of

>> windows are Windows Server 2003 CALs. TS CALs

>> are *not* included; they must be purchased separately.

>>

>> For each user/device you need both a Windows CAL

>> and a TS CAL.

>>

>> Licensing Terminal Server in Windows Server 2003 R2

>>

>> http://www.microsoft.com/windowsserver2003/howtobuy/licensing/ts

>> 2003....

>>

>> -TP

>>

>> xanthi...@googlemail.com wrote:

>> > Hi,

>>

>> > I'm in the process of setting up a Server 2003 R2 SP2 system

>> > that I want to use as to provide Terminal Services (Remote

>> > Desktop) sessions to for a small number (3 currently) remote

>> > workers.

>>

>> > From the packaging it appears that I've got a BIOS locked

>> > copy od Server 2003 with 5 CALs?

>>

>> > But Terminal services doesn't seem to know anything about

>> > them. I can activate the server but get asked for a code I

>> > don't appear to have when trying to add the client licenses?

>>

>> > I've got a piece of paper in with the Server 2003 disks and

>> > manuals that shows **5** Client access licenses.

>>

>> > Are these TS Client licenses? and if not can someone explain

>> > what they are and how I use them?

>>

>> > Do I need to buy some TS client access licenses?

>>

>> > Thanks for you help,

>>

>> > Mark