Re: What is the best licensing option for TS?

No, that's not possible, apart from running Citrix on top of the
OS, which will cost you a lot more than the 2003 TS CALs.
That's one reason why I mentioned features.....

And in the long run, how long are you planning to run on an
unsupported OS, once the security fixes stop coming?

Since you've already bought these licenses, I would strongly
suggest you go for 2003.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*

"Jordan" <none@xxxxxxxx> wrote on 01 jun 2006:

{W2K is cheapest. But have you considered which features you
need?}

I don't mind eating the licenses if in the long run I am better
off with W2K as the TS. I don't run anything that appears to
need 2003 instead of W2K however the only draw back seems to be
that I can only connect to my W2K servers in 256 color mode.
Is there any way to get a better color resolution on W2K?


"Vera Noest [MVP]" <vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
in message
news:Xns97D4EDCC5C996veranoesthemutforsse@xxxxxxxxxxxxxxxx
answers inline.

"Jordan" <none@xxxxxxxx> wrote on 31 maj 2006 in
microsoft.public.windows.terminal_services:

I am trying to find out what is the best licensing method for
Terminal Server for me.

1. I have both Windows 2000 and 2003 Servers.
2. I can make either one a Terminal Server if needed.
3. I have purchase 20 Terminal Server client Licenses for
2003. 4. Half my clients are 2000 Pro and half XP Pro.
5. I log in to the server from at least 3 computers and other
users may as well.

I would think that my best option would be Per User since I
have less than 20 users and they probably will log in from
more than one machine.

I agree so far.

What is confusing me is the following:

1. I have read that XP Pro clients come with a built in TS
License for free.

This is incorrect. W2K Pro and XP Pro clients receive a free TS
CAL from the TS Licensing Server when they connect to a W2K TS.
When thet connect to a 2003 TS, they need a purchase TS CAL,
just like any other client. The client OS does *not* contain a
built-in TS CAL.

2. Terminal Server Licensing manager shows 3 types of
licenses: -- Existing W2K Server CAL Per Device - UNLIMITED
-- Temporary for W2K3 Per Device - Temporary
-- W2K3 Per User CAL - (20)

OK, this reveals that you have installed Per User TSCALs, but
your Terminal Server is configured in Per Device licensing
mode. That's why the LS issues Temporary Per Device licenses.
You have to change the licensing mode of your TS to match your
TS CALs!

The way this looks to me is that if I have my Terminal Server
as a Windows 2000 Terminal Server I can have Unlimited amounts
of clients for free and I did not need to buy those 20
licenses.

Correct.

If I want to use a 2003 Server (which I prefer to do) and all
I am using are XP clients I only need to purchase TS CALs for
W2K and below clients and set the licensing scheme for Per
Device and have up to 20 non-XP clients connecting.

Incorrect. You need a purchased TS CAL for every client or
user.

Do I have this
correct? If so, what is the best option for me if I have
mostly XP clients connecting remotely?

W2K is cheapest. But have you considered which features you
need?

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

Relevant Pages

  • RE: Licensing Change from Per User to Per Device
    ... user CAL's) Now the 700 or so temporary per device CAL licenses that I see ... > change the licensing mode of your Terminal Server. ... > start to issue Per User TS CALs and everything will be fine. ... >>> Windows Server 2003 Pricing and Licensing FAQ ...
    (microsoft.public.windows.terminal_services)
  • Re: Problems with the Windows 2003 License Server
    ... all clients connecting to the 2003 TerminalServerwill use a Per ... CALs Tokens)". ... W2k3) was equipped with 400 TS Cals, terminal servers ... that a licenses will be pulled - Can I make a test ...
    (microsoft.public.windows.terminal_services)
  • Re: Windows 2000 terminal servers in 2003 domain
    ... So, in my case, it will not work with my purchsed W2K TS per device CALs (at ... CAL when they connect to your W2K Terminal Server. ... Server can have Windows 2000 Terminal Server per Device Licenses ...
    (microsoft.public.windows.terminal_services)
  • Re: licensing problem
    ... See my other post - TS CALS DON'T EXPIRE!!!!! ... license server and becomes available again for another client. ... MCSE, CCEA, Microsoft MVP - Terminal Server ... W2K clients *only* receive a free license when they ...
    (microsoft.public.windows.terminal_services)
  • Re: Temporary Licences for Windows2000 Terminal Services Client
    ... it seems that your clients are running on temporary licenses. ... Are the Terminal Server and the TS Licensing Server running on the ... > so that we have Temporary Licences somehow instead of Permanent ...
    (microsoft.public.windows.terminal_services)
Loading