Very Confused

[Brian]

A little background on my situation. We were in a
WindowsNT 4.0 domain until just recently. We had a mix
of NT4.0 servers including a PDC and BDC. We also had
some 2000 servers up and running. My terminal server is
sitting on a 2000 server. I upgraded my domain to a 2003
with AD domain and also changed my Domain name from
DomainA to DomainB and decommisioned all my NT4.0
PDC/BDC's and rejoined all my 2000 servers to the new
domain. As far as I can tell my TS is still working.

From my understanding TS Licensing Server has to be run
on 2000 Domain Controller(which I dont have). Is it
possible that the licensing server could have been
running on an NT4.0 BDC or PDC and the TS sitting on a
2000 server? It this is not possible how is my TS
working when it is not sitting on a Windows 2000 DC?

Whenever I open TS Licensing on the W2K terminal server
it searchs for a licensing server. The first server it
tries to find is an old NT4.0 BDC which it cannot find
(because it has been shut-off). If I plugged the old
NT4.0 BDC back in it sees it then searches for other
servers and ultimately tells me there is no license
server available.

Should I just shut the old server off completely and
purchase TS license's for a W2K3 DC and put my terminal
server on that?

If anybody has any ideas I would be very grateful.

 

[Vera Noest [MVP]]

Your W2K TS needs a LS on a Domain Controller, but not necesarily
a W2K Domain Controller.
So just install a 2003 LS on one of your 2003 DCs, deactivate your
old W2K Licensing server (but not the terminal services), activate
the new 2003 LS, phone the Clearinghouse to get your TS CALs re-
issued and install them on the new 2003 LS. 2003 LS can handle
both W2K and 2003 TS CALs.

Since your old LS was running on the W2K TS itself (if I get the
picture right), you might previously have hardcoded the name of
the LS into the registry of the TS. If so, remove that registry
entry and verify that the TS can locate the LS.