Only one of 2 load balanced servers allows clients to obtain a lic

[blueboy1894]

Okay, I have a bit of a weird situation here.

I recently rebuilt my 2-Server TS NLB Cluster becuase I wanted to re-build
the RAID configurations. All went fine, NLB Cluster is up, along with Session
Directory, and both servers can see the licence server. So far so good.

I also purchased 15 additional CALs to ensure that I didn't run out of
licences - I knew I was sailing close to the wind. So now I have 4 spare
licences from the original CAL pack and another 15, none of which have been
issued yet. So, 19 spare licences.

The Licensing Server is in per device mode, the CALs are all per device CALs
and so are the Terminal Servers (believe me - I've checked, at first I
thought I must have forgotten one and left it in Per-User, but no).

What is happening is that when a license expires, and the device connects to
Server1 I get the message "The remote session was disconnected because there
are no Terminal Server client access licenses available for this computer.
Please contact the server administrator." Strange because this is usually
when per device Terminal Servers are trying to contact a Per-User Licensing
Server.

BUT

If you then immediately connect to Server2 from the same client, the licence
is granted and everything is fine, and you can log onto either server from
the client.

As I said, both TS's can see the Licensing Server (from both TS Licensing
and through lsview.exe) , they're in the same domain and AD Site as the
licensing server, and there's plenty of Licenses.

What's going on???!

 

[Vera Noest [MVP]]

Re: Only one of 2 load balanced servers allows clients to obtain a lic

Anything in the EventLog on Server1?
Are you using a Licensing Server Security Group on the LS?
I understand that the servers run Windows 2003, but which SP are
they running?

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*

=?Utf-8?B?Ymx1ZWJveTE4OTQ=?=
<blueboy1894@discussions.microsoft.com> wrote on 02 okt 2007:

> Okay, I have a bit of a weird situation here.
>
> I recently rebuilt my 2-Server TS NLB Cluster becuase I wanted
> to re-build the RAID configurations. All went fine, NLB Cluster
> is up, along with Session Directory, and both servers can see
> the licence server. So far so good.
>
> I also purchased 15 additional CALs to ensure that I didn't run
> out of licences - I knew I was sailing close to the wind. So now
> I have 4 spare licences from the original CAL pack and another
> 15, none of which have been issued yet. So, 19 spare licences.
>
> The Licensing Server is in per device mode, the CALs are all per
> device CALs and so are the Terminal Servers (believe me - I've
> checked, at first I thought I must have forgotten one and left
> it in Per-User, but no).
>
> What is happening is that when a license expires, and the device
> connects to Server1 I get the message "The remote session was
> disconnected because there are no Terminal Server client access
> licenses available for this computer. Please contact the server
> administrator." Strange because this is usually when per device
> Terminal Servers are trying to contact a Per-User Licensing
> Server.
>
> BUT
>
> If you then immediately connect to Server2 from the same client,
> the licence is granted and everything is fine, and you can log
> onto either server from the client.
>
> As I said, both TS's can see the Licensing Server (from both TS
> Licensing and through lsview.exe) , they're in the same domain
> and AD Site as the licensing server, and there's plenty of
> Licenses.
>
> What's going on???!

 

[blueboy1894]

Re: Only one of 2 load balanced servers allows clients to obtain a

Re: Only one of 2 load balanced servers allows clients to obtain a

Thanks for the response Vera,

OK:

Having had a closer look at the EventViewer it suggests that the Terminal
Server is contacting a license server on our other AD Site to obtain a
licence for the client - which is very odd. "The terminal server client
WindowsCE has been disconnected because its license could not be renewed"
(Event 1028). This now makes the error to be more sensible since the other
Licensing Server on the other AD Site IS in Per-User mode (For
hsitorical/merger reasons).

I can hard-define the licensing server if necessary, and see how it goes,
but Server2 is configured exactly the same way (automatic discovery), so it
doesn't really follow.

The Licensing Server Security Group is not used.

Both Servers are SP2.

Thanks in advance

Chris

"Vera Noest [MVP]" wrote:

> Anything in the EventLog on Server1?
> Are you using a Licensing Server Security Group on the LS?
> I understand that the servers run Windows 2003, but which SP are
> they running?
>
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> *----------- Please reply in newsgroup -------------*
>
> =?Utf-8?B?Ymx1ZWJveTE4OTQ=?=
> <blueboy1894@discussions.microsoft.com> wrote on 02 okt 2007:
>
> > Okay, I have a bit of a weird situation here.
> >
> > I recently rebuilt my 2-Server TS NLB Cluster becuase I wanted
> > to re-build the RAID configurations. All went fine, NLB Cluster
> > is up, along with Session Directory, and both servers can see
> > the licence server. So far so good.
> >
> > I also purchased 15 additional CALs to ensure that I didn't run
> > out of licences - I knew I was sailing close to the wind. So now
> > I have 4 spare licences from the original CAL pack and another
> > 15, none of which have been issued yet. So, 19 spare licences.
> >
> > The Licensing Server is in per device mode, the CALs are all per
> > device CALs and so are the Terminal Servers (believe me - I've
> > checked, at first I thought I must have forgotten one and left
> > it in Per-User, but no).
> >
> > What is happening is that when a license expires, and the device
> > connects to Server1 I get the message "The remote session was
> > disconnected because there are no Terminal Server client access
> > licenses available for this computer. Please contact the server
> > administrator." Strange because this is usually when per device
> > Terminal Servers are trying to contact a Per-User Licensing
> > Server.
> >
> > BUT
> >
> > If you then immediately connect to Server2 from the same client,
> > the licence is granted and everything is fine, and you can log
> > onto either server from the client.
> >
> > As I said, both TS's can see the Licensing Server (from both TS
> > Licensing and through lsview.exe) , they're in the same domain
> > and AD Site as the licensing server, and there's plenty of
> > Licenses.
> >
> > What's going on???!
>

 

[blueboy1894]

Re: Only one of 2 load balanced servers allows clients to obtain a

Re: Only one of 2 load balanced servers allows clients to obtain a

This is giving my TS Licensing memory a workout - if memory serves, any
license server which is in enterprise mode (which the remote ls is) will be
found first, and then the search will stop.

This seems a bit odd since I was under the impression this search is
confined to the same site as the TS, which presumably why previously the
search has got all the way down to the domain scope level, and then picked up
the ls from the dc.

As below, I can hard-specify it, but seems a bit odd when lsview only shows
the correct ls in the correct site.

"Vera Noest [MVP]" wrote:

> Anything in the EventLog on Server1?
> Are you using a Licensing Server Security Group on the LS?
> I understand that the servers run Windows 2003, but which SP are
> they running?
>
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> *----------- Please reply in newsgroup -------------*
>
> =?Utf-8?B?Ymx1ZWJveTE4OTQ=?=
> <blueboy1894@discussions.microsoft.com> wrote on 02 okt 2007:
>
> > Okay, I have a bit of a weird situation here.
> >
> > I recently rebuilt my 2-Server TS NLB Cluster becuase I wanted
> > to re-build the RAID configurations. All went fine, NLB Cluster
> > is up, along with Session Directory, and both servers can see
> > the licence server. So far so good.
> >
> > I also purchased 15 additional CALs to ensure that I didn't run
> > out of licences - I knew I was sailing close to the wind. So now
> > I have 4 spare licences from the original CAL pack and another
> > 15, none of which have been issued yet. So, 19 spare licences.
> >
> > The Licensing Server is in per device mode, the CALs are all per
> > device CALs and so are the Terminal Servers (believe me - I've
> > checked, at first I thought I must have forgotten one and left
> > it in Per-User, but no).
> >
> > What is happening is that when a license expires, and the device
> > connects to Server1 I get the message "The remote session was
> > disconnected because there are no Terminal Server client access
> > licenses available for this computer. Please contact the server
> > administrator." Strange because this is usually when per device
> > Terminal Servers are trying to contact a Per-User Licensing
> > Server.
> >
> > BUT
> >
> > If you then immediately connect to Server2 from the same client,
> > the licence is granted and everything is fine, and you can log
> > onto either server from the client.
> >
> > As I said, both TS's can see the Licensing Server (from both TS
> > Licensing and through lsview.exe) , they're in the same domain
> > and AD Site as the licensing server, and there's plenty of
> > Licenses.
> >
> > What's going on???!
>

 

[Vera Noest [MVP]]

Re: Only one of 2 load balanced servers allows clients to obtain a

Re: Only one of 2 load balanced servers allows clients to obtain a

Yes, I agree that something isn't quite as expected.
The AD query for an Enterprise LS should be confined to the same
site, so your first TS shouldn't detect the Enterprise LS in the
other site, and a Domain LS (which I presume is how your own LS is
configured) should only be autodiscovered if it runs on a DC in the
same site. Again assuming that your Domain LS runs on a member
server, your second TS shouldn't be able to detect your own LS.
But maybe it does run on a DC?

301932 - Terminal Services Licensing service discovery
http://support.microsoft.com/?kbid=301932

Anyway, as you already said, the easiest way to solve the problem
is to configure a prefferred LS for both terminal Servers. I'd use
a Group Policy to do that.
_________________________________________________________
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?Ymx1ZWJveTE4OTQ=?=
<blueboy1894@discussions.microsoft.com> wrote on 02 okt 2007 in
microsoft.public.windows.terminal_services:

> This is giving my TS Licensing memory a workout - if memory
> serves, any license server which is in enterprise mode (which
> the remote ls is) will be found first, and then the search will
> stop.
>
> This seems a bit odd since I was under the impression this
> search is confined to the same site as the TS, which presumably
> why previously the search has got all the way down to the domain
> scope level, and then picked up the ls from the dc.
>
> As below, I can hard-specify it, but seems a bit odd when lsview
> only shows the correct ls in the correct site.
>
> "Vera Noest [MVP]" wrote:
>
>> Anything in the EventLog on Server1?
>> Are you using a Licensing Server Security Group on the LS?
>> I understand that the servers run Windows 2003, but which SP
>> are they running?
>>
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> *----------- Please reply in newsgroup -------------*
>>
>> =?Utf-8?B?Ymx1ZWJveTE4OTQ=?=
>> <blueboy1894@discussions.microsoft.com> wrote on 02 okt 2007:
>>
>> > Okay, I have a bit of a weird situation here.
>> >
>> > I recently rebuilt my 2-Server TS NLB Cluster becuase I
>> > wanted to re-build the RAID configurations. All went fine,
>> > NLB Cluster is up, along with Session Directory, and both
>> > servers can see the licence server. So far so good.
>> >
>> > I also purchased 15 additional CALs to ensure that I didn't
>> > run out of licences - I knew I was sailing close to the wind.
>> > So now I have 4 spare licences from the original CAL pack and
>> > another 15, none of which have been issued yet. So, 19 spare
>> > licences.
>> >
>> > The Licensing Server is in per device mode, the CALs are all
>> > per device CALs and so are the Terminal Servers (believe me -
>> > I've checked, at first I thought I must have forgotten one
>> > and left it in Per-User, but no).
>> >
>> > What is happening is that when a license expires, and the
>> > device connects to Server1 I get the message "The remote
>> > session was disconnected because there are no Terminal Server
>> > client access licenses available for this computer. Please
>> > contact the server administrator." Strange because this is
>> > usually when per device Terminal Servers are trying to
>> > contact a Per-User Licensing Server.
>> >
>> > BUT
>> >
>> > If you then immediately connect to Server2 from the same
>> > client, the licence is granted and everything is fine, and
>> > you can log onto either server from the client.
>> >
>> > As I said, both TS's can see the Licensing Server (from both
>> > TS Licensing and through lsview.exe) , they're in the same
>> > domain and AD Site as the licensing server, and there's
>> > plenty of Licenses.
>> >
>> > What's going on???!

 

[blueboy1894]

Re: Only one of 2 load balanced servers allows clients to obtain a

Re: Only one of 2 load balanced servers allows clients to obtain a

Yep, it is a domain ls running on a dc.

I have now configured the GPO to use this ls, so presumably this should sort
it so I'll keep an eye out for which client is due to expire next!

Thanks Vera

Chris

"Vera Noest [MVP]" wrote:

> Yes, I agree that something isn't quite as expected.
> The AD query for an Enterprise LS should be confined to the same
> site, so your first TS shouldn't detect the Enterprise LS in the
> other site, and a Domain LS (which I presume is how your own LS is
> configured) should only be autodiscovered if it runs on a DC in the
> same site. Again assuming that your Domain LS runs on a member
> server, your second TS shouldn't be able to detect your own LS.
> But maybe it does run on a DC?
>
> 301932 - Terminal Services Licensing service discovery
> http://support.microsoft.com/?kbid=301932
>
> Anyway, as you already said, the easiest way to solve the problem
> is to configure a prefferred LS for both terminal Servers. I'd use
> a Group Policy to do that.
> _________________________________________________________
> 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?Ymx1ZWJveTE4OTQ=?=
> <blueboy1894@discussions.microsoft.com> wrote on 02 okt 2007 in
> microsoft.public.windows.terminal_services:
>
> > This is giving my TS Licensing memory a workout - if memory
> > serves, any license server which is in enterprise mode (which
> > the remote ls is) will be found first, and then the search will
> > stop.
> >
> > This seems a bit odd since I was under the impression this
> > search is confined to the same site as the TS, which presumably
> > why previously the search has got all the way down to the domain
> > scope level, and then picked up the ls from the dc.
> >
> > As below, I can hard-specify it, but seems a bit odd when lsview
> > only shows the correct ls in the correct site.
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> Anything in the EventLog on Server1?
> >> Are you using a Licensing Server Security Group on the LS?
> >> I understand that the servers run Windows 2003, but which SP
> >> are they running?
> >>
> >> _________________________________________________________
> >> Vera Noest
> >> MCSE, CCEA, Microsoft MVP - Terminal Server
> >> TS troubleshooting: http://ts.veranoest.net
> >> *----------- Please reply in newsgroup -------------*
> >>
> >> =?Utf-8?B?Ymx1ZWJveTE4OTQ=?=
> >> <blueboy1894@discussions.microsoft.com> wrote on 02 okt 2007:
> >>
> >> > Okay, I have a bit of a weird situation here.
> >> >
> >> > I recently rebuilt my 2-Server TS NLB Cluster becuase I
> >> > wanted to re-build the RAID configurations. All went fine,
> >> > NLB Cluster is up, along with Session Directory, and both
> >> > servers can see the licence server. So far so good.
> >> >
> >> > I also purchased 15 additional CALs to ensure that I didn't
> >> > run out of licences - I knew I was sailing close to the wind.
> >> > So now I have 4 spare licences from the original CAL pack and
> >> > another 15, none of which have been issued yet. So, 19 spare
> >> > licences.
> >> >
> >> > The Licensing Server is in per device mode, the CALs are all
> >> > per device CALs and so are the Terminal Servers (believe me -
> >> > I've checked, at first I thought I must have forgotten one
> >> > and left it in Per-User, but no).
> >> >
> >> > What is happening is that when a license expires, and the
> >> > device connects to Server1 I get the message "The remote
> >> > session was disconnected because there are no Terminal Server
> >> > client access licenses available for this computer. Please
> >> > contact the server administrator." Strange because this is
> >> > usually when per device Terminal Servers are trying to
> >> > contact a Per-User Licensing Server.
> >> >
> >> > BUT
> >> >
> >> > If you then immediately connect to Server2 from the same
> >> > client, the licence is granted and everything is fine, and
> >> > you can log onto either server from the client.
> >> >
> >> > As I said, both TS's can see the Licensing Server (from both
> >> > TS Licensing and through lsview.exe) , they're in the same
> >> > domain and AD Site as the licensing server, and there's
> >> > plenty of Licenses.
> >> >
> >> > What's going on???!
>