Beruflich Dokumente
Kultur Dokumente
APPLICATION METERING
SOLUTION 6.0
PRODUCT GUIDE
Notice
Copyright 2001-2004 Altiris Inc. All rights reserved.
Product Version: 6.0
Document Date: March 29, 2004
Bootworks U.S. Patent No. 5,764,593.
RapiDeploy U.S. Patent No. 6,144,992.
Due to the inherently complex nature of computer software, Altiris does not warrant that the Altiris
software is error-free, will operate without interruption, is compatible with all equipment and
software configurations, or will otherwise meet your needs.
The content of this documentation is furnished for informational use only, is subject to change
without notice, and should not be construed as a commitment by Altiris. Altiris Inc. assumes no
responsibility or liability for any errors or inaccuracies that may appear in this documentation. For
the latest documentation, visit our Web site at www.altiris.com.
Altiris, the Altiris logo, BootWorks, Inventory Solution, LabExpert, PC Transplant, RapiDeploy,
and RapidInstall are registered trademarks of Altiris, Inc. in the United States.
Carbon Copy is a registered trademark licensed to Altiris, Inc. in the United States and a trademark
of Altiris, Inc. in other countries.
Altiris eXpress, Altiris Vision, Application Management Solution, Application Metering Solution,
Asset Control Solution, Asset Management Suite, Client Management Suite, Compliance Toolkit,
Conflict Analysis Solution, Contract Management Solution, Deployment Server, Deployment
Solution, Education Management Suite, Helpdesk, Helpdesk Solution,
HP Client Manager Software, Lab Management Suite, Migration Toolkit, Mobile Client for SMS,
My IT Forum, Notification Server, Problem Management Suite, Server Management Suite,
Server Monitor Solution, Site Monitor Solution, Software Delivery Solution,
TCO Management Solution, Unix Client for SMS, Unix Inventory Solution, Unix Software Deliver
Solution, Web Admin for SMS, Web Reports and other product names are trademarks of Altiris, Inc.
in the United States and other countries.
Microsoft, Windows, and the Windows logo are trademarks, or registered trademarks of Microsoft
Corporation in the United States and/or other countries.
HP is a registered trademark of the Hewlett-Packard Corporation.
Compaq is a registered trademark of the Hewlett-Packard Corporation.
Macintosh is a registered trademark of the Apple Computer Corporation.
All other brand names are trademarks or registered trademarks of their respective companies.
Contents
Application
Altiris
Product
Guide
Metering Solution 6.0
Notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Chapter 1: Introducing Application Metering Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Terminology
...................................................................... 5
............................................... 5
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
. . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
11
12
13
13
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Monitoring an Application
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Chapter 1:
Web
Administration
Discover Applications
Monitor Frequency of
Application Usage
Report Starting and
Stopping of Applications
SMS
Integration
License Harvesting
Notification
Server
Managed
Computers
Web-based
Reports
Discover Applications that Are Run Application Metering Solution records the first time an
application is started. This makes it easy to identify exactly what software (including the version)
is being run on the computers of your network.
Monitor Frequency of Application Usage You can track the number of times a particular
application is run on a computer. This helps you determine whether applications are used
frequently or rarely and by whom applications are used.
Track Starting and Stopping of Applications You can track when an application is started,
stopped, or both and how long an application is used. You can also be alerted when an attempt
is made to start an unauthorized application or block the use of an application.
License Harvesting Application Metering Solution integrates with Altiris Inventory Solution to
identify the applications installed on computers (Inventory Solution) and which of these
applications are used. This helps you reclaim (harvest) unused software licenses and put them to
use elsewhere.
The many features of Application Metering Solution provide data for numerous predefined reports
that can help you to analyze your data. There are reports for analyzing application performance,
application usage, and unauthorized usage. There are cost analysis and inventory audit reports.
There are also history and trend, concurrent usage, and many other reports that provide powerful
analysis of your environment. If there is not a predefined report for your needs, you can leverage the
extensive data Application Metering Solution provides through custom reporting.
Terminology
Terminology
To understand this document, it is important that you understand the Application Metering Solutionspecific terminology used in this document. The following are terms with which you should be
familiar as you use this document:
application monitoring period
This period specifies how often Application Metering Solution summary data is uploaded from
the managed computer to the Notification Server. This period also specifies how long the use of
an application is counted before the counter is reset.
application summary data
Data collected about a monitored application during the application monitoring period, such as
product name, manufacturer, and last user.
license harvesting
The process of determining which applications installed on a computer are not used, removing
these applications from these computers, and making the software licenses for the removed
applications available for use elsewhere.
managed computer
A computer on the network that is running the Altiris Agent and managed by Notification Server.
monitored application
An application that is being monitored on managed computers by Application Metering Solution
using an application monitoring policy.
start event, stop event, denial event
An event sent to the Notification Server from the managed computer in response to the starting
or stopping of a monitored application. A denial event is a start event where the user was denied
the use of the application after attempting to start it.
Chapter 2:
Monitor and prevent the use of an application using a predefined application monitoring policy
Important: This procedure assumes that Notification Server is already installed, the Altiris Agent is
installed on the computers with applications you want to monitor, and Application Metering
Solution is installed on the Notification Server. If any of these are not installed, install them before
proceeding.
In the left pane, click Solution Settings > Application Metering Solution > Application Metering
Solution Agent Rollout > Win32 Application Metering Agent Install/Upgrade.
This will deploy the Application Metering Agent to managed workstation (not server) computers the
next time the Altiris Agent checks for updated configuration information (by default, the Altiris
Agent checks for new configuration information every fifteen minutes) after the policy is enabled.
Important: If you are installing the agent on a managed computer running Windows NT, you must
restart the computer after installing the agent. Also, if you are installing the agent on a managed
computer that already has the agent installed on it (upgrading) and the computer is running Windows
9x/Me/NT, you must restart the computer after upgrading. No restart is necessary on computers
running Windows 2000/XP.
After the Application Metering Agent is installed, the application discovery feature automatically
discovers applications as they are run. The discovery feature keeps track of the applications run on
a managed computer and sends this information to the Notification Server.
Note: Application Metering Solution only discovers applications as they are used - not all installed
In the left pane, click Tasks > Software Management > Application Metering Solution > Application
Monitors (Games) > Pinball 3D.
In the right pane, select the Enable check box if it is not already selected (selected by default).
Select the Deny users the ability to run this application check box.
To generate some data about the use of Pinball 3D, start Pinball 3D on a managed computer after
the application monitoring policy configuration information has been sent to the managed
computer.
To start Pinball 3D, click Start > Programs > Accessories > Games > Pinball on a managed
computer.
When you attempt to run the program, you will get a message indicating that you cannot run the
program. Data will also be recorded about the attempt to run the program.
Metering Solution
3
Select the Clients with Application Metering Agent Installed check box under Collections >
Application Metering Solution > Application Metering Agent Rollout.
10
To record some data about the use of Microsoft HTML Help, start Microsoft HTML Help on a
managed computer after the application monitoring policy configuration information has been
sent to the managed computer by clicking Start > Help
In the left pane, click Reports > Software Management > Application Metering Solution >
Discovered Applications > List discovered applications (machine count).
In the right pane, select the View report on latest data link, and then click the Submit button.
This will create a table report in the right pane.
In the left pane, click Reports > Software Management > Application Metering Solution > History
and Trend > Count application usage (date range).
In the right pane, select the View report on latest data link.
This will create a table report in the right pane.
Note: Certain Application Metering Solution reports require data from Inventory Solution. If you
are not correlating Inventory Solution data with Application Metering Solution data, these reports
will not work or will only display data collected by Application Metering Solution.
Whats Next?
After you complete the above steps, Application Metering Solution is monitoring the use of two
applications and uploading application summary data from the managed computer to the
Notification Server on a regular basis. For more information on the Application Metering Solution
features, see the documentation on the specific feature.
Chapter 3:
If you want to correlate Inventory Solution data with Application Metering Solution data, specify
how you will be using Inventory Solution with Application Metering Solution (see Application
Metering Solution Configuration on page 10).
Deploy the Application Metering Agent (see Application Metering Agent on page 16). This
agent provides the Application Metering Solution functionality on the managed computers.
After the Application Metering Agent is installed on managed computers, the agent will
automatically discover applications as they are used on the managed computers (see
Discovering Applications on page 10).
Specify the applications you want to monitor (see Application Monitoring on page 19).
Chapter 4:
Discovering Applications
Application Metering Solution can automatically discover the first time a version of an application
is run. After a new application is discovered on a managed computer by being run, data about the
application is added to a file on the managed computer (the application discovery file) and an event
with the application data is sent immediately to the Notification Server.
Note: Application Metering Solution only discovers applications as they are used - not all installed
Note: The application discovery file is named AexAMDiscovery.txt and is located in the same folder
as the Altiris Agent (c:\Program Files\Altiris\Altiris Agent by default). You must not edit or change
this file; in fact, opening this file at the wrong time can cause errors in the discovery process. If you
have problems with application discovery, opening this file can help you to verify that the
Application Metering Agent was able to discover applications.
During the initial application discovery stage, many events are generated, because many
applications are discovered and the data is uploaded to the Notification Server. After the initial
discovery, far fewer applications are discovered and there is little system overhead. You can use
reports to identify which applications are new.
To discover applications, the Application Metering Agent must be deployed on the managed
computers. By default, application discovery is enabled and will automatically discover applications
on managed computers. For more information, see Deploying the Application Metering Agent on
page 16.
To enable or disable application discovery
1
In the left pane, click Configuration > Solution Settings > Application Metering Solution >
Application Metering Solution Configuration.
If you want to disable application discovery, clear the Discover and report all new Win32
applications executed on client machines check box.
If you want to enable application discovery, select the Discover and report all new Win32
applications executed on client machines check box.
10
Chapter 4: Application Metering Solution ConfigurationIntegrating Application Metering Solution with Inventory Solution
For a description of the options, see Application Metering Solution Configuration Page on
page 14.
4
11
Field
Description
Manufacturer
Internal Name
explorer
File Version
5.00.3315.2846
File Name
explorer.exe
Product Name
Microsoft(R)
Windows (R) 2000
Operating System
5.00.3315.2846
Known As
Windows Explorer
User
jsmith
Domain
ALTIRIS
Discovered
6/03/2002 11:39:53
AM
Last Start
11/03/2002 8:38:18
AM
Month Year
(month we
tracked it in)
Month and year of the last application monitoring period March 2002
in which the application was monitored.
Run Count
Denial Count
Total Run Time Total amount of time during the last application
monitoring period that the application was used in
seconds. This value is determined by monitoring the
application process and is updated every 30 seconds.
Peak Memory
Sample Data
188714.032
7921664
Maximum amount of memory used by the application
during the application monitoring period in bytes. This
value is determined by monitoring the application process
and is updated every 30 seconds. This information is NOT
available from Windows 9x/Me managed computers.
12
Field
Description
Sample Data
0.7652
Avg CPU Usage Average CPU usage by the application during the last
application monitoring period, where 100 equals 100
percent usage. This value is determined by monitoring the
application process and is updated every 30 seconds. This
information is NOT available from Windows 9x/Me
managed computers.
Month End
Summary
In the left pane, click Configuration > Solutions Settings > Application Metering Solution >
Application Metering Solution Configuration.
To enable the uploading of application summary data, select the Client should send summary data
every check box.
To disable the uploading of application summary data, clear the Client should send summary data
every check box.
To change the upload frequency of application summary data, select an upload interval using the
field associated with the Client should send summary data every check box.
To enable the automatic deletion of old application summary data, select the Purge summary data
older than check box.
To disable the automatic deletion of old application summary data, clear the Purge summary data
older than check box.
To change how long old application summary data is kept before it is deleted, enter a value in
the field associated with the Purge summary data older than check box.
To delete old application summary data immediately, click the Purge Data Now button.
13
In the left pane, click Configuration > Solutions Settings > Application Metering Solution >
Application Metering Solution Configuration.
Item
Description
Purge events older than Select this checkbox to automatically delete old event data. If this
checkbox is selected, you can specify in the associated field the number of
days that data must be older than before it is deleted.
Click this Purge Events Now button to immediately delete events older than
the specified number of days; otherwise, old events will be deleted the
next time Notification Server performs clean-up procedures.
Purge reports older than Select this checkbox to automatically delete old reports. If this checkbox
is selected, you can specify in the associated field the number of days that
a report must be older than before it is deleted.
Click this Purge Reports Now button to immediately delete reports older
than the specified number of days; otherwise, old reports will be deleted
the next time Notification Server performs clean-up procedures.
Purge summary data
older than
Select this checkbox to specify how often summary data is sent to the
Notification Server. If this checkbox is selected, you can specify in the
associated field the how often the data is sent.
Data can be sent every 1, 2, 7, or 14 days. The default is 7 days. Uploading
data less often results in data that is not quite as current. Uploading data
more frequently creates a bit more network traffic. Data can also be
uploaded every 5 minutes, but this setting is intended for testing purposes
only.
14
Item
Description
Discover and report all Select this check box to enable automatic application discovery on
new Win32
computers with the Application Metering Agent installed. For more
applications run on
information, see Discovering Applications on page 10.
client computers
Audit Plus INI
Integration
The Audit Plus integration options allow you to specify how Application
Metering data is correlated with Inventory Solution data. The options are:
I dont use Inventory Solution - Select this option if you do not use
Inventory Solution or do not want to integrate Inventory Solution data
with Application Metering data.
Client based Inventory Solution - Select this option if you use Inventory
15
Chapter 5:
deploying the agent during off-peak hours to minimize network traffic at peak times.
To deploy the Application Metering Agent
Important: Before installing the Application Metering Agent on a computer, the Altiris Agent must
In the left pane, click Solution Settings > Application Metering Solution > Application Metering
Solution Agent Rollout > Win32 Application Metering Agent Install/Upgrade.
If you are installing the agent on a computer running Windows NT, you must restart the
computer after the agent has been deployed on the computer. Following are instructions on how
to configure the agent installation to restart the computers automatically.
If you are upgrading the agent on a Windows 9x/Me/NT computer, you must restart the
computers after upgrading.
No restart is necessary when installing or upgrading the agent on computers running Windows
2000/XP.
To modify the agent package to automatically restart the computers after installing
or upgrading the Application Metering Agent
If you are installing the Application Metering Agent on a computer running Windows NT or
upgrading the agent on a computer running Windows 9x/Me/NT, you must restart the computer after
the agent has been installed or upgraded. If you want to have the agent installation policy
automatically restart the applicable managed computers after installing the Application Metering
Agent, you can do so by modifying the policy package program Command Line field.
1
In the left pane, select Configuration > Solution Settings > Application Metering Solution >
Application Metering Agent Rollout > Win32 Application Metering Agent Package.
16
you want to require a user acknowledgement before restarting, remove the /s from the value in
the field.
17
In the left pane, click Solution Settings > Application Metering Solution > Application Metering
Solution Agent Rollout > Win32 Application Metering Agent Install/Upgrade.
In the left pane, select Solution Settings > Application Metering Solution > Application Metering
> Win32 Application Metering Agent Uninstall.
In the right pane, ensure that Clients with Application Metering Installed is selected in the Applies
to Collection(s) field.
Restart the managed computer after the agent has been uninstalled.
The Application Metering Agent will be removed from the managed computers as soon as possible
after the policy is enabled. If at a later time you want to reinstall the Application Metering Agent,
make sure you disable this Win32 Application Metering Agent Uninstall policy.
18
Chapter 6:
Application Monitoring
Application Metering Solution allows you to do the following for each monitored application:
Send application start, stop, and denial events to the Notification Server
Each time a monitored application starts, the Application Metering Agent records information about
the application and the application execution environment; this is the application summary data.
This data is sent to the Notification Server based on a schedule controlled on the configuration page
(see Configuring the Uploading of Application Summary Data on page 13).
The Application Metering Agent can also send an application start or stop event to the Notification
Server immediately after a monitored application starts or stops. The start and stop events allow the
Notification Server to know when an application is used. Start and stop events also allow you to
determine how long an application has been used. For more information on the start and stop events,
see Start and Stop Events on page 20.
Monitored
Application Stops
App. Metering
Agent
Start event
data (sent
immediately)
App. Metering
Agent
App. Summary
Data File
Sent on a scheule
Altiris Agent
Notification
Server
Stop event
data (sent
immediately)
Notification
Server Database
19
Windows NT/2000/XP
Yes
No
Windows 9x/Me
Yes
Yes
Application Metering Solution allows you to monitor an application based on any of the following
file properties:
File name
Internal name
File version
Company name
Product name
Product version
Note: To view these properties, right-click on the name of the file in My Computer or Windows
Note: When specifying an application to monitor, we recommend that you monitor an internal file
property (all of the properties in the previous list are internal except File name), such as the
internal name. Internal file properties are compiled into the file and cannot be changed by a user. If
you monitor the filename and the user renames the file, you will no longer be monitoring the use of
that application.
sufficient network and server resources to handle the traffic generated by these events. In general, a
single Notification Server can handle real-time reporting of start events for over 10,000 managed
computers. For more information on capacity planning, see the Altiris Scalability document.
20
The following table lists and describes the data sent in a start or stop event. (The fields are listed in
the order in which the data is sent in the event.)
Application start and stop event data fields
Field
Description
Example
PID
Policy Name
MS Word
Start Date
7/03/2002 9:51:18 AM
Internal Name
File Name
winword.exe
File Version
9.0.2717
Product Name
Name of the product. The path to the application file Microsoft Word*
on the managed computer.
Product Version
Manufacturer
File Path
Language
User
User name of the person that last ran the application. jsmith
Domain
ALTIRIS
Known As
Microsoft Word*
Policy Guid
GUID (a unique identifier) of the policy that caused {CC1355B1-3993the start or stop event to be generated.
4519-BB4C8C41735E3825}
Command Line
Denied
0
Specifies whether this is a denial event. A denial
event is a start event followed by the closing of the
application because the running of the application is
prohibited. If the value is equal to 0, the event was
not a denial event. If the value is equal to 1, the
event was a denial event.
Microsoft
Language Neutral
9.0.2717
21
Monitoring an Application
Monitoring an Application
To monitor an application with a predefined application monitoring policy, just enable the policy.
To monitor an application without a predefined application monitoring policy, just create and enable
a new application monitoring policy.
If the Application Metering Agent is monitoring an application that is not stored on a local drive, the
agent will cause the file to be downloaded to a local drive, where it checks the version information.
If many monitored files are not local to the monitoring computer, this can significantly increase
network traffic to download these files. If wanted, you can configure the Application Metering
Agent so not check the file version, which eliminates the need for non-local files to be downloaded.
However, doing this will also prevent any monitoring policies that are based on internal file
information, such as internal name, manufacturer, product name, and company name, from being
able to monitor non-local applications.
To stop the agent from checking for the file version, you need to add the following key to the
registry:
HKLM\SOFTWARE\Altiris\Altiris Agent\NO_VERSION_OVER_NETWORK
To re-enable the checking of the file version, remove the registry key.:
Note: It is possible for multiple policies to monitor the same application. If you have more than one
policy monitoring the same application, you might get erroneous data in reports or trigger duplicated
notification policy actions.
To monitor an application using a predefined application monitoring policy
In the left pane, click the predefined application monitoring policy you want to use under Tasks
> Software Management > Application Metering Solution > application monitor group name.
In the left pane, right-click the Application Monitors group under Tasks > Software Management >
Application Metering Solution and select New > Application Monitor Policy.
In the right pane Name and Description fields, enter a name and description for the policy.
Click the Applies to collections link, and select the collections to which the policy applies.
Click the Click here to select a discovered application link. Use the dialog to search the list of
discovered applications for the one you want to monitor.
Enter the properties of the application you want to monitor in the fields in the Details of
Application to Monitor section. For a description of the fields, see Application Monitor
Configuration Page on page 24.
The application monitored by the policy must meet the criteria of all of the specified fields in the
Details of Application to Monitor section. For example, if you specify the File Name and File version,
only applications that meet both of these criteria will be monitored. Unspecified fields are
ignored.
You can use wildcards in the details fields. Use a * to represent any number of characters and
a % for a single character.
6
22
computer, you must restart the computer before any messages denying the user access to an
application will appear on the managed computer.
You can prevent the use of an application at all times or only at specific times, such as during
business hours.
Note: When a user attempts to use an unauthorized application on a managed computer running
Windows NT/2000/XP, the starting of the application will be stopped immediately. When a user
attempts to use an unauthorized application on a managed computer running Windows 9x/Me, the
use of the application will be stopped within 30 seconds of the starting of the application. On
Windows 9x/Me managed computers, the Application Metering Agent checks every 30 seconds to
determine which applications are running and takes appropriate actions.
If you do not already have the desired application monitoring policy page loaded, load the page.
a
In the left pane, click Tasks > Software Management > Application Metering Solution >
application monitor group name > application monitor policy.
Select the Deny users the ability to run this application check box.
Below the Deny users the ability to run this application check box, specify options.
For a description of the options, see Denied Application Use Options on page 23.
23
Note: The following options are available only when the Deny users the ability to run this application
Item
Description
Deny the use of the application between the times specified in the
associated From and To fields.
Denial to apply for different Deny the use of the application between the times and on the days of
periods on different days
the week specified in the associated days and times fields.
Denial times to be matched Specifies the use of absolute times, based on Greenwich Mean Time,
on Greenwich Mean Time during which the application is not available. If you want to specify
times relative to the local time zone, do not use this option.
In the left pane, click Tasks > Software Management > Application Metering Solution > application
monitor group name > application monitor policy.
Item
Description
Enable
Name
Description
Applies to collections
Link that opens a dialog for selecting the collections to which the policy
applies.
24
Item
Description
Internal Name
Internal name of the applications you want to monitor. This field supports
wildcards. This information is available from the properties of the file.
File Version
File version of the applications you want to monitor. This field supports
wildcards. This information is available from the properties of the file.
Company Name
Product Name
The product name of the applications you want to monitor. This field
supports wildcards. This information is available from the properties of
the file.
Product Version
Known As
Command Line
Option to send application start and denial events from the managed
computer to the Notification Server.
Note: For maximum scalability, report application summary data only.
Option to send both start and stop events from the managed computer to
the Notification Server.
Deny users the ability Option to prevent the running of an application. When this option is
to run this application. selected, several additional options are available. For information on these
options, see Denied Application Use Options on page 23.
Note: In Details of Application to Monitor section, you can use a * to represent any number of
characters and a % for a single character. For example, if you had files named notepad.exe,
notepads.exe, and note.exe, specifying note*.exe would allow you to monitor all of the named files.
note%.exe would only allow you to monitor the notes.exe file.
25
Index
A
agent 16
agent deployment 16
application
monitoring 22
preventing the use of 23
application discovery 6
Application Metering Agent 6, 16
uninstalling 17
upgrading 17
Application Monitor Configuration
page 24
application monitoring 7, 19
monitorable applications 20
application monitoring period 5
application summary data 5
upload schedule 14
application summary data deleting 14
application usage data
forwarding 13
Audit Plus INI file 15
Auditpls.ini 11
Avg CPU Usage field 13
data
forwarding 13
Denial Count field 12
denial event 5, 25
denied application options
application monitoring
E
event 25
event deleting 14
K
Known As field 12
L
Last Start field 12
legal notice 2
license harvesting 4, 5
Manufacturer field 12
monitorable applications 20
monitored application 5
monitoring an application 19, 22
Month End Summary field 13
Month Year field 12
R
report
creating 8
report deleting 14
Run Count field 12
I
installation
agent 16
Inventory Solution 11
installation parameters 17
internal name 25
Internal Name field 12
inventory data
upload schedule 14
command line 25
company name 25
copyright 2
correlating data 11
creation date of document 2
denial options
file name 25
File Name field 12
file version 25
File Version field 12
forwarding data 13
program monitoring 22
S
scalability 20
start event 5, 20, 25
stop event 5, 20, 25
stop use of application 25
summary data deleting 14
switches 17
T
terminology 5
Total Run Time field 12
trademark 2
U
usage overview 9
User field 12
V
version 2
W
Win16 applications 20
Win32 command-line applications 20
N
normalizing data 11
notice 2
O
23
overview of usage 9
P
parameters 17
patent 2
Peak Memory field 12
prevent use of application 25
preventing the use of an application 23
product name 25
Product Name field 12
product version 2, 25
26