Licensing

  • Thread starter Thread starter graham mckenzie
  • Start date Start date
G

graham mckenzie

im having a problem at the momement the terminal server issues temporary
licenses but there has always been proper licences installed i have two types
of cals users and devices the original ones installed were users

now one of my users is only able to connect what seems strange is that in
the licensing section it shows my licenses as non used under the ones i
purchased has any one come across this before

any help would appreciate many thanks
 
Per User licenses are unmanaged (assuming your TS runs Windows
2003), that's why they are listed as N/A and are not issued.
It's unfortunate that you have bought both Per User and Per Device
licenses, because that makes it very complicated for you to know if
you have enough licenses.
Since your users have problem connecting and the LS is issueing
temporary licenses, it is clear that your Terminal server is
configured to use Per Device licenses. You can check that in
Terminal Services Configuration - Server settings.
When the TS is configured in the Per Device licensing mode, it will
not "see" your Per User licenses, and thus only use your Per Device
licenses. Hence your current shortage of licenses.
You will have to change the TS to the Per User licensing mode. Then
it will not "see" your Per Device licenses, and no licenses will be
issued to users whatsoever, but at least they will be able to
connect again.

But as I said, it will be very difficult to calculate how many
licenses you need to stay within the EULA.
_________________________________________________________
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?Z3JhaGFtIG1ja2Vuemll?= <graham
mckenzie@discussions.microsoft.com> wrote on 07 jun 2008 in
microsoft.public.windows.terminal_services:

> im having a problem at the momement the terminal server issues
> temporary licenses but there has always been proper licences
> installed i have two types of cals users and devices the
> original ones installed were users
>
> now one of my users is only able to connect what seems strange
> is that in the licensing section it shows my licenses as non
> used under the ones i purchased has any one come across this
> before
>
> any help would appreciate many thanks
 
thanks for your help it is 2003 server these device licenses i had spare i
can remove these

it was originally installed with per user cals and setup that way and the
config was set to per user cals when you change this setting im assuming it
is advisable to restart the service

but it still said that the user couldnt connect

once again thanks for your help and comments

graham

"Vera Noest [MVP]" wrote:

> Per User licenses are unmanaged (assuming your TS runs Windows
> 2003), that's why they are listed as N/A and are not issued.
> It's unfortunate that you have bought both Per User and Per Device
> licenses, because that makes it very complicated for you to know if
> you have enough licenses.
> Since your users have problem connecting and the LS is issueing
> temporary licenses, it is clear that your Terminal server is
> configured to use Per Device licenses. You can check that in
> Terminal Services Configuration - Server settings.
> When the TS is configured in the Per Device licensing mode, it will
> not "see" your Per User licenses, and thus only use your Per Device
> licenses. Hence your current shortage of licenses.
> You will have to change the TS to the Per User licensing mode. Then
> it will not "see" your Per Device licenses, and no licenses will be
> issued to users whatsoever, but at least they will be able to
> connect again.
>
> But as I said, it will be very difficult to calculate how many
> licenses you need to stay within the EULA.
> _________________________________________________________
> 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?Z3JhaGFtIG1ja2Vuemll?= <graham
> mckenzie@discussions.microsoft.com> wrote on 07 jun 2008 in
> microsoft.public.windows.terminal_services:
>
> > im having a problem at the momement the terminal server issues
> > temporary licenses but there has always been proper licences
> > installed i have two types of cals users and devices the
> > original ones installed were users
> >
> > now one of my users is only able to connect what seems strange
> > is that in the licensing section it shows my licenses as non
> > used under the ones i purchased has any one come across this
> > before
> >
> > any help would appreciate many thanks
>
 
Yes, a restart might be a good idea.
What exactly is the error message that users get when they try to
connect?
Which EventID and Source do you see in the EventLog on the server?

_________________________________________________________
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?Z3JhaGFtIG1ja2Vuemll?=
<grahammckenzie@discussions.microsoft.com> wrote on 07 jun 2008 in
microsoft.public.windows.terminal_services:

> thanks for your help it is 2003 server these device licenses i
> had spare i can remove these
>
> it was originally installed with per user cals and setup that
> way and the config was set to per user cals when you change this
> setting im assuming it is advisable to restart the service
>
> but it still said that the user couldnt connect
>
> once again thanks for your help and comments
>
> graham
>
> "Vera Noest [MVP]" wrote:
>
>> Per User licenses are unmanaged (assuming your TS runs Windows
>> 2003), that's why they are listed as N/A and are not issued.
>> It's unfortunate that you have bought both Per User and Per
>> Device licenses, because that makes it very complicated for you
>> to know if you have enough licenses.
>> Since your users have problem connecting and the LS is issueing
>> temporary licenses, it is clear that your Terminal server is
>> configured to use Per Device licenses. You can check that in
>> Terminal Services Configuration - Server settings.
>> When the TS is configured in the Per Device licensing mode, it
>> will not "see" your Per User licenses, and thus only use your
>> Per Device licenses. Hence your current shortage of licenses.
>> You will have to change the TS to the Per User licensing mode.
>> Then it will not "see" your Per Device licenses, and no
>> licenses will be issued to users whatsoever, but at least they
>> will be able to connect again.
>>
>> But as I said, it will be very difficult to calculate how many
>> licenses you need to stay within the EULA.
>> _________________________________________________________
>> 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?Z3JhaGFtIG1ja2Vuemll?= <graham
>> mckenzie@discussions.microsoft.com> wrote on 07 jun 2008 in
>> microsoft.public.windows.terminal_services:
>>
>> > im having a problem at the momement the terminal server
>> > issues temporary licenses but there has always been proper
>> > licences installed i have two types of cals users and devices
>> > the original ones installed were users
>> >
>> > now one of my users is only able to connect what seems
>> > strange is that in the licensing section it shows my licenses
>> > as non used under the ones i purchased has any one come
>> > across this before
>> >
>> > any help would appreciate many thanks
 
Back
Top