Maybe you didn't perform the LS installation using an Enterprise
Admin account?
I don't know if I would bother publishing the LS in AD, you could
just as easy create a policy to point the TS to the LS.
But sure, it can be done. Here's all the info you need:
Manually Publishing and Un-publishing Terminal Server License
Servers
http://blogs.msdn.com/ts/archive/2007/02/27/manually-publishing-
and-un-publishing-terminal-server-license-servers.aspx
270898 - Permissions Required to Install a Terminal Services
Enterprise License Server
http://support.microsoft.com/?kbid=270898
895151 - Windows Server 2003-based or Windows 2000-based terminal
servers do not automatically discover a license server that is
designated as an enterprise license server
http://support.microsoft.com/?kbid=895151
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting:
http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
=?Utf-8?B?QkZI?= <BFH@discussions.microsoft.com> wrote on 16 jul
2007 in microsoft.public.windows.terminal_services:
> That seems very clear, however, it prompts a couple of
> questions: any idea what I might have done wrong in installing
> the License Server so that it's not an Enterprise LS? It's the
> only one in our single-forest single-domain native Win2003 AD
> domain - isn't in the default behaviour for it to be registered
> as the Enterprise LS or Domain LS?
>
> Secondly, can I fix it now, register it as the Enterprise LS in
> AD?
>
> Thanks,
> BFH
>
> "Vera Noest [MVP]" wrote:
>
>> This is the default behaviour. Your LS would be discovered
>> automatically if it was installed as an Enterprise LS (and thus
>> registered in AD as such), and also if it was installed as
>> Domain LS and running on your DC. That's why you see the TS
>> contact the DC and then fail to find an LS. A Domain LS running
>> on a member server is not automatically discovered.
>>
>> Documented here:
>>
>> 301932 - Terminal Services Licensing service discovery
>> http://support.microsoft.com/?kbid=301932
>>
>> You can override the default discovery method by specifying a
>> preferred LS:
>>
>> 279561 - How to Override the License Server Discovery Process
>> in Windows Server 2003 Terminal Services
>> http://support.microsoft.com/?kbid=279561
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> =?Utf-8?B?QkZI?= <BFH@discussions.microsoft.com> wrote on 03
>> jul 2007 in microsoft.public.windows.terminal_services:
>>
>> > Setup is: two terminal servers, one licensing server (all
>> > 2003).
>> > The licensing server has the TS Manager (licmgr.exe)
>> > installed
>> > on it. When I start TS manager, it says it's looking for a
>> > licening server, I see it trying (and failing) to connect to
>> > a particular DC, and then it tells me no license server is
>> > available in the current domain or workgroup.
>> >
>> > This is, of course, nonsense- all the server are part of the
>> > same domain, and the license server service is actually
>> > running on the server that tells me it can't find the
>> > service!
>> >
>> > So, then I right-click, connect to license service on the
>> > local server, and I see all the licenses, etc. All's well
>> > from that point, but it bugs me that I have to do the exact
>> > nosing around (not to mention wait for the first attempt to
>> > time out). Is there any way (command line option, maybe, or
>> > reg hack) to tell licmgr.exe where to look for the server
>> > right away?