Windows 2003 Server Terminal Server Licensing

  • Thread starter Thread starter Benny
  • Start date Start date
B

Benny

Hi All
I'm a bit unsure about Terminal Server Licensing and am having problems.
Please help if you can.

I have just installed a win2003 terminal server for a client who previously
used a Windows SBS 2000 server as their terminal server.
The users are all Windows 2000 Pro machines.

I now get temporary licence expiration warning for the users.

The old SBS server is still the domain controller and I think has 25 CALs
installed on it (although I am not sure).
I thought that if the clients where win2000 or XP then you didn't need any
separate licences for Terminal service access ??

Any Ideas ?
Also, in the terminal server Licensing MMC on both the new and the old
server, neither are activated, but both show temporary licences. IS this
right ?

Many Thanks in advance
Ben
 
Benny,

I just implemented a Win2k3 Terminal Server connecting to a Win2k domain and
went through everything that you are beginning to go through. Here's the
scoop:

You must have actual Terminal Server Licenses to connect to Win2k3 terminal
server. They may be obtained one of two ways:
1. Purchase them from Microsoft or a reseller. The MS product number for 5
TS Cals is R19-00846
2. If you have any Windows XP Professional computers that were purchased ON
or BEFORE April 14, 2003, you can submit their product keys to Microsoft and
receive a free Terminal Server CAL. It is a one-to-one relationship and you
may submit them to the URL below. Basically, you enter your email address,
select what type of licensing ( Per User or Per Device ), enter the XP
Product Keys, and Microsoft then mails you the Terminal Server license
codes. I have received emails from Microsoft within 10 minutes of
submitting the product keys.
http://licensecode.one.microsoft.com/transition/

Those are the only 2 ways to obtain licensing to Win2k3 terminal server.
Win2k3 licensing is different in that it requires actual license codes to be
entered. A couple of other things:
1. you will need to active your License Server on the Win2k3 box.
2. you may encounter License Server not found messages when opening the
License Manager if the Win2k3 server is part of the domain and the license
server is installed on the Win2k3 server - there is a reg hack for this
3. I would select Per User licensing for Terminal Server, but that is my
preference. Keep in mind that if you select this method, it is an unmanaged
licensing solution and you won't be able to see how many licenses have been
handed out, are available, etc. through the licensing manager...

Good luck,
Bill
 
Thanks Bill, you have been very helpful.
Looks like I'm gonna have to shell out for some TS licences now then.

Thanks again
Benny
 
Back
Top