Jump to content

Terminal server and W2K3 Server licenses


Recommended Posts

Guest GotNoIdea
Posted

OK I need to get this straight as I have heard all kinds of explainations

and comments. I'm looking into setting up a W2K3 Standard server for a

potential that will

also be used as a Citrix server. The amount of clients and user accounts is

undetermined at the moment. I know for example if I'm going to have say 50

users accessing this server that I will need 50 W2K3 user cal's as this

server will also be a DC. Now my

question is do I also need terminal server licenses? My coworker seems to

disagree that we need them. He claims that since XP comes with the TS client

(RDC) that it is no longer required.

We have our own W2K3/Citrix server that is a terminal server. It is not

a DC but it is part of our domain. When we first set it up to be a TS we did

get the deafult prompt that

it will remain operable for 90 days in which you will need to activate it

and

configure the licensing. Well I believe when we activated it we sort of got

around that and used "per device" option which allowed us unlimited access.

When I go to the TS License Manager and view our licensing it states:

 

Product = "Existing Windows 2000 Server - Terminal Services CAL Token (per

device)"

Type = Built-in

Total = Unlimited

Available = Unlimited

Issued = 0

 

I need some experts to shed some light on this. Is this correct and do I

need to purchase TS licenses also. thanks.

  • Replies 4
  • Created
  • Last Reply

Popular Days

Guest Rob Leitman [MS]
Posted

Re: Terminal server and W2K3 Server licenses

 

Yes, you need a TS CAL for each connection.

 

See the licensing section at

http://www.microsoft.com/technet/community/en-us/terminal/terminal_faq.mspx

 

Rob

 

"GotNoIdea" <GotNoIdea@GotNoEmail.com> wrote in message

news:O%23wZFnf1HHA.4584@TK2MSFTNGP03.phx.gbl...

> OK I need to get this straight as I have heard all kinds of explainations

> and comments. I'm looking into setting up a W2K3 Standard server for a

> potential that will

> also be used as a Citrix server. The amount of clients and user accounts

> is

> undetermined at the moment. I know for example if I'm going to have say 50

> users accessing this server that I will need 50 W2K3 user cal's as this

> server will also be a DC. Now my

> question is do I also need terminal server licenses? My coworker seems to

> disagree that we need them. He claims that since XP comes with the TS

> client

> (RDC) that it is no longer required.

> We have our own W2K3/Citrix server that is a terminal server. It is not

> a DC but it is part of our domain. When we first set it up to be a TS we

> did get the deafult prompt that

> it will remain operable for 90 days in which you will need to activate it

> and

> configure the licensing. Well I believe when we activated it we sort of

> got

> around that and used "per device" option which allowed us unlimited

> access.

> When I go to the TS License Manager and view our licensing it states:

>

> Product = "Existing Windows 2000 Server - Terminal Services CAL Token (per

> device)"

> Type = Built-in

> Total = Unlimited

> Available = Unlimited

> Issued = 0

>

> I need some experts to shed some light on this. Is this correct and do I

> need to purchase TS licenses also. thanks.

>

>

Guest Vera Noest [MVP]
Posted

Re: Terminal server and W2K3 Server licenses

 

Rob Leitman has already answered your first question, let me

explain the situation on your existing TS:

 

What you did when the licensing warning came up is that you

activated the TS Licensing Server, and changed the TS Licensing

mode of the Terminal Server to use "Per User" licensing. You can

check this in Terminal Services Configuration - Server Settings.

Since Per User licensing is unmanaged on a 2003 TS, you were able

to continue to use the TS without installing any licenses at all on

the TS Licensing Server. This is of course a violation of the EULA.

 

The only licenses which are present on your 2003 TS Licensing

Server are the "Existing Windows 2000 Server TS CALs".

 

And here's the reason for your coworker's misunderstanding:

those free licenses are issued to XP Pro and W2K Pro clients *when

they connect to a W2K TS*. These clients do *not* come with a

built-in license, but they get a free one on connecting to a W2K

TS. And since a 2003 TS Licensing Server also can act as a

Licensing Server for W2K Terminal Servers, it contains these free

W2K TS CALs.

 

But XP Pro and W2K Pro clients do *not* get a free license when

connecting to a 2003 TS.

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

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

___ please respond in newsgroup, NOT by private email ___

 

"GotNoIdea" <GotNoIdea@GotNoEmail.com> wrote on 03 aug 2007 in

microsoft.public.windows.terminal_services:

> We have our own W2K3/Citrix server that is a terminal server. It

> is not a DC but it is part of our domain. When we first set it

> up to be a TS we did get the deafult prompt that

> it will remain operable for 90 days in which you will need to

> activate it and

> configure the licensing. Well I believe when we activated it we

> sort of got around that and used "per device" option which

> allowed us unlimited access. When I go to the TS License Manager

> and view our licensing it states:

>

> Product = "Existing Windows 2000 Server - Terminal Services CAL

> Token (per device)"

> Type = Built-in

> Total = Unlimited

> Available = Unlimited

> Issued = 0

>

> I need some experts to shed some light on this. Is this correct

> and do I need to purchase TS licenses also. thanks.

Guest GotNoIdea
Posted

Re: Terminal server and W2K3 Server licenses

 

Hi Vera,

thank you very much for your explaination. I did read this article and

according to this MS is aware of the issue and there fore offered

complimentary TS server licenses for those who want to take advantage of

W2Ke TS server and who purchase XP before April 24, 2003.

 

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

 

Now according to this article the cut off date for those complimentary TS

licens was June 30, 2007 so I just missed it. So am I still in violation of

the EULA even though I have legal copies of XP purchased before April 24,

2003?

 

"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message

news:Xns99821574588veranoesthemutforsse@207.46.248.16...

> Rob Leitman has already answered your first question, let me

> explain the situation on your existing TS:

>

> What you did when the licensing warning came up is that you

> activated the TS Licensing Server, and changed the TS Licensing

> mode of the Terminal Server to use "Per User" licensing. You can

> check this in Terminal Services Configuration - Server Settings.

> Since Per User licensing is unmanaged on a 2003 TS, you were able

> to continue to use the TS without installing any licenses at all on

> the TS Licensing Server. This is of course a violation of the EULA.

>

> The only licenses which are present on your 2003 TS Licensing

> Server are the "Existing Windows 2000 Server TS CALs".

>

> And here's the reason for your coworker's misunderstanding:

> those free licenses are issued to XP Pro and W2K Pro clients *when

> they connect to a W2K TS*. These clients do *not* come with a

> built-in license, but they get a free one on connecting to a W2K

> TS. And since a 2003 TS Licensing Server also can act as a

> Licensing Server for W2K Terminal Servers, it contains these free

> W2K TS CALs.

>

> But XP Pro and W2K Pro clients do *not* get a free license when

> connecting to a 2003 TS.

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

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

> ___ please respond in newsgroup, NOT by private email ___

>

> "GotNoIdea" <GotNoIdea@GotNoEmail.com> wrote on 03 aug 2007 in

> microsoft.public.windows.terminal_services:

>

>> We have our own W2K3/Citrix server that is a terminal server. It

>> is not a DC but it is part of our domain. When we first set it

>> up to be a TS we did get the deafult prompt that

>> it will remain operable for 90 days in which you will need to

>> activate it and

>> configure the licensing. Well I believe when we activated it we

>> sort of got around that and used "per device" option which

>> allowed us unlimited access. When I go to the TS License Manager

>> and view our licensing it states:

>>

>> Product = "Existing Windows 2000 Server - Terminal Services CAL

>> Token (per device)"

>> Type = Built-in

>> Total = Unlimited

>> Available = Unlimited

>> Issued = 0

>>

>> I need some experts to shed some light on this. Is this correct

>> and do I need to purchase TS licenses also. thanks.

Guest Vera Noest [MVP]
Posted

Re: Terminal server and W2K3 Server licenses

 

Did you try to get the transition licenses from the website anyway?

If you didn't succeed because it's past the June 30 deadline, then

you're out of luck, I would say.

From the website: "After June 30th, 2007, customers forfeit their

right to this process for complimentary TS CALs."

 

The deadline has already been extended with a year and a half, it

was originally Jan 1, 2006.

 

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

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

___ please respond in newsgroup, NOT by private email ___

 

"GotNoIdea" <GotNoIdea@GotNoEmail.com> wrote on 04 aug 2007 in

microsoft.public.windows.terminal_services:

> Hi Vera,

> thank you very much for your explaination. I did read this

> article and according to this MS is aware of the issue and there

> fore offered complimentary TS server licenses for those who want

> to take advantage of W2Ke TS server and who purchase XP before

> April 24, 2003.

>

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

> 003.mspx

>

> Now according to this article the cut off date for those

> complimentary TS licens was June 30, 2007 so I just missed it.

> So am I still in violation of the EULA even though I have legal

> copies of XP purchased before April 24, 2003?

>

> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote

> in message

> news:Xns99821574588veranoesthemutforsse@207.46.248.16...

>> Rob Leitman has already answered your first question, let me

>> explain the situation on your existing TS:

>>

>> What you did when the licensing warning came up is that you

>> activated the TS Licensing Server, and changed the TS Licensing

>> mode of the Terminal Server to use "Per User" licensing. You

>> can check this in Terminal Services Configuration - Server

>> Settings. Since Per User licensing is unmanaged on a 2003 TS,

>> you were able to continue to use the TS without installing any

>> licenses at all on the TS Licensing Server. This is of course a

>> violation of the EULA.

>>

>> The only licenses which are present on your 2003 TS Licensing

>> Server are the "Existing Windows 2000 Server TS CALs".

>>

>> And here's the reason for your coworker's misunderstanding:

>> those free licenses are issued to XP Pro and W2K Pro clients

>> *when they connect to a W2K TS*. These clients do *not* come

>> with a built-in license, but they get a free one on connecting

>> to a W2K TS. And since a 2003 TS Licensing Server also can act

>> as a Licensing Server for W2K Terminal Servers, it contains

>> these free W2K TS CALs.

>>

>> But XP Pro and W2K Pro clients do *not* get a free license when

>> connecting to a 2003 TS.

>> _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

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

>> ___ please respond in newsgroup, NOT by private email ___

>>

>> "GotNoIdea" <GotNoIdea@GotNoEmail.com> wrote on 03 aug 2007 in

>> microsoft.public.windows.terminal_services:

>>

>>> We have our own W2K3/Citrix server that is a terminal server.

>>> It is not a DC but it is part of our domain. When we first set

>>> it up to be a TS we did get the deafult prompt that

>>> it will remain operable for 90 days in which you will need to

>>> activate it and

>>> configure the licensing. Well I believe when we activated it

>>> we sort of got around that and used "per device" option which

>>> allowed us unlimited access. When I go to the TS License

>>> Manager and view our licensing it states:

>>>

>>> Product = "Existing Windows 2000 Server - Terminal Services

>>> CAL Token (per device)"

>>> Type = Built-in

>>> Total = Unlimited

>>> Available = Unlimited

>>> Issued = 0

>>>

>>> I need some experts to shed some light on this. Is this

>>> correct and do I need to purchase TS licenses also. thanks.


×
×
  • Create New...