834651 - Terminal Services licensing mode changes from Per..

Archived from groups: microsoft.public.windowsnt.terminalserver.connectivity (More info?)

I ran into this bug today, at least that's what I think because the registry
key involved was set to 0. Is it sufficient to change te registry key or
should I run the hotfix as well? And if so can this fix be downloaded
directly or do I need to call in Microsoft support?

Archived from groups: microsoft.public.windowsnt.terminalserver.connectivity (More info?)

I installed SP1 and set the registry key to 4, no warnings about expiring
licensing anymore now. However our TS licensing server gives a not
applicable remark in the 'per user cal token' entry. Is this by design or
should I reactivate the licensing server?
"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> schreef in bericht
news:Xns9667EFBD816F6veranoesthemutforsse@207.46.248.16...
> I'd get the hotfix, because this problem can occur again, everytime
> you use the Windows Component Wizard.
>
> And as with nearly all hotfixes, you'll have to phone Microsoft to
> get it. It's included in SP1, though.
>
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> http://hem.fyristorg.com/vera/IT
> ___ please respond in newsgroup, NOT by private email ___
>
> "b.binnenweg" <barry@nospam.binnenweg.demon.nl> wrote on 31 maj
> 2005 in microsoft.public.windowsnt.terminalserver.connectivity:
>
>> I ran into this bug today, at least that's what I think because
>> the registry key involved was set to 0. Is it sufficient to
>> change te registry key or should I run the hotfix as well? And
>> if so can this fix be downloaded directly or do I need to call
>> in Microsoft support?