It's not just counting cpu's, which isn’t hard via WMI or registry scripting.  
The trick is finding out if multi-cores are being used (different pvu units 
than single), and if logical procs (e.g. hyperthreading) are included.

You cant even get this info from WMI without a non-public hotfix from M$ 
applied to all of your windows servers (and one of the files replaced is 
ntoskrnl - how good do you feel about rolling that out?).

Intel has a downloadable program called cpucount.exe if you have all intel 
procs, but even that tool doesn’t play well with mass remote scripting without 
some recoding and compiling, which isn’t very useful for us non-C++ programmer 
types.  (if someone does get this to work by yanking out the need to hit 
"return" at the end of the program, please share).

But who knows?  Maybe Tivoli will pull the rabbit out of the hat and build it 
into v6 somehow.

Until then, the SWAGging will continue...

Steve Schaub
Systems Engineer, Windows
Blue Cross Blue Shield of Tennessee


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Gill, Geoffrey L.
Sent: Thursday, August 07, 2008 12:58 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] New Tivoli Licensing Free Metric tool!

Anything 'mandatory' should be built in to the TSM product in my opinion. They 
already get a ton of information about the servers so how hard can it be to add 
cpu's to the node info.

----- Original Message -----
From: ADSM: Dist Stor Manager <ADSM-L AT VM.MARIST DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU <ADSM-L AT VM.MARIST DOT EDU>
Sent: Thu Aug 07 09:48:41 2008
Subject: Re: New Tivoli Licensing Free Metric tool!

>If this has a heavy enough footprint to not warrant running on a 
>workstation or desktop, theres no way on earth I'd allow it on any of
my
>servers.

But didn't somebody say that they heard it was going to be mandatory?





This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. If 
you have received this email in error please notify the system manager. This 
message contains confidential information and is intended only for the 
individual named. If you are not the named addressee you should not 
disseminate, distribute or copy this e-mail.
Please see the following link for the BlueCross BlueShield of Tennessee E-mail 
disclaimer:  http://www.bcbst.com/email_disclaimer.shtm