Terminal Services - Urgent

[DMKanz]

I am having problems issueing licenses. I was currently
running Terminal Services Licensing on a Windows 2000
member server in a Windows NT 4.0 domain without any
problems. We have currently upgrade to a Windows 2000
domain. Now my W2k member service no longer issues or
recognizing licenses as I can not start the Terminal
Services Licensing service due to the server belongs to a
W2k domain (service specific error code 29). I do have a
Windows 2000 domain controller running terminal services,
but it does not seem to issues or recognize the W2k
professional license when my user logon to the member
server. Any help would be appreciated

Thanks in advance

DMKanz

 

[Vera Noest [MVP]]

In a W2K domain, the TS Licensing Service must run on a Domain
Controller.
Install and activate TS Licensing on your DC. Uninstall it from
your old LS.
If you have any purchased TS CALs, call the Clearinghouse to get
them re-issued.

Note: you write that the DC is running Terminal Services. If that
means TS in Application mode, be aware that this is *not*
recommended, for security and performance reasons.

 

[DMKanz]

Vera

This is how I was currently configured:

Server 1 was a Windows NT 4.0 sp6a PDC running as an
exchange server.

Server 2 was a Windows NT 4.0 sp6a BDC running as a
file/print server

Server 3 was a Windows 2000 sp4 member server running as
an application server, also running TS in application mode
along with Citrix Server Metaframe SR2.

This is how I am now configured:

Server 1 is a Windows NT 4.0 sp6a BDC (demoted from PDC)
running as an exchange server.

Server 2 is a Windows 2000 sp4 PDC (promoted from BDC and
upgraded to Windows 2000) running as a file/print server,
also running TS in remote administration mode.

Server 3 is a Windows 2000 sp4 member server running as an
application server, but TS Licensing Service will not
start. Also still running Citrix.

When I now try to give a user access thru Citrix on a
Windows 2000 professional machine I receive a
message "Network or dialup problems are preventing
communication with the Citrix Server. An attempt to auto
matically restore the connection will begin after a delay
to let the network recover." I check with Citrix and
found that it is a licensing issue. I also receive in
event viewer the following message (Server 3) "The
terminal server cannot issue a client license" - Event ID
1004

Thanks in Advance

DMKanz

 

[Vera Noest [MVP]]

Since your Terminal Server (= Citrix server = server 3) now is a
member server in a Windows 2000 domain, the TS Licensing server
must run on the domain controller, which is your server 2.

 

[DMKanz]

Vera

Okay I have uninstalled TS Licensing on Server 3 but I
still get the same errors. Do I have to force Server 3 to
look for Server 2 as the TS Licensing server? I also
still receive event ID 1004 when trying to connect thru
Citrix.

Thanks in advance

DMKanz

 

[Vera Noest [MVP]]

Have you installed and activated the TS Licensing Service on your
Domain Controller (server 2)?
Have you re-installed the TS CALs on the new LS?

If you *also* see Event 1010 (cannot locate Licensing Server),
then you could point the TS to the new LS:

239107 - Establishing Preferred Windows 2000 Terminal Services
License Server
http://support.microsoft.com/?kbid=239107

 

[Guest]

I have found a fix for this problem.

I had the same problem. I had an NT 4.0 domain with a 2000 Server in app
mode with Citrix loaded. This server also was the TS License Server. When I
upgraded my Domain to AD using 2003 Servers only I started to see problem
with the TS Licensing server. I would not start, displaying 2 errors in
eventlog. Errors were ID's 29 then 7024.

After research I found that I either had to move the license server to a DC
or put it on a member server in a workgroup. Both options were not acceptable
to me. I place a call with MS and after some searching (scratching and
sniffing) the PSS engineer found a case with this problem and found a hidden
switch. In the registry of the TS License server I went to
hklm\SYSTEM\CurrentControlSet\Services\TermServLicensing, modified
"Imagepath" to include, at the end of lserver.exe, the hidden switch "-nodc"
(without quotes). Once this inserted. I started the TS License server and
whalla. It worked. Oh, I also included the servername of the TS license
server as noted in Q261110, I used the IP instead of the name.

I am still receiving random "1010" id's in my eventlog after this fix, that
I will research. But as soon as I did this, users we able to connect.

-Eric

 

[Vera Noest [MVP]]

Yes, I know about that switch, but I would avoid to use it. It's
an undocumented switch, which should be used for troubleshooting
purposes only. Undocumented switched are not guaranteed to work
with the next upgrade or servicepack.

About your Event 1010: that's not a problem, documented here:

281258 - Event 1010 Is Reported After Specifying Default License
Server
http://support.microsoft.com/?kbid=281258

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---