Archived from groups: microsoft.public.windowsnt.terminalserver.connectivity (
More info?)
No, I don't know. And if I knew, I wouldn't be allowed to disclose
it.
_________________________________________________________
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?UmF5IFdoaXRl?= <Ray White@discussions.microsoft.com>
wrote on 06 aug 2005 in
microsoft.public.windowsnt.terminalserver.connectivity:
> Any idea when MS will start decrementing TS User CAL's?
>
> "Vera Noest [MVP]" wrote:
>
>> That's by design.
>> Check this article, it explains that even after you have
>> switched licensing mode on the TS, your Per User TS CAL count
>> will not be decremented:
>>
>> 822134 - The Function of Terminal Server CALs in Windows Server
>> 2003
>>
http://support.microsoft.com/?kbid=822134
>>
>> --
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>>
http://hem.fyristorg.com/vera/IT
>> --- please respond in newsgroup, NOT by private email ---
>>
>> "silvan" <sjappert@ziptrack.com> wrote on 20 jan 2005 in
>> microsoft.public.windowsnt.terminalserver.connectivity:
>>
>> > Both the Terminal Server and Terminal Server Lisence
>> > configurations are set to Per User lisensing, I changed this
>> > a while back but still see 10 lisences available and 0 issued
>> > when I open up the Terminal server lisence window.
>> >
>> >
>> > "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se>
>> > wrote in message
>> > news:Xns95E3EAD6BC9BEveranoesthemutforsse@207.46.248.16...
>> >> No, it probably won't!
>> >> Is the Terminal Server set to use "Per User" licensing? The
>> >> default is "Per Device".
>> >> You can check this from Administrative Tools - Terminal
>> >> Services Configuration - Server Settings
>> >> If it's set to Per Device mode, it will look for a Device TS
>> >> CAL and will not issue your Per User TS CALs.
>> >>
>> >> About the "not recommended" part of your first post: it is
>> >> no problem at all to run the Licensing Service on the same
>> >> server as the Terminal Service.
>> >> BUT: it is *not* recommended to run Terminal Services on
>> >> your Domain Controller. This is both a security and a
>> >> performance risk. Realize that you now have users running
>> >> interactively on your Domain Controller, using it as their
>> >> personal workstation!
>> >>
>> >> If some non-TS compatible application crashes the server,
>> >> your whole AD might go down.
>> >>
>> >> --
>> >> Vera Noest
>> >> MCSE, CCEA, Microsoft MVP - Terminal Server
>> >>
http://hem.fyristorg.com/vera/IT
>> >> --- please respond in newsgroup, NOT by private email ---
>> >>
>> >> "silvan" <sjappert@ziptrack.com> wrote on 19 jan 2005 in
>> >> microsoft.public.windowsnt.terminalserver.connectivity:
>> >>
>> >>> I did some reading and I think I might be alright. I
>> >>> didn't know that Per User CAL's were unmanaged so hopefully
>> >>> everything will go fine when temporary lisence expire
>> >>>
>> >>> "silvan" <sjappert@ziptrack.com> wrote in message
>> >>> news:BOCdnTVccPpAEXPcRVn-sQ@magma.ca...
>> >>>> Hi,
>> >>>>
>> >>>> I have terminal server running on my win2k3 server. This
>> >>>> is the PDC which also has AD, DHCP and DNS running on it.
>> >>>> I have had no problems using Terminal Server with the
>> >>>> temoporary lisences so far. However these are expiring
>> >>>> very soon. i've purchased a 10 user or computer lisence
>> >>>> package and installed the terminal server lisence server
>> >>>> on the same server as terminal server. I did read that
>> >>>> this is not recommended, but it did not state it was
>> >>>> mandatory to install the lisence server on a different
>> >>>> machine. I've added the users that I want to issue the
>> >>>> lisences to the Terminal Server Lisence group in AD but
>> >>>> they continue to use the temporary lisence. Will these
>> >>>> users simply switch over to the purchased lisences once
>> >>>> the temporary ones expire? Or am i missing something to
>> >>>> assign the lisences properly? Thanks for your help.
Facebook
Twitter
Instagram