There are two methods for configuring Application Metering policies: 1) defining criteria for specific files to be metered or 2) selecting software releases/products to be metered. The second option is desirable in that the metering data becomes associated to software products as software usage data that can be used for identifying computers that are wasting software licenses, etc. Unfortunately some software products (Adobe and Microsoft suites) can have associations to hundreds of files due to their complexity and this can make their application metering data bloated and meaningless. It is not possible to manually modify the file associations on the software releases because the NS.Nightly task automatically re-associates all the files and software releases generated by software inventory.
The easiest solution when metering complex software is to use the first method and meter specific files rather than software. However if software usage data is required then the NS.Nightly issue can be avoided by manually creating software products, software releases, and file associations rather than using those generated by software inventory. The following steps demonstrate this process.
1. Create a Software Release
2. Create a Detection Rule for the Software Release
3. Create a Targeted Software Inventory Policy
4. Create a Software Product
5. Associate Program Files to the Software Product
6. Enable Application Metering on the Software Product
7. View the Application Metering data