Recently we have purchased a new server - Server A (Windows Server 2003) mainly for TS Access. We have another TS server - Server B (Windows Server 2000) being used for another factory's users. I found out only Server B's TS licensing can be managed by our Domain Controller (act as a TS Licensing Server). So the Server A now is having the license expired problem. Anyone here have idea to solve it? Should i propose to management to purchase a new server (HP DL320) with Windows Server 2003 to act as a Licensing Server to manage the Server A and Server B together to reduce the traffic to the Domain Controller? Or can i just ignore this problem by converting the Server A TS access method from "Per Device" to "Per User"? Any illegal issue? Compared to above solution, which is better?

With Windows 2003, the licensing server can be on the same server you are using as a terminal server. I believe with 2000 you had to have the TS and licensing server on two different servers. How about upgrading the 2000 server to 2003, then both servers can run as their own licensing server.

A Windows 2003 Terminal server must get licenses from a license service running on a Windows 2003 Server. If your terminal license server is installed on a Windows 2000 domain controller and you are no planning to upgrade your domain controller to 2003 in the near future. It is best to install it on a dedicated server. The easier approach is to install on a low end box, register all your licenses, and take a ghost image of the server and store the image on somewhere safe for recovery purpose. It your TS server(s) are on separate subnets, you can edit the registry key to point all your TS server to the dedicate the license server. Hope this helps.