How to Install windows 2003 terminal server license

does anyone have any instructions on "how to Insall" terminal server licensing on a Windows 2003 member server?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Guidelines for Deploying Terminal Server

Installing Your License Server
It is required that at least one Windows Server 2003 license server be present in your Windows Server 2003 Terminal Server environment. For small deployments, it is acceptable to install both the Terminal Server and the Terminal Server Licensing service on the same physical computer. However, for larger deployments we suggest that Terminal Server Licensing be installed on a separate server.

To install Terminal Server Licensing:

1. Click Start, click Control Panel, and then double-click Add or Remove Programs.
2. Click Add/Remove Windows Components.
3. In the dialog box, select Terminal Server Licensing.
4. Follow the instructions in the Windows Components Wizard.

After Terminal Server Licensing is installed, the server becomes a license server and you are asked whether you want to activate the license server. It is highly recommended that you activate the license server. A Terminal Server running on Windows Server 2003 operates for 120 days before the terminal server must discover an activated license server.

4. Activating Terminal Server Licensing
A license server is not considered operational until it is activated. If you do not activate the license server as a part of the installation itself (highly recommended), you can activate it later.

To activate Terminal Server Licensing:

1. On the computer running Terminal Server License Server, click Start, Programs, Administrative Tools, Terminal Server Licensing.
2. If the License Server has not been activated, in the console tree, right-click the Terminal Server License Server you want to activate.
3. Click Activate Server to start the Activation Wizard.
4. In the Activation method list, select Automatic connection (recommended), and then click Next.
5. Follow the instructions in the wizard.
If having problems with license activation, see: 

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Good work IA

one thing though, in a 2003 domain terminal servers look for a license server entry in AD
and the license server is normally installed on a DC

this will work if the license server and the terminal server are the same server or on the same subnet

there is a reg key listed in the white paper for terminal server licensing that tells how to set this on a terminal server
so it can find the license server when not installed on a DC
Intense_Angel, good explanations, does the server makes contact with Microsoft while activating Terminal Server Licensing in step 2 - 5?
CompTIA Security+

Learn the essential functions of CompTIA Security+, which establishes the core knowledge required of any cybersecurity role and leads professionals into intermediate-level cybersecurity jobs.

Sorry, one more thing, what's differences between Per Device and Per User questions during the installation?
yes during that process it does access the web if set to do that in the wizard.
there are three methods I beleive phone, web, an email thing you get to paste in to the wizard.

just call the clearing house and activate it, and then they can help with the licenses too.
See: Activating a Terminal Server license server

if you activate it, you can always deactivate it and start fresh if needed (uninstall/reinstall licensing)

per device are physically installed in the clients registry and get decremented by the license server
use for: same user at same machine all the time this type would work

per user are unmanaged right now, which means the server doesn't check to see if the client has a license installed.
use for: same user uses multiple machines at work and at home

NOTE: a terminal server can only be in per user or per device not both modes (Under TS configuration)
a license server however can server both license types to terminal servers

Also another gotcha

Some additional comments:
- the third option is not email but through the web, using a different machine than the one containing the license server. This is so for when the license server doesn't have internet access.
- SP1 on 2003 server does not change the 'unmanaged' user licenses. Still the same. I'll be looking in R2 shortly to see if MS added it there.
- Be careful when choosing 'device' licenses, especially when external people use the terminal server (e.g. external support, home users, ...). They tend to switch machines between sessions and you can quickly have a lot of unintended use of device licenses. You'll have to wait up to 89 days before they are automatically released. New clients will be handed out temporary licenses which are valid for 90 days. So if the switching between client machines is final then they get a recovered device license after 90 days. If they are continuously switching then you'll need additional licenses, probably more then you anticipated. I found that in many cases going for user licenses is the better option. But your mileage may vary.
- The key mentioned by itforall for letting a TS now where the license server is: HKLM\system\CCS\Services\TermService\Parameters\LicenseServers. There you add netbios name of the License Server as a key (not a value!)
- On the license server you can use a GPO to define which TS can request licenses: local computer policy\ computer configuration\ administrative templates\ windows components \ terminal services \ licensing. You can choose a security group, and only machines in that group will be able to connect to the license server. Also in that GPO you can to prevent license upgrades, so that the 2003 license server will not hand out licenses to 2000 terminal server.

Regards, J.
shorisAuthor Commented:
All of the comments are great however, i didn't know how to install terminal services on a 2003 server which was my question. I found out that on a Windows 2003 server.. once you activate the server, its already configured to insall in application mode. I'm willing to give the points because there were some good comments but none that i can see helped understand the 2003 server. Any suggestions would be great to allocate properly.

Thanks everyone for responding. great info.
Mmm, now you've got me confused.
Your original question was about installing license server for terminal services. Intense Angel perfectly described how to do that. The other comments were about your terminal server finding the license server, etc ...
But now you say that once you activate a 2003 server it's already in application mode. That can't be right.

First of all: putting terminal services in application mode has no direct relation to installing the license server. Those are complete seperate processes.
Secondly: a 2003 server is standard in 'remote desktop for management'-mode. You have to switch it yourself to application mode by going to add/remove programs / windows components and adding 'terminal server'. Then you can use 'terminal services configuration' to switch between 'application mode' and 'administration mode'.
The only way I can explain this confusion is that you installed both 'terminal server' AND 'terminal server license' through 'add/remove windows components' at the same time.
They are just next to eachother in the list. Can you confirm this?

If this is so, then you have your license server on your terminal server. This is not recommended except if the terminal server is the only 2003 server you have. The order of recommendation is having the license server on a 2003 domain controller, if not then on a seperate 2003 member server, if not then on the terminal server itself.

Regards, J.
shorisAuthor Commented:
Since my AD is a Windows 2000 I can't install the terminal server because the TCALS have to be installed if I have Citrix on a 2003 box then the TCals have to reside on a Terminal Server box that is 2003 of which i had another member server that is 2003 is where I activated the terminal server for 2003 TCALS.

I installed the Terminal Service Licensing on the Citrix box.. but there is no where you have the option on a 2003 box the option for application mode like you would on a 2000 box. What i did do is enable the remote desktop on the box for it work for everyone.  I hope i made some sense. :)
the 2000 way is different you do both modes (admin or application) through add/remove programs

in 2003 you install terminal services (read application mode) through windows components in add remove programs.

in 2003 admin mode (read remote desktop) is enabled by right clicking on My Computer/Properties/Remote Tab/Enable RDP on this computer and then grant access

I too was thinking you had license questions
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.