Windows NT TS Licence Server message

  • Thread starter Thread starter =?Utf-8?B?VG9tbXlE?=
  • Start date Start date
?

=?Utf-8?B?VG9tbXlE?=

Hi,
I get a message: “No Terminal Server licence server is available …†every
time I start Terminal Server Licensing. I only have one server in my domain,
Windows 2003 TS which also is a DC and TS Licence Server. I know this is not
the recommend solution, but shouldn’t it work?

I can connect manually to the Licence Server and verify that it is activated.

Why doesn’t it connect to the Licence Server automatically? Will this
situation cause problem for me when the first 120 days has passed?

Thanks!
Tommy
 
Yes, it should.
Does the LS issue temporary licenses to connecting clients?
Have you run lsview from the Resource Kit?
Are you logging in on the server with an Domain Administrator
account?
Is the LS installed as Enterprise or as Domain LS?
If Enterprise, did you use an Enterprise Administrator account
during installation? Have you checked the entry for the Enterprise
LS in AD?
LDAP://CN=TS-Enterprise-License-Server,CN=site-
name,CN=sites,CN=configuration,DC=domainname,DC=com
Have you checked the DNS entry for 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?VG9tbXlE?= <TommyD@discussions.microsoft.com> wrote on
25 aug 2007 in microsoft.public.windows.terminal_services:

> Hi,
> I get a message: “No Terminal Server licence server is
> available …†every time I start Terminal Server Licensing. I
> only have one server in my domain, Windows 2003 TS which also is
> a DC and TS Licence Server. I know this is not the recommend
> solution, but shouldn’t it work?
>
> I can connect manually to the Licence Server and verify that it
> is activated.
>
> Why doesn’t it connect to the Licence Server automatically?
> Will this situation cause problem for me when the first 120 days
> has passed?
>
> Thanks!
> Tommy
 
It only issues temporary licenses. The User CAL licences that are installed
says “Not applicabledâ€.

When I run lsview no “Machine†is displayed.

Now I am logging in with a Domain Admin account, didn't help. I was only
Local administrator when I installed the LS.

It is installed as Domain LS.

/Tommy

"Vera Noest [MVP]" wrote:

> Yes, it should.
> Does the LS issue temporary licenses to connecting clients?
> Have you run lsview from the Resource Kit?
> Are you logging in on the server with an Domain Administrator
> account?
> Is the LS installed as Enterprise or as Domain LS?
> If Enterprise, did you use an Enterprise Administrator account
> during installation? Have you checked the entry for the Enterprise
> LS in AD?
> LDAP://CN=TS-Enterprise-License-Server,CN=site-
> name,CN=sites,CN=configuration,DC=domainname,DC=com
> Have you checked the DNS entry for 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?VG9tbXlE?= <TommyD@discussions.microsoft.com> wrote on
> 25 aug 2007 in microsoft.public.windows.terminal_services:
>
> > Hi,
> > I get a message: “No Terminal Server licence server is
> > available …†every time I start Terminal Server Licensing. I
> > only have one server in my domain, Windows 2003 TS which also is
> > a DC and TS Licence Server. I know this is not the recommend
> > solution, but shouldn’t it work?
> >
> > I can connect manually to the Licence Server and verify that it
> > is activated.
> >
> > Why doesn’t it connect to the Licence Server automatically?
> > Will this situation cause problem for me when the first 120 days
> > has passed?
> >
> > Thanks!
> > Tommy

>
 
Problem solved. DNS problem (as you suggested). Thanks Vera!

Regards
Tommy

"TommyD" wrote:

> It only issues temporary licenses. The User CAL licences that are installed
> says “Not applicabledâ€.
>
> When I run lsview no “Machine†is displayed.
>
> Now I am logging in with a Domain Admin account, didn't help. I was only
> Local administrator when I installed the LS.
>
> It is installed as Domain LS.
>
> /Tommy
>
> "Vera Noest [MVP]" wrote:
>
> > Yes, it should.
> > Does the LS issue temporary licenses to connecting clients?
> > Have you run lsview from the Resource Kit?
> > Are you logging in on the server with an Domain Administrator
> > account?
> > Is the LS installed as Enterprise or as Domain LS?
> > If Enterprise, did you use an Enterprise Administrator account
> > during installation? Have you checked the entry for the Enterprise
> > LS in AD?
> > LDAP://CN=TS-Enterprise-License-Server,CN=site-
> > name,CN=sites,CN=configuration,DC=domainname,DC=com
> > Have you checked the DNS entry for 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?VG9tbXlE?= <TommyD@discussions.microsoft.com> wrote on
> > 25 aug 2007 in microsoft.public.windows.terminal_services:
> >
> > > Hi,
> > > I get a message: “No Terminal Server licence server is
> > > available …†every time I start Terminal Server Licensing. I
> > > only have one server in my domain, Windows 2003 TS which also is
> > > a DC and TS Licence Server. I know this is not the recommend
> > > solution, but shouldn’t it work?
> > >
> > > I can connect manually to the Licence Server and verify that it
> > > is activated.
> > >
> > > Why doesn’t it connect to the Licence Server automatically?
> > > Will this situation cause problem for me when the first 120 days
> > > has passed?
> > >
> > > Thanks!
> > > Tommy

> >
 
OK, I'm glad that your LS discovery problem is solved, but you have
another one :-)
You mention that you have installed Per User licenses, but the
server is issueing temporary licenses (which are Per Device,
correct?).
That means that your Terminal Server is still running in the
default Per Device licensing mode. You have to change that, in
Terminal Services Configuration - server settings.
Note that Per User licenses are currently unmanaged, so they will
always be listed as N/A.

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

> Problem solved. DNS problem (as you suggested). Thanks Vera!
>
> Regards
> Tommy
>
> "TommyD" wrote:
>
>> It only issues temporary licenses. The User CAL licences that
>> are installed says “Not applicabledâ€.
>>
>> When I run lsview no “Machine†is displayed.
>>
>> Now I am logging in with a Domain Admin account, didn't help. I
>> was only Local administrator when I installed the LS.
>>
>> It is installed as Domain LS.
>>
>> /Tommy
>>
>> "Vera Noest [MVP]" wrote:
>>
>> > Yes, it should.
>> > Does the LS issue temporary licenses to connecting clients?
>> > Have you run lsview from the Resource Kit?
>> > Are you logging in on the server with an Domain Administrator
>> > account?
>> > Is the LS installed as Enterprise or as Domain LS?
>> > If Enterprise, did you use an Enterprise Administrator
>> > account during installation? Have you checked the entry for
>> > the Enterprise LS in AD?
>> > LDAP://CN=TS-Enterprise-License-Server,CN=site-
>> > name,CN=sites,CN=configuration,DC=domainname,DC=com
>> > Have you checked the DNS entry for 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?VG9tbXlE?= <TommyD@discussions.microsoft.com> wrote
>> > on 25 aug 2007 in microsoft.public.windows.terminal_services:
>> >
>> > > Hi,
>> > > I get a message: “No Terminal Server licence server
>> > > is available …†every time I start Terminal
>> > > Server Licensing. I only have one server in my domain,
>> > > Windows 2003 TS which also is a DC and TS Licence Server. I
>> > > know this is not the recommend solution, but
>> > > shouldn’t it work?
>> > >
>> > > I can connect manually to the Licence Server and verify
>> > > that it is activated.
>> > >
>> > > Why doesn’t it connect to the Licence Server
>> > > automatically? Will this situation cause problem for me
>> > > when the first 120 days has passed?
>> > >
>> > > Thanks!
>> > > Tommy
 
Only one temporary license (Per Device) is issued and it was issued before I
installed the User licenses.

When looking at Per User CAL token it says Total = 5, Availible = 5.
Shouldn't there be a count down when users are connecting?
How can I verify that Per User licensing is working properly?

/Tommy

"Vera Noest [MVP]" wrote:

> OK, I'm glad that your LS discovery problem is solved, but you have
> another one :-)
> You mention that you have installed Per User licenses, but the
> server is issueing temporary licenses (which are Per Device,
> correct?).
> That means that your Terminal Server is still running in the
> default Per Device licensing mode. You have to change that, in
> Terminal Services Configuration - server settings.
> Note that Per User licenses are currently unmanaged, so they will
> always be listed as N/A.
>
> _________________________________________________________
> 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?VG9tbXlE?= <TommyD@discussions.microsoft.com> wrote on
> 26 aug 2007 in microsoft.public.windows.terminal_services:
>
> > Problem solved. DNS problem (as you suggested). Thanks Vera!
> >
> > Regards
> > Tommy
> >
> > "TommyD" wrote:
> >
> >> It only issues temporary licenses. The User CAL licences that
> >> are installed says “Not applicabledâ€Â.
> >>
> >> When I run lsview no “Machine†is displayed.
> >>
> >> Now I am logging in with a Domain Admin account, didn't help. I
> >> was only Local administrator when I installed the LS.
> >>
> >> It is installed as Domain LS.
> >>
> >> /Tommy
> >>
> >> "Vera Noest [MVP]" wrote:
> >>
> >> > Yes, it should.
> >> > Does the LS issue temporary licenses to connecting clients?
> >> > Have you run lsview from the Resource Kit?
> >> > Are you logging in on the server with an Domain Administrator
> >> > account?
> >> > Is the LS installed as Enterprise or as Domain LS?
> >> > If Enterprise, did you use an Enterprise Administrator
> >> > account during installation? Have you checked the entry for
> >> > the Enterprise LS in AD?
> >> > LDAP://CN=TS-Enterprise-License-Server,CN=site-
> >> > name,CN=sites,CN=configuration,DC=domainname,DC=com
> >> > Have you checked the DNS entry for 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?VG9tbXlE?= <TommyD@discussions.microsoft.com> wrote
> >> > on 25 aug 2007 in microsoft.public.windows.terminal_services:
> >> >
> >> > > Hi,
> >> > > I get a message: “No Terminal Server licence server
> >> > > is available …†every time I start Terminal
> >> > > Server Licensing. I only have one server in my domain,
> >> > > Windows 2003 TS which also is a DC and TS Licence Server. I
> >> > > know this is not the recommend solution, but
> >> > > shouldn’t it work?
> >> > >
> >> > > I can connect manually to the Licence Server and verify
> >> > > that it is activated.
> >> > >
> >> > > Why doesn’t it connect to the Licence Server
> >> > > automatically? Will this situation cause problem for me
> >> > > when the first 120 days has passed?
> >> > >
> >> > > Thanks!
> >> > > Tommy

>
 
No, that's what I meant with "unmanaged". Per User licenses are
actually never issued, so the Total and Available counters will
stay what they are.
Documented here:
822134 - The Function of Terminal Server CALs in Windows Server
2003
http://support.microsoft.com/?kbid=822134

But as long as your TS is configured to use Per User licenses and
you do *not* see any more temporary Per Device licenses issued,
then everthing is working as it should.
You'll have to keep track of the number of connecting users in some
other way, to be sure that you are compliant with the EULA. That's
easiest done by making sure that only 5 user accounts are members
of the Remote Desktop Users group on the TS.
_________________________________________________________
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?VG9tbXlE?= <TommyD@discussions.microsoft.com> wrote on
26 aug 2007 in microsoft.public.windows.terminal_services:

> Only one temporary license (Per Device) is issued and it was
> issued before I installed the User licenses.
>
> When looking at Per User CAL token it says Total = 5, Availible
> = 5. Shouldn't there be a count down when users are connecting?
> How can I verify that Per User licensing is working properly?
>
> /Tommy
>
> "Vera Noest [MVP]" wrote:
>
>> OK, I'm glad that your LS discovery problem is solved, but you
>> have another one :-)
>> You mention that you have installed Per User licenses, but the
>> server is issueing temporary licenses (which are Per Device,
>> correct?).
>> That means that your Terminal Server is still running in the
>> default Per Device licensing mode. You have to change that, in
>> Terminal Services Configuration - server settings.
>> Note that Per User licenses are currently unmanaged, so they
>> will always be listed as N/A.
>>
>> _________________________________________________________
>> 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?VG9tbXlE?= <TommyD@discussions.microsoft.com> wrote
>> on 26 aug 2007 in microsoft.public.windows.terminal_services:
>>
>> > Problem solved. DNS problem (as you suggested). Thanks Vera!
>> >
>> > Regards
>> > Tommy
>> >
>> > "TommyD" wrote:
>> >
>> >> It only issues temporary licenses. The User CAL licences
>> >> that are installed says “Not applicabledâ€Â.
>> >>
>> >> When I run lsview no “Machine†is displayed.
>> >>
>> >> Now I am logging in with a Domain Admin account, didn't
>> >> help. I was only Local administrator when I installed the
>> >> LS.
>> >>
>> >> It is installed as Domain LS.
>> >>
>> >> /Tommy
>> >>
>> >> "Vera Noest [MVP]" wrote:
>> >>
>> >> > Yes, it should.
>> >> > Does the LS issue temporary licenses to connecting
>> >> > clients? Have you run lsview from the Resource Kit?
>> >> > Are you logging in on the server with an Domain
>> >> > Administrator account?
>> >> > Is the LS installed as Enterprise or as Domain LS?
>> >> > If Enterprise, did you use an Enterprise Administrator
>> >> > account during installation? Have you checked the entry
>> >> > for the Enterprise LS in AD?
>> >> > LDAP://CN=TS-Enterprise-License-Server,CN=site-
>> >> > name,CN=sites,CN=configuration,DC=domainname,DC=com
>> >> > Have you checked the DNS entry for 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?VG9tbXlE?= <TommyD@discussions.microsoft.com>
>> >> > wrote on 25 aug 2007 in
>> >> > microsoft.public.windows.terminal_services:
>> >> >
>> >> > > Hi,
>> >> > > I get a message: “No Terminal Server
>> >> > > licence server is available
>> >> > > …†every time I start
>> >> > > Terminal Server Licensing. I only have one server in my
>> >> > > domain, Windows 2003 TS which also is a DC and TS
>> >> > > Licence Server. I know this is not the recommend
>> >> > > solution, but shouldn’t it work?
>> >> > >
>> >> > > I can connect manually to the Licence Server and verify
>> >> > > that it is activated.
>> >> > >
>> >> > > Why doesn’t it connect to the Licence
>> >> > > Server automatically? Will this situation cause problem
>> >> > > for me when the first 120 days has passed?
>> >> > >
>> >> > > Thanks!
>> >> > > Tommy
 
Back
Top