Windows NT Terminal Server Licensing Issue

  • Thread starter Thread starter DanC
  • Start date Start date
D

DanC

I have setup a new TS for our sales staff and we purchased 15 Per-device
Cals. I installed the licenses by first installing a batch of 10 and later
adding 5 more. I noticed a few days later that each device that I use to
connect to our terminal server using remote desktop takes one available
license. I have remoted in personally from 3 machines and each machine took
one license leaving me with 12 instead of 15 for our sales staff. I also
noticed that our terminal server is taking one of the 15 licenses so that
leaves me with 11.
I was told that this problem might be caused by remoting into the terminal
server with Windows XP but two if the machines that I have used are running
Vista Ultimate and the terminal server that is taking a license is running
Windows 2003 std (32bit)

As I said all of the licensing has been per device

I also am unable to connect a new terminal and take advantage of the
temporary licensing (90days) that I thought was available.

Is there something about the per-device cal that makes these temporary
licenses unavailable?

Any ideas would be appreciated.
 
The License Server only issues temporary licenses when no permanent licenses
are available. Thus the first fifteen devices to connect will take the 15
CALs.

The good news is that if you stop using these other machines to connect,
they will return their licenses back to the pool, and your sales staff will
be able to take them. There should be no delay in connectivity.

Rob

"DanC" <DanC@discussions.microsoft.com> wrote in message
news:70902084-E437-481F-9DBE-BD8A2FA80643@microsoft.com...
>I have setup a new TS for our sales staff and we purchased 15 Per-device
> Cals. I installed the licenses by first installing a batch of 10 and later
> adding 5 more. I noticed a few days later that each device that I use to
> connect to our terminal server using remote desktop takes one available
> license. I have remoted in personally from 3 machines and each machine
> took
> one license leaving me with 12 instead of 15 for our sales staff. I also
> noticed that our terminal server is taking one of the 15 licenses so that
> leaves me with 11.
> I was told that this problem might be caused by remoting into the terminal
> server with Windows XP but two if the machines that I have used are
> running
> Vista Ultimate and the terminal server that is taking a license is running
> Windows 2003 std (32bit)
>
> As I said all of the licensing has been per device
>
> I also am unable to connect a new terminal and take advantage of the
> temporary licensing (90days) that I thought was available.
>
> Is there something about the per-device cal that makes these temporary
> licenses unavailable?
>
> Any ideas would be appreciated.
>
 
I appreciate your quick response.

I am still wondering why the terminal server itself is taking a license and
why the three machines that I used to remote into are taking licenses. Can't
I (as an administrator) remote into the TS with my computer w/o a license
being used?
And why is the terminal server itself using a license. I never remoted into
the machine from that same machine.



"Rob Leitman [MS]" wrote:

> The License Server only issues temporary licenses when no permanent licenses
> are available. Thus the first fifteen devices to connect will take the 15
> CALs.
>
> The good news is that if you stop using these other machines to connect,
> they will return their licenses back to the pool, and your sales staff will
> be able to take them. There should be no delay in connectivity.
>
> Rob
>
> "DanC" <DanC@discussions.microsoft.com> wrote in message
> news:70902084-E437-481F-9DBE-BD8A2FA80643@microsoft.com...
> >I have setup a new TS for our sales staff and we purchased 15 Per-device
> > Cals. I installed the licenses by first installing a batch of 10 and later
> > adding 5 more. I noticed a few days later that each device that I use to
> > connect to our terminal server using remote desktop takes one available
> > license. I have remoted in personally from 3 machines and each machine
> > took
> > one license leaving me with 12 instead of 15 for our sales staff. I also
> > noticed that our terminal server is taking one of the 15 licenses so that
> > leaves me with 11.
> > I was told that this problem might be caused by remoting into the terminal
> > server with Windows XP but two if the machines that I have used are
> > running
> > Vista Ultimate and the terminal server that is taking a license is running
> > Windows 2003 std (32bit)
> >
> > As I said all of the licensing has been per device
> >
> > I also am unable to connect a new terminal and take advantage of the
> > temporary licensing (90days) that I thought was available.
> >
> > Is there something about the per-device cal that makes these temporary
> > licenses unavailable?
> >
> > Any ideas would be appreciated.
> >
>
>
 
When you install Terminal Services (implying in Application mode),
*all* connections, including your's, need a TS CAL.
It's simply impossible for the licensing system to know if you are
going to perform remote administration, or reading your email.
But there's one way around this: when you connect to the server
with a console session, you don't take a license.
Console connections are made with "mstsc /console" (without the
quotes).

I don't know why the TS itself takes a license (I see it on all of
my servers as well, but then I remotely connect from one server to
the other, with rdp over rdp).

Even if all of your 15 TS CALs are issued, you should be able to
connect with temporary licenses from new clients. If that doesn't
work, check the eventLog on the TS to find the reason. Are these
thin clients?
_________________________________________________________
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?RGFuQw==?= <DanC@discussions.microsoft.com> wrote on 13
aug 2007 in microsoft.public.windows.terminal_services:

> I appreciate your quick response.
>
> I am still wondering why the terminal server itself is taking a
> license and why the three machines that I used to remote into
> are taking licenses. Can't I (as an administrator) remote into
> the TS with my computer w/o a license being used?
> And why is the terminal server itself using a license. I never
> remoted into the machine from that same machine.
>
>
>
> "Rob Leitman [MS]" wrote:
>
>> The License Server only issues temporary licenses when no
>> permanent licenses are available. Thus the first fifteen
>> devices to connect will take the 15 CALs.
>>
>> The good news is that if you stop using these other machines to
>> connect, they will return their licenses back to the pool, and
>> your sales staff will be able to take them. There should be no
>> delay in connectivity.
>>
>> Rob
>>
>> "DanC" <DanC@discussions.microsoft.com> wrote in message
>> news:70902084-E437-481F-9DBE-BD8A2FA80643@microsoft.com...
>> >I have setup a new TS for our sales staff and we purchased 15
>> >Per-device
>> > Cals. I installed the licenses by first installing a batch of
>> > 10 and later adding 5 more. I noticed a few days later that
>> > each device that I use to connect to our terminal server
>> > using remote desktop takes one available license. I have
>> > remoted in personally from 3 machines and each machine took
>> > one license leaving me with 12 instead of 15 for our sales
>> > staff. I also noticed that our terminal server is taking one
>> > of the 15 licenses so that leaves me with 11.
>> > I was told that this problem might be caused by remoting into
>> > the terminal server with Windows XP but two if the machines
>> > that I have used are running
>> > Vista Ultimate and the terminal server that is taking a
>> > license is running Windows 2003 std (32bit)
>> >
>> > As I said all of the licensing has been per device
>> >
>> > I also am unable to connect a new terminal and take advantage
>> > of the temporary licensing (90days) that I thought was
>> > available.
>> >
>> > Is there something about the per-device cal that makes these
>> > temporary licenses unavailable?
>> >
>> > Any ideas would be appreciated.
 
Yes they are thin clients. Why do you ask?
I will check the eventlog
Thanks

"Vera Noest [MVP]" wrote:

> When you install Terminal Services (implying in Application mode),
> *all* connections, including your's, need a TS CAL.
> It's simply impossible for the licensing system to know if you are
> going to perform remote administration, or reading your email.
> But there's one way around this: when you connect to the server
> with a console session, you don't take a license.
> Console connections are made with "mstsc /console" (without the
> quotes).
>
> I don't know why the TS itself takes a license (I see it on all of
> my servers as well, but then I remotely connect from one server to
> the other, with rdp over rdp).
>
> Even if all of your 15 TS CALs are issued, you should be able to
> connect with temporary licenses from new clients. If that doesn't
> work, check the eventLog on the TS to find the reason. Are these
> thin clients?
> _________________________________________________________
> 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?RGFuQw==?= <DanC@discussions.microsoft.com> wrote on 13
> aug 2007 in microsoft.public.windows.terminal_services:
>
> > I appreciate your quick response.
> >
> > I am still wondering why the terminal server itself is taking a
> > license and why the three machines that I used to remote into
> > are taking licenses. Can't I (as an administrator) remote into
> > the TS with my computer w/o a license being used?
> > And why is the terminal server itself using a license. I never
> > remoted into the machine from that same machine.
> >
> >
> >
> > "Rob Leitman [MS]" wrote:
> >
> >> The License Server only issues temporary licenses when no
> >> permanent licenses are available. Thus the first fifteen
> >> devices to connect will take the 15 CALs.
> >>
> >> The good news is that if you stop using these other machines to
> >> connect, they will return their licenses back to the pool, and
> >> your sales staff will be able to take them. There should be no
> >> delay in connectivity.
> >>
> >> Rob
> >>
> >> "DanC" <DanC@discussions.microsoft.com> wrote in message
> >> news:70902084-E437-481F-9DBE-BD8A2FA80643@microsoft.com...
> >> >I have setup a new TS for our sales staff and we purchased 15
> >> >Per-device
> >> > Cals. I installed the licenses by first installing a batch of
> >> > 10 and later adding 5 more. I noticed a few days later that
> >> > each device that I use to connect to our terminal server
> >> > using remote desktop takes one available license. I have
> >> > remoted in personally from 3 machines and each machine took
> >> > one license leaving me with 12 instead of 15 for our sales
> >> > staff. I also noticed that our terminal server is taking one
> >> > of the 15 licenses so that leaves me with 11.
> >> > I was told that this problem might be caused by remoting into
> >> > the terminal server with Windows XP but two if the machines
> >> > that I have used are running
> >> > Vista Ultimate and the terminal server that is taking a
> >> > license is running Windows 2003 std (32bit)
> >> >
> >> > As I said all of the licensing has been per device
> >> >
> >> > I also am unable to connect a new terminal and take advantage
> >> > of the temporary licensing (90days) that I thought was
> >> > available.
> >> >
> >> > Is there something about the per-device cal that makes these
> >> > temporary licenses unavailable?
> >> >
> >> > Any ideas would be appreciated.
>
 
Because - generally speaking - there are more licensing problems
with thin clients than with fat clients. But the usual problem with
thin clients is that they take a new license on every connection,
and that doesn't seem to be your problem.

_________________________________________________________
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?RGFuQw==?= <DanC@discussions.microsoft.com> wrote on 13
aug 2007 in microsoft.public.windows.terminal_services:

> Yes they are thin clients. Why do you ask?
> I will check the eventlog
> Thanks
>
> "Vera Noest [MVP]" wrote:
>
>> When you install Terminal Services (implying in Application
>> mode), *all* connections, including your's, need a TS CAL.
>> It's simply impossible for the licensing system to know if you
>> are going to perform remote administration, or reading your
>> email. But there's one way around this: when you connect to the
>> server with a console session, you don't take a license.
>> Console connections are made with "mstsc /console" (without the
>> quotes).
>>
>> I don't know why the TS itself takes a license (I see it on all
>> of my servers as well, but then I remotely connect from one
>> server to the other, with rdp over rdp).
>>
>> Even if all of your 15 TS CALs are issued, you should be able
>> to connect with temporary licenses from new clients. If that
>> doesn't work, check the eventLog on the TS to find the reason.
>> Are these thin clients?
>> _________________________________________________________
>> 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?RGFuQw==?= <DanC@discussions.microsoft.com> wrote on
>> 13 aug 2007 in microsoft.public.windows.terminal_services:
>>
>> > I appreciate your quick response.
>> >
>> > I am still wondering why the terminal server itself is taking
>> > a license and why the three machines that I used to remote
>> > into are taking licenses. Can't I (as an administrator)
>> > remote into the TS with my computer w/o a license being used?
>> > And why is the terminal server itself using a license. I
>> > never remoted into the machine from that same machine.
>> >
>> >
>> >
>> > "Rob Leitman [MS]" wrote:
>> >
>> >> The License Server only issues temporary licenses when no
>> >> permanent licenses are available. Thus the first fifteen
>> >> devices to connect will take the 15 CALs.
>> >>
>> >> The good news is that if you stop using these other machines
>> >> to connect, they will return their licenses back to the
>> >> pool, and your sales staff will be able to take them. There
>> >> should be no delay in connectivity.
>> >>
>> >> Rob
>> >>
>> >> "DanC" <DanC@discussions.microsoft.com> wrote in message
>> >> news:70902084-E437-481F-9DBE-BD8A2FA80643@microsoft.com...
>> >> >I have setup a new TS for our sales staff and we purchased
>> >> >15 Per-device
>> >> > Cals. I installed the licenses by first installing a batch
>> >> > of 10 and later adding 5 more. I noticed a few days later
>> >> > that each device that I use to connect to our terminal
>> >> > server using remote desktop takes one available license. I
>> >> > have remoted in personally from 3 machines and each
>> >> > machine took one license leaving me with 12 instead of 15
>> >> > for our sales staff. I also noticed that our terminal
>> >> > server is taking one of the 15 licenses so that leaves me
>> >> > with 11. I was told that this problem might be caused by
>> >> > remoting into the terminal server with Windows XP but two
>> >> > if the machines that I have used are running
>> >> > Vista Ultimate and the terminal server that is taking a
>> >> > license is running Windows 2003 std (32bit)
>> >> >
>> >> > As I said all of the licensing has been per device
>> >> >
>> >> > I also am unable to connect a new terminal and take
>> >> > advantage of the temporary licensing (90days) that I
>> >> > thought was available.
>> >> >
>> >> > Is there something about the per-device cal that makes
>> >> > these temporary licenses unavailable?
>> >> >
>> >> > Any ideas would be appreciated.
 
Back
Top