Software License and *.exe management

Flo2France's picture
Flo2France
January 28th, 2009

Software License (contract/PO/License) versus installed/discovered software and the management of *.exe to clean data. 3 Questions:
. How do you manage the software license in Altiris. I mean by that using the Contract / Software Purchase / Software License in Altiris? Do you do it in Altiris or with another product or skip it?
. The above question is triggered by having a huge volume of software (*.exe) with unclean data from the discovery ("n" manager/product names for a same product). How do you aquire the knowledge of the *.exe and deal with a consequent volume of software at the start of the Altiris implementation?

Thank you.

Filed under:
0 votes
DeborahAlbrecht's picture
DeborahAlbrecht
42 weeks 4 days ago

SW Purchase and License Info

Hi there.

You first have to setup your Software Purchase, which has 3 pieces (in my eyes) that are important. (1) Product Name, (2) Product Version and (3) Quantity. These 3 fields are used to link the software purchase and license compliance (quantity) to the software license entry itself.

Once your software purchase is setup you can setup your Software License. A couple of items that are important here. On the General Tab make sure you select the License Type (concurrent or per install). On the Software Purchases tab add a Rule to link your SW Purchase to your License entry (again this helps you know if you are in compliance).

In my opinion, the most important part of the Software License is the "Software Installs" tab. Here you will note all of your non-inventoried installs as well as (the more important) Software License Search Rules. Here is where you will specify the software foot printing which the software will be detected from.

To find more data about the software and the foot print it leaves, go to SQL (or Resource Manager > Inventory tab > Inventory > Software > Aex SW Audit Software) and check out the table "Inv_Aex_SW_Audit_Software.

Please note that a single software may have multiple foot prints within this table. I suggest choosing the actual executable and narrow it by using the version.

Example. Microsoft Outlook 2007 would be entered as follows:

FILE NAME: outlook.exe
VERSION: 12.%

This take a lot of work up front to setup, but you will enjoy the benefits of your applications and software compliance being setup within Altiris!

Good luck!

-d

-d

0 votes