Non-Version Specific Windows TS CALs showing up as 2000 TS CALs

[Guest]

We have a windows 2000 DC that is being used as a Terminal Server Licensing
Server. We installed all of our licenses after it was set up.

Now that we are starting to deploy Windows Server 2003 machines as Terminal
Servers, we are starting to run into problems because they won't pull those
licenses which should be non-version specific but are showing up as 2000 TS
CALs.

I'm guessing I'm probably going to have to call MS about this, but I'm not
sure exactly which group.

Any help would be greatly appreciated.

 

[Mike D]

call ms IT tech Support and tell them you have a licensing issue. They
should nto charge you and will direct you to the right people.
Mike D

 

[Vera Noest [MVP]]

A Windows 2003 Terminal Server can only work with a 2003 TS
Licensing Server. The reason is that you need 2003 TS CALs, which
come in 2 flavours: Per User and Per DEvice.
Since a Windows 2000 TS Licensing server doesn't know what a "Per
user" license is, it doesn't work as a Licensing Server for a 2003
TS.

So you need 3 things:
* install and activate a 2003 TS Licensing Server. This service
doesn't have to run on a Domain Controller (as in W2K), so your
TS can also be the LS
* buy and install 2003 TS CALs. Your existing Windows 2000 TS CALs
are indeed version specific and will only be issued to clients
that connect to a Windows 2000 TS, not to a 2003 TS
* the above is alse true for normal server CALs: you need those as
well for 2003

Recommended reading:

Windows Server 2003 Pricing and Licensing FAQ
http://www.microsoft.com/windowsserver2003/howtobuy/licensing/pric
licfaq.mspx

What's New in Windows Server 2003 Licensing '
http://www.microsoft.com/windowsserver2003/howtobuy/licensing/over
view.mspx

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---

"=?Utf-8?B?U2hhd24gQ3VkZQ==?=" <Shawn
(e-mail address removed)> wrote on 29 okt 2004 in
microsoft.public.win2000.termserv.apps: