TS license server gone with AD upgrade

[Brian]

We WERE running an NT4 domain, which included a windows
2000 server (call it "REMOTE"). This W2K server was set
up as a Terminal Services License server (complete with 15
licenses). We use this server as our Citrix Metaframe
Server.

We upgraded the domain to AD by upgrading the NT4 PDC. We
did not touch the original W2K server REMOTE.

The AD DC LicenseService is now reporting all sorts of
license violations, which isn't a big deal because we've
got all our software licensed.

What is a big deal is now I cannot connect to the TS
licensing server that WAS running on REMOTE. I used to be
able to see which of our Citrix clients had connected to
REMOTE and pulled a license. The message says "No
Terminal Services license server is available in the
current domain or workgroup."

Is my license server info that lived on REMOTE gone? Do I
have to create a new license server on my AD DC? How am I
going to convice Microsoft to give me 15 licenses?

Any help would be appreciated. Thanks.
Brian

 

[Matthew Harris [MVP]]

Have you tried hardcoding the name of the cliense server
into the registry of the terminal server?

support.microsoft.com/default.aspx?scid=kb;en-
us;239107&Product=win2000

-M

 

[Guest]

http://support.microsoft.com/default.aspx?scid=kb;EN-US;30657

Your TS is now polling the DCs for a TSLS but there isn't one on the DC. In an AD environment w/ 2000 TS the TSLS MUST be on a DC. With 2003 TS the TSLS can be on any 2003 server in the same domain

Patrick Rous
Microsoft MVP - Terminal Serve
http://www.workthin.co

----- Brian wrote: ----

We WERE running an NT4 domain, which included a windows
2000 server (call it "REMOTE"). This W2K server was set
up as a Terminal Services License server (complete with 15
licenses). We use this server as our Citrix Metaframe
Server

We upgraded the domain to AD by upgrading the NT4 PDC. We
did not touch the original W2K server REMOTE

The AD DC LicenseService is now reporting all sorts of
license violations, which isn't a big deal because we've
got all our software licensed

What is a big deal is now I cannot connect to the TS
licensing server that WAS running on REMOTE. I used to be
able to see which of our Citrix clients had connected to
REMOTE and pulled a license. The message says "No
Terminal Services license server is available in the
current domain or workgroup.

Is my license server info that lived on REMOTE gone? Do I
have to create a new license server on my AD DC? How am I
going to convice Microsoft to give me 15 licenses

Any help would be appreciated. Thanks
Bria

 

[Brian]

So, I guess my licensing info is gone. Terrific.

Well, Matthew and Patrick, thanks for your help.

Looking forward to dealing with Microsoft on this one...
Brian

-----Original Message-----
http://support.microsoft.com/default.aspx?scid=kb;EN- US;306578

Your TS is now polling the DCs for a TSLS but there isn't

one on the DC. In an AD environment w/ 2000 TS the TSLS
MUST be on a DC. With 2003 TS the TSLS can be on any 2003
server in the same domain.

 

[Guest]

Matthew, I believe this only works to point the TS to a TSLS that exists on a particular DC, not to a member server or the TS lise you can do in 2003

I don't think any of this is a big deal, as all he has to do is install the TSLS on a DC

Patrick Rous
Microsoft MVP - Terminal Serve
http://www.workthin.co

----- Matthew Harris [MVP] wrote: ----

Have you tried hardcoding the name of the cliense server
into the registry of the terminal server

support.microsoft.com/default.aspx?scid=kb;en
us;239107&Product=win200

-