Domain upgraded to 2003 from NT4, now 2000 TS licensing won't work
Posted on 2006-03-28
We recently upgraded our NT4 domain to Server 2003 AD in Interim mode. We still have some NT4 BDCs left, but the domain is effectively a 2003 AD domain. Prior to this domain upgrade, we have been using Windows 2000 member servers running terminal services and Citrix metaframe XP. After the domain upgrade, we recently noticed that we are getting licensing errors in the event log and brand new clients we want to setup to use our Citrix server are unable to connect, the Citrix server can't grant them a connection license. People who have been using this TS server up until now are unaffected, they can logon and work no problem, only new clients who have never connected before are affected.
I tried to open the license loggin for TS on the citrix server, (which has the license logging component installed, but the service won't start). I installed license loggin on our new 2003 AD domain controller, but it can't see our Citrix TS server for some reason, I get a "cannot connect to license logging server" error when I try to connect to our citrix server.
I've read that the license logging service can only be run on a domain controller, is that true, and if so, now that my domain is in 2003 interim mode and our Terminal server is running Windows 2000 (member server), how can I get terminal services licensing to work? I can't make a 2000 server a DC because of the mode our domain is in. This was never an issue in our NT4 domain. Can someone help me figure this out and give me some options?