Re: Terminal Services confusion...

Thanks for the input, again. I went into our Remote Desktop Users group and
removed about 1/2 of the entries. Those staff are never gone from the
office and simply don't need access. Thanks!

Bill

"Vera Noest [MVP]" <Vera.Noest@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:Xns9BB79D628A270veranoesthemutforsse@xxxxxxxxxxxxxxxx
OK, that sounds fine.
You don't really need to move the 2003 LS away from the 2003
TS/Citrix server. With so few users, it shouldn't create a
performance issue to run bot LS and TS on the same server.

And yes, you need some sort of routine to ensure that you stay
within your licensing limit of 50 total users. Memebership in the
local Remote Desktop Users group on the TS is easiest to regulate.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*

"Bill Clark" <billc@xxxxxxxxxxxx> wrote on 18 feb 2009:

Vera,

Argghh!! MY BAD!! That 2nd server IS running Win2003 Standard
edition....my fault!! In response to point #2, yes, all clients
are Windows XP, with only 2 of us running Vista. We have only
the 1 Citrix Metaframe server that IS Windows 2003 and has the
2nd TS LS installed on the box. We only have 15 concurrent
licenses from Citrix, and about 65 users (all on XP machines)
that could access it. What I'm thinking is this:

a) We are phasing out the 1st licensing server as it is
installed on a Windows 2000 server running AD; we are migrating
to Windows 2008 AD and once DNS, DHCP and the roles are migrated
off that server, we will do away with it. Once AD is off of it,
I see no reason to keep it around since nothing is using it for
TS licenses.

b) Possibly install a new TS LS on a different Windows 2003
server and move/migrate the 2003 TS CALs to that box so it isn't
on the same server as Citrix. At the same time reduce the
number of users that could actually use it to under 50 since I
only have the 50 per-user 2003 TS CALs.

Thoughts?

Bill


"Vera Noest [MVP]" <vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
in message
news:Xns9BB6D7306E589veranoesthemutforsse@xxxxxxxxxxxxxxxx
There are a number of puzzling things in your post:

1. a Windows 2000 TS Licensing Server cannot handle 2003 TS
CALs, and you cannot install them on it, as documented here:

839878 - You cannot install the Terminal Services CAL pack on
Windows Server 2003-based or Windows 2000 Server-based
computers http://support.microsoft.com/?kbid=839878

So are you really sure that the second LS is running W2K?
You can only install 2003 TS CALs on a W2K LS by down-grading
them, and then they become effectively W2K TS CALs, and
moreover, they become W2K Per Device TS CALs, since a W2K LS
doesn't know what a Per User TS CAL is. But I must admit that
I've never done that myself, so I'm not 100% sure how such
downgraded TS CALs would show up in the W2K TS Licensing
Manager.

2. According to your post, 25 built-in licenses have been
issued, and none of the purchased licenses. Assuming that all
of your clients run XP or Vista, they all receive a free TS CAL
from the built-in pool of licenses (those that are called
"Existing Windows 2000 Licenses: Built In") and you don't need
the purchased licenses at all (of which you have 150 in total).
Maybe these licenses were bought at a time that the company
used thin clients, or other down- level clients which needed a
purchased TS CAL?

3. Assuming that you only have Terminal / Citrix servers that
run W2K, you have no use for Per User licenses, again because
W2K doesn't know the concept of Per User licenses.

Now to what you need now (and in the near future, in case you
upgrade):

You *can* install W2K TS CALs on a 2003 TS Licensing Server.
It's the other way around that doesn't work. So yes, you could
consolidate the TS Licensing Servers onto a single 2003 LS and
install all of your licenses on it. Note that you do not have
to do anything at the moment, a 2003 TS LS also contains a free
pool of built-in W2K TS Per Device CALs, so you don't have to
(and can't) move these, you simply get a new pool on every 2003
TS LS. If you would want to move the purchased licenses to
another LS, you can do so, but it involves calling the
Clearinghouse. For details, check:

How do I move my TS licenses to a new TS Licensing Server?
http://ts.veranoest.net/ts_faq_licensing.htm#move_LS

If you decide to upgrade your *Terminal Server* to 2003, you
will not be able to use any of the W2K licenses anymore, you'll
need a 2003 TS CAL for every client or user (no built-in pool
of 2003 TS CALs). If you do so, you should first decide what is
cheapest for you, Per User or Per Device:
http://ts.veranoest.net/ts_faq_licensing.htm#Device_vs_User_TSCA
Ls _________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"Bill Clark" <billc@xxxxxxxxxxxx> wrote on 18 feb 2009 in
microsoft.public.windows.terminal_services:

I've inherited an aging system that I'm questioning what was
done with Terminal Services and if we are over-loaded on
licensing. From what I can tell, we have 2 TS Licensing
Servers.

The first one is hosted on our main AD controller (Win2k
server) and shows the following: (Product:
Type-Total-Available-Issued) Existing Windows 2000 Licenses:
Built In - Unlimited - Unlimited - 25 (none have been issued
since June of 2008) Windows 2000 Server-TS CAL Token(per
device): Open - 50 - 50 - 0 Windows 2000 Server-TS CAL
Token(per device): Open - 50 - 50 - 0

The 2nd licensing server is on our old, Citrix Metaframe box
(win2k server) that is currently licensed for 15 concurrent
users: Existing Windows 2000 Server-TS CAL Token(per device):
Built in - Unlimited - Unlimited - 0
Windows Server 2003-TS Per User CAL Token: Open - 50 - 50 -0

Our company has 110 employees, and about 65 of them have
rights to use the Citrix server (although only 1/2 have EVER
used it) that is limited to 15 concurrent users. In addition,
we have about 20 various Windows servers that only 3 of us
ever remote into and use, and never at the same time. I'm
trying to update our AD to at least 2003 and would like to do
away with anything not needed, like old, unused licensing
servers and from what I understand I cannot transfer the Win2K
TS CAL's to run on Win2003 TS server. So, with that all said,
what do I REALLY need for TS licensing and server? What else
could be using any CAL's and do I need both sets anymore? We
don't run Exchange so that isn't in the mix. Any light shed
on this would be greatly appreciated.

Bill


.

Relevant Pages

  • Re: Problems with the Windows 2003 License Server
    ... purchased licenses being issued. ... "ExistingWindows2000 Per Device TS CALs Tokens)". ... Now I had downgrade some of the W2k3 Servers for publishing ... server) is started. ...
    (microsoft.public.windows.terminal_services)
  • 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: Licensing problem...
    ... 2000, XP Pro, Vista Business, 2003 Server, 2008 Server, etc. receive a "free" TS CAL from the pool you mentioned. ... The 25 licenses you see were issued from the built-in "free" pool, and have nothing to do with your problem. ... The solution is to purchase TS CALs for the number of devices that run home OS versions and install them on your TS licensing server. ... The above information applies to a Windows 2000 Server TS. ...
    (microsoft.public.windows.terminal_services)
  • Re: Transfer Licenses of Server Win 2000 to a server Win 2003
    ... 2003 server you need Windows 2003 CALs - so you need to buy new ones. ... > nwe server with Windows 2003...how can i transfer those licenses that i ...
    (microsoft.public.windows.server.migration)
  • Re: CAL
    ... If you just have the 5 CALs that came with the server, ... So SBS can tell which one you've bought based on the license code? ... You go and you buy 10, 'per user, CALs. ... it's up to you to keep track of the licenses. ...
    (microsoft.public.windows.server.sbs)
Loading