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

Cannot find Windows 2003 Terminal Server License Server

We have three "domain controllers / file servers" - which have Windows 2003 standard 64 bit. We have a separate Windows 2003 standard 32 bit, which we use as a Terminal Server, which is a member on the domain.

The license server is residing on the primary domain controller (PDC).

When we log on to the Terminal Server via rdp, the following message appears:

"Cannot find Windows 2003 Terminal Server License Server"...

"This computer is past its grace period and needs to connect to a Windows Server 2003 Terminal Server License Server; otherwise, Terminal Server will stop working. Click here to launch Terminal Services Configuration tool to assign a valid License Server.

When I click "here" Terminal Services Coniguration\Connections window comes up.

Under Server Settings, in License server discovery mode, I have changed it to "As specified", and have specified the PDC as the license server. When I click "Check names" the following message comes up:

"The specified License Servers are valid Windows 2003 Terminal server License Servers"


When I go to Terminal Server Licensing. The PDC is listed as "Windows Server 2003 - TS Per User CAL" with 17 open licenses.


Why does the message keep appearing every time anyone logs onto Terminal Server?


Is there something I have missed?
0
encoded66
Asked:
encoded66
  • 3
  • 2
1 Solution
 
beaconlightboyCommented:
I experienced this exact problem a while back.  It's apparently a glitch.  I fixed it by modifying/creating the following registry key on the terminal server.

HKEY_LOCAL-MACHINE\SYSTEM\ControlSet001\Services\TermService\Parameters\LicenseServers
if this key does not exist, create it.

then add a key with no value of the IP address or name of your license server
i attached a screen shot of my servers registry.  We have since turned over all our servers and did not have to do this when we re-installed the OS.  i presume it's fixed R2.

Doc1.doc
0
 
encoded66Author Commented:
I have created a new key LicenseServers, and under the key  I have made a new key (folder) with the ip address name of the pdc. Have logged out and logged back in. The message still appears.

What other settings do i need to put under that key?
0
 
encoded66Author Commented:
Do i need to restart the service or anything like that?
0
 
beaconlightboyCommented:
This is the KB article i used back then.

http://support.microsoft.com/kb/279561

and yes you will need to restart the server.
0
 
encoded66Author Commented:
Thank you for all your help
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: SQL Server Core 2016

This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.

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