Cals Getting Used Up

[rbg]

I have a medium sized distribunted communitiy of devices. My license sever
tells mr that cals allocated to the same machine name. Are the any utilities
that can show move information regarding the machine as I want to avoid
asking the users to look at their terminal settings. I suspect there is a
faulty terminal which is taking more than one license but I cannot eaasily
find it as the machine name is not listed against any logged in sessions but
licenses continue to be allcated to this machine name. Please help.

 

[TP]

Re: Cals Getting Used Up

Hi,

There are a couple of tools in the resource kit that can help
you troubleshoot this. They are lsreport.exe and tsctst.exe.

You can download the resource kit tools here:

Windows Server 2003 Resource Kit Tools

http://www.microsoft.com/downloads/details.aspx?familyid=9d467a69-57ff-4ae7-96ee-b18c4790cffd

After installing you can open up the Resource Kit help file
and find full details on usage of each tool. Quick summary:

lsreport.exe - Run on your TS licensing server, creates
lsreport.txt file which contains information about issued
licenses and installed license packs.

tsctst.exe - Run this on each *workstation*, it gives you
information about the license stored on the device.

-TP

rbg wrote:
> I have a medium sized distribunted communitiy of devices. My license
> sever tells mr that cals allocated to the same machine name. Are the
> any utilities that can show move information regarding the machine as
> I want to avoid asking the users to look at their terminal settings.
> I suspect there is a faulty terminal which is taking more than one
> license but I cannot eaasily find it as the machine name is not
> listed against any logged in sessions but licenses continue to be
> allcated to this machine name. Please help.

 

[rbg]

Re: Cals Getting Used Up

Thanks for your reply. I tried this, it gives similar information to the
license manager. I have 98% windows terminals connected.

Here are the results some of the results.

fpdc2 2171 4 HP-D5P649P1WN8V User 26/07/2007 24/09/2007 Active A02-5.02-S
fpdc2 2237 4 HP-D5P649P1WN8V User 14/08/2007 17/10/2007 Active A02-5.02-S
fpdc2 2255 4 WT00806467a9d4 19/08/2007 13/11/2007 Active A02-5.02-S

In each case the machine name is unique except for HP-D5P649P1WN8V where we
have several hundred temp licenses allocated and about 15% of the active
licenses allocated to the same name at various dates and times but cannot
track down the terminal. Is it possible to create an event with the ip
address and machine name
each time a licence is checked out in a debug mode to catch it. (Multiple
sites and subnets!). As I said before this machine name never seems to
appear on the list of users logged in even though a license has bee taken
today.

Regards
RBG
"TP" wrote:

> Hi,
>
> There are a couple of tools in the resource kit that can help
> you troubleshoot this. They are lsreport.exe and tsctst.exe.
>
> You can download the resource kit tools here:
>
> Windows Server 2003 Resource Kit Tools
>
> http://www.microsoft.com/downloads/details.aspx?familyid=9d467a69-57ff-4ae7-96ee-b18c4790cffd
>
> After installing you can open up the Resource Kit help file
> and find full details on usage of each tool. Quick summary:
>
> lsreport.exe - Run on your TS licensing server, creates
> lsreport.txt file which contains information about issued
> licenses and installed license packs.
>
> tsctst.exe - Run this on each *workstation*, it gives you
> information about the license stored on the device.
>
> -TP
>
> rbg wrote:
> > I have a medium sized distribunted communitiy of devices. My license
> > sever tells mr that cals allocated to the same machine name. Are the
> > any utilities that can show move information regarding the machine as
> > I want to avoid asking the users to look at their terminal settings.
> > I suspect there is a faulty terminal which is taking more than one
> > license but I cannot eaasily find it as the machine name is not
> > listed against any logged in sessions but licenses continue to be
> > allcated to this machine name. Please help.
>

 

[TP]

Re: Cals Getting Used Up

Hello RBG,

In Terminal Services Licensing (licmgr.exe) it shows the exact
time a license was issued. Match that up to your security log
and you will have the username and *real* source ip address.

The eventid is 528, scroll to the bottom of the description field
for the Source Network Address.

-TP

rbg wrote:
> Thanks for your reply. I tried this, it gives similar information to
> the license manager. I have 98% windows terminals connected.
>
> Here are the results some of the results.
>
> fpdc2 2171 4 HP-D5P649P1WN8V User 26/07/2007 24/09/2007 Active
> A02-5.02-S fpdc2 2237 4 HP-D5P649P1WN8V User 14/08/2007 17/10/2007
> Active A02-5.02-S fpdc2 2255 4 WT00806467a9d4 19/08/2007 13/11/2007
> Active A02-5.02-S
>
> In each case the machine name is unique except for HP-D5P649P1WN8V
> where we have several hundred temp licenses allocated and about 15%
> of the active licenses allocated to the same name at various dates
> and times but cannot track down the terminal. Is it possible to
> create an event with the ip address and machine name
> each time a licence is checked out in a debug mode to catch it.
> (Multiple sites and subnets!). As I said before this machine name
> never seems to appear on the list of users logged in even though a
> license has bee taken today.
>
> Regards
> RBG

 

[rbg]

Re: Cals Getting Used Up

Ht TP,

That helped. It looks like it takes the license when the client connects
then shows in security when the user loggs on. Been able to track it to a
particulat type of windows based terminal supplied by HP. Is it possible
that they all have the same computer name for licensing purposes? Does that
cause the license server a problem ? It is a shame the lic serv does not
capture somthing more traceable. We definately have more than enough lic for
the devices we have and are working the device cal model but run out because
of the naming issue.

Regards
RBG

Regards
RBG

"TP" wrote:

> Hello RBG,
>
> In Terminal Services Licensing (licmgr.exe) it shows the exact
> time a license was issued. Match that up to your security log
> and you will have the username and *real* source ip address.
>
> The eventid is 528, scroll to the bottom of the description field
> for the Source Network Address.
>
> -TP
>
> rbg wrote:
> > Thanks for your reply. I tried this, it gives similar information to
> > the license manager. I have 98% windows terminals connected.
> >
> > Here are the results some of the results.
> >
> > fpdc2 2171 4 HP-D5P649P1WN8V User 26/07/2007 24/09/2007 Active
> > A02-5.02-S fpdc2 2237 4 HP-D5P649P1WN8V User 14/08/2007 17/10/2007
> > Active A02-5.02-S fpdc2 2255 4 WT00806467a9d4 19/08/2007 13/11/2007
> > Active A02-5.02-S
> >
> > In each case the machine name is unique except for HP-D5P649P1WN8V
> > where we have several hundred temp licenses allocated and about 15%
> > of the active licenses allocated to the same name at various dates
> > and times but cannot track down the terminal. Is it possible to
> > create an event with the ip address and machine name
> > each time a licence is checked out in a debug mode to catch it.
> > (Multiple sites and subnets!). As I said before this machine name
> > never seems to appear on the list of users logged in even though a
> > license has bee taken today.
> >
> > Regards
> > RBG
>

 

[TP]

Re: Cals Getting Used Up

Hi,

It takes the name based on what the client gives it when a
license is first issued to the device. It is not a problem having
the same name because a unique hardware id is associated
with each license. If things are working properly the name
will stay the same even if the local device changes its name
because the unique hardware id stored on the device stays
the same.

lsreport /w will dump this hardware id on the server side
whereas tsctst /a will show it on the client side (in your case
you may be unable to run tsctst because of the client OS).

It sounds like one or more of your terminals needs a firmware
update or is faulty and is resetting to factory defaults each time.
This makes it appear to be a "brand new" device as far as
the TS licensing server is concerned.

-TP

rbg wrote:
> Ht TP,
>
> That helped. It looks like it takes the license when the client
> connects then shows in security when the user loggs on. Been able to
> track it to a particulat type of windows based terminal supplied by
> HP. Is it possible that they all have the same computer name for
> licensing purposes? Does that cause the license server a problem ?
> It is a shame the lic serv does not capture somthing more traceable.
> We definately have more than enough lic for the devices we have and
> are working the device cal model but run out because of the naming
> issue.
>
> Regards
> RBG

 

[rbg]

Re: Cals Getting Used Up

Hi TP,

I checked the web for command line but it does not list that one! Anyway we
make further progress. So What you are suggesting is that each terminal
should have a unique hardware number. What we seem to have is a range of
terminals from one manufacturer where the hardware number is the same for all
terminals. So what must be happening is that they are continuously cycling
between tempory and permenant using up all of the licenses. This must have
been happening over a few years as I guess it takes 6 months for each
terminal to clock over a license 3 month temporary 3months perm but the when
it goes to renew it goes back to temporary as the hardware id is already
allocated ! Slowly using up the licenses.
What do you think ? What solution should we look for ?
Regards
RBG

"TP" wrote:

> Hi,
>
> It takes the name based on what the client gives it when a
> license is first issued to the device. It is not a problem having
> the same name because a unique hardware id is associated
> with each license. If things are working properly the name
> will stay the same even if the local device changes its name
> because the unique hardware id stored on the device stays
> the same.
>
> lsreport /w will dump this hardware id on the server side
> whereas tsctst /a will show it on the client side (in your case
> you may be unable to run tsctst because of the client OS).
>
> It sounds like one or more of your terminals needs a firmware
> update or is faulty and is resetting to factory defaults each time.
> This makes it appear to be a "brand new" device as far as
> the TS licensing server is concerned.
>
> -TP
>
> rbg wrote:
> > Ht TP,
> >
> > That helped. It looks like it takes the license when the client
> > connects then shows in security when the user loggs on. Been able to
> > track it to a particulat type of windows based terminal supplied by
> > HP. Is it possible that they all have the same computer name for
> > licensing purposes? Does that cause the license server a problem ?
> > It is a shame the lic serv does not capture somthing more traceable.
> > We definately have more than enough lic for the devices we have and
> > are working the device cal model but run out because of the naming
> > issue.
> >
> > Regards
> > RBG
>