Terminal services licensing

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Migrated from one domain to another domain.
When we were a part of the old domain, the terminal server, a windows 2000
server, worked just fine.

But now that we are in the new domain our terminal server is unable to find
a terminal server licensing server and the following events gets logged
whenever a client that never have got any ts license before tries to connect:
---
Event Type: Warning
Event Source: TermService
Event Category: None
Event ID: 1004
Date: 2004-12-21
Time: 15:47:11
User: N/A
Computer: ABC123
Description:
The terminal server cannot issue a client license.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
---

And a few times a day, usually at night this event is generated:
---
Event Type: Warning
Event Source: TermService
Event Category: None
Event ID: 1010
Date: 2004-12-21
Time: 05:47:02
User: N/A
Computer: ABC123
Description:
The terminal services could not locate a license server. Confirm that all
license servers on the network are registered in WINS\DNS, accepting network
requests, and the Terminal Services Licensing Service is running.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
---

Note that the problem only occurs on computers that don't have any ts
licenses.

Is there any special configuration needed to make the terminal server find
the licensing server?
If i have understood this right, there should be one central license server
for the ad domain and the terminal server should be able to find it
automatically if it's on a DC.

Any ideas how to fix this?
 
swefax said:
Migrated from one domain to another domain.
When we were a part of the old domain, the terminal server, a windows 2000
server, worked just fine.

But now that we are in the new domain our terminal server is unable to
find
a terminal server licensing server and the following events gets logged
whenever a client that never have got any ts license before tries to
connect:
---
Event Type: Warning
Event Source: TermService
Event Category: None
Event ID: 1004
Date: 2004-12-21
Time: 15:47:11
User: N/A
Computer: ABC123
Description:
The terminal server cannot issue a client license.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
---

And a few times a day, usually at night this event is generated:
---
Event Type: Warning
Event Source: TermService
Event Category: None
Event ID: 1010
Date: 2004-12-21
Time: 05:47:02
User: N/A
Computer: ABC123
Description:
The terminal services could not locate a license server. Confirm that all
license servers on the network are registered in WINS\DNS, accepting
network
requests, and the Terminal Services Licensing Service is running.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
---

Note that the problem only occurs on computers that don't have any ts
licenses.

Is there any special configuration needed to make the terminal server find
the licensing server?
If i have understood this right, there should be one central license
server
for the ad domain and the terminal server should be able to find it
automatically if it's on a DC.

Any ideas how to fix this?
Click to expand...
There is a registry setting to specify what license server to use. Search
the knowledge base let me know if you can't find it.

Matt
 
Hi Matt,

I can tell you that we had tried all the solutions both to change the
registry settings and the script used for W2003.
But the problem was that the Enterprise licensing server was in a strange
mode.
After restart of that server all went fine and we could use the registry to
set the default license server.
 
Back
Top