Terminal Servers automatically discover TS License Servers available in a deployment by querying the Active Directory Catalog for a list of license servers. This list is in the "TS-Enterprise-License-Server" object in the Catalog Server. Typically, License Servers in "Enterprise" discovery mode publish themselves to this list during installation. However, this process may go wrong for a variety of reasons, and the publishing step may need to be performed manually. Alternatively, when the discovery mode or deployment location of a License Server changes, it may be necessary to un-publish the LS from the list. In this post, I want to discuss how you can perform these manual operations in Windows Server 2003 License Server.
Manually Publishing a License Server for Enterprise Discovery
Typical problems that cause the failure of publishing the TS License Server are:
In these cases, the License Server may need to be manually published. You may also have to create the TS-Enterprise-License-Server object if it does not yet exist in the Catalog Server.
Publishing a License Server
We can manually publish the Terminal Server License Server, using one of the following two methods,
Using "Active Directory Sites and Services":
Using ADSI Edit tool:
Creating the "TS-Enterprise-License-Server" Object in the Catalog
Manually Un-Publishing a License Server
Typical scenarios that may require manually un-publishing License Server:
In all of these cases, the entry that is left behind in the TS-Enterprise-License-Server object would cause the TS servers to still look for the License Server, even though the LS server may no longer be available or may have moved to a different network. This may lead problems in license discovery and cause the TS servers to not find the type of CAL needed for a particular user. Therefore, it is a good idea to keep the list as current as possible by manually un-publishing a removed License server from the list in the TS-Enterprise-License-Server object.
Un-Publishing a License Server
We can manually Un-Publish Terminal Server License Server using ADSI Edit tool.
Note that the "Active Directory Sites and Services" tool doesn't support removing an entry from a Catalog Server object.
White Paper on Terminal Server License Server is available at http://www.microsoft.com/windowsserver2003/techinfo/overview/termservlic.mspx
*ADSI Tool can be downloaded from
PingBack from http://emailserveronline.com/manually-publishing-and-un-publishing-terminal-server-license-servers/
As far as Load Balancing/Failover is concerned
If there are two Enterprise License Servers installed, how can the second one be published ?
as far as I know, the only way is to put both Licenseservers with FQDN into
on the terminal servers
But how to add the second one into AD ?
License Server are published in "CN= TS-Enterprise-License-Server" object of the Catalog server. This object can contain more than one License Server names.
If both License Server are installed in Enterprise mode, then both of them will be published in AD.
If you wish to Add(Publish) a license server, follow the steps in section "Publishing a License Server"
TS License servers ( 2 ) were installed in domain mode.
Now one of our TS Terminal Server License Servers was removed from the network without decommissioning the TS license service.
When I view Terminal server licenses manager, it tries to read the old server that was removed.
How can I tell the network that the terminal server no longer exists?
The TSLS can be defined in several places, i.e. Active Directory Sites and Services -> Site Name -> TS-Enterprise-License-Server, or via TSCC.MSC on 2003 SP2 (on the TS), via Group Policy or in the registry on the TS.
Citrix Technology Professional
Microsoft MVP - Terminal Server
Provision Networks VIP