Re: Licensing
It's not so strange that your 2008 LS has only issued 9 licenses.
You recently moved LS, right? So most clients still have a valid
license.
The warning about the autodiscovery is correct, but if you set the
prefferred LS on the 2003 TS, you don't need (and actually
override) autodiscovery, so that's no problem either.
If you're not using the LS on the 2003 server anymore and you have
moved your licenses, you should uninstall the TS Licensing Sevices
from it.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting:
http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
RandyH <RHollaw@HOTmail.com> wrote on 06 aug 2008 in
microsoft.public.windows.terminal_services:
> on the 2008 server I ran the report and it's issuing licenses,
> but only 9 have been issued..we have 100 TS users.
>
> in the TS licensing console, the 2008 server has a ! triangle.
> Right mouse, Review configuration - says, This License Server is
> not installed on a domain controller. Terminal servers in the
> domain will not be able to automatically discover this license
> server - that's why I asked about
> the DC requirement.
>
> My most recent event on the 2003 TS from licensing: 7/31
> Terminal Server Licensing on server ***** has not been
> activated. Terminal Server Licensing will only issue temporary
> licenses until the server is activated.
> See Terminal Server Licensing help topic for more information.
>
> On 5/29 I see this:
> Regenerate public/private key by client ncacn_np:172.16.x.x.
>
> Vera Noest [MVP] wrote:
>> Aaah, but I'm not sure that you can *manage* the 2008 TS
>> Licensing Server from a 2003 server.
>> Open the TS Licensing Manager on the 2008 server to see if it
>> is issueing licenses to the clients which connect to the 2003
>> TS.
>>
>> And check the EventLog on the 2003 TS for more information.
>>
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> RandyH <RHollaw@HOTmail.com> wrote on 06 aug 2008 in
>> microsoft.public.windows.terminal_services:
>>
>>> thank you Vera.
>>>
>>> from the 2003 TS, TS configuration, Server settings -
>>> Licensing Server, it's set to Automatic, and below under,
>>> Automatically discovered license servers, my 2008 TS server is
>>> listed in the, In Enterprise Mode.
>>>
>>> If I open Terminal Server Licensing, I msg appears, no
>>> Terminal Server license server is available in the current
>>> domain or workgroup. To connect . . .etc . ..etc...
>>>
>>> I choose connect, type in my servername and says, "windows
>>> cannot connect to a licensing server.
>>>
>>> thanks again Vera...god bless you!
>>>
>>> Vera Noest [MVP] wrote:
>>>> No, it doesn't have to be a domain controller. But you must
>>>> make sure that the 2003 TS can detect your new 2008 TS
>>>> Licensing Server. Easiest is to start Terminal Services
>>>> Configuration - Server settings - Licensing Server.
>>>>
>>>> _________________________________________________________
>>>> Vera Noest
>>>> MCSE, CCEA, Microsoft MVP - Terminal Server
>>>> TS troubleshooting: http://ts.veranoest.net
>>>> ___ please respond in newsgroup, NOT by private email ___
>>>>
>>>> RandyH <RHollaw@HOTmail.com> wrote on 06 aug 2008 in
>>>> microsoft.public.windows.terminal_services:
>>>>
>>>>> I'm confused...
>>>>>
>>>>> Does the TS licensing server need to be on a domain
>>>>> controller?
>>>>>
>>>>> I have a 2003 TS where I have the licenses installed.
>>>>>
>>>>> Recently we deployed a 2008 TS published apps.
>>>>>
>>>>> my boss told me to move the licenses to that 2008 member
>>>>> server.
>>>>>
>>>>> Since then my 2003 TS cannot see a TS Licensing server and
>>>>> says its under the grace period again, BAH!
>>>>>
>>>>> Do I need a 2008 domain controller to host the TS Licenses?
>>>>> and then the
>>>>> 2003 TS will "see" the licensing server?
>>>>>
>>>>> Any help, thank you so much,
>>>>> RandyH