[Last Call] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 274
  • Last Modified:

Terminal server 2003 will not assign tokens

We have a 2003 network with one 2000 MS server (with 2000 Exchange server & 
2000 TS server) the other fiver servers are 2003 SP1 servers.

One 2003 server Enterprise is a dedicated 2003 TS server. The 2003 TS
licensing server is installed on that server.

The licensing server is assigning temporary licenses instead of assigning
tokens. The licensing manager showed the 2000 TS server, the 2003 TS server
and the temporary licenses assigned.

The TS 2003 license server showed the actual license number but with none

I added the suggested registry change to hard code the 2003 license server.

I uninstalled and re-installed the 2003 TS license server.

Now the License server only shows the 2000 license server and the temporary
assigned licenses. No 2003 TS license server shows.

Most TS clients are being assigned temporary licenses. One TS client can
connect but no temporary license is shown. BTW, this is the same client that
showed it's temporary license had expires before I re-installed the 2003
license server.

How can I resolve this issue?

  • 4
  • 2
2 Solutions
User or Device licenses?

Is your TS setup to use the same licenses as you have installed?  If you installed User licenses make sure you are also configured on a User license mode (in TS Configuration Manager)

MS01-052: Clients with an Expired Temporary License May Be Unable to Connect to Terminal Services

DMVanceAuthor Commented:

The articles refer to 2000 TS.This 2003 TS. The TS temporary licenses are being assigned per device. How can one switch from per device to per user?

Thanks for the quick response.

BTW, I received no responses on MS newsgroup. Another person posted a similar question with no response either.

craig200x is right, the license modes MUST be the same.
Prepare for your VMware VCP6-DCV exam.

Josh Coen and Jason Langer have prepared the latest edition of VCP study guide. Both authors have been working in the IT field for more than a decade, and both hold VMware certifications. This 163-page guide covers all 10 of the exam blueprint sections.

DMVanceAuthor Commented:

Your answers seem very logical but...

When installing the licenses the mode is not requested during the installation or indicated on the license code sheet

1) The first installation question asked is License package.

2) I select License pak ( retail purchase).

3) The License code(s) are requested which I enter.

4) The licensing program connects to the Clearhouse.

5) A message appears stating the server's licenses are actived.

6) Done

Where are the modes selected that you are mentioning? I see no options in the Terminal Server License or the Terminal Server Manager programs. What am I missing. Is there another program or a hidden option?

Thank you,


When you are setting up your terminal server, the license management wizard will prompt you to choose which type of TS CAL you prefer.

Guidelines for Deploying Terminal Server

DMVanceAuthor Commented:

Okay, now we are getting closer. This TS server was installed almost three months ago and the licensing issue is just appearing because of the 90 day temporary tokens.

In the configuration manager I can see where "Per User" or "Per Device" can be selected.

The licensing server can be set to automatic or by name. By name is selected and is found.

First, are the CALS purchased as  "Per User" or "Per Device" or the determined by the mode of CAL selected at installation? I see nothing on MS License Code paper stating  "Per User" or "Per Device".

Since the server is up and running how can I switch from one CAL mode to another -

1) Change the mode setting in Configuration Manager and restart the server


2) Un-install the license server, change the mode, restart the server, re-install and re-activate the license server?

The guidleines docs state one is unable to monitor the number of "Per User" connections. Does this mean when the installed number of CALS is reached no more TS clients can physically connect or Microsoft does not track the number of "Per User" connections and theorically more than the purchased CAL connections could be physically connected sucessfully?

Thanks in advance,

DMVanceAuthor Commented:
Both responders gave me enough good background information to call MS's billable tech support. MS deemed it was a corrupted license and did not charge me for the repair and tech support call, $240.

Thank you,


Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now