Setting

Definition

Candidate list of images

.The list of images (executable file names) that ESIScan and/or the activeX found that may represent the image that should be specified to watch for usage.  There may or may not be any items in this list, and the items in the list may or may not be the one that must be specified to watch.  The items (if any) in this list are only a guide.  The best way to determine which image to watch is to go to a machine that is running the application, bring up its task list, and see what is listed in the task list.  Use that image name.

Image name (executable)

The image name, exactly as spelled when it is seen in the machine's task list when running, to watch.  When watching web-based applications, enter the image name(s) of the browser(s), each separated from the other by a semi-colon.  For example, iexplorer.exe;firefox.exe;chrome.exe

Window caption to match

When monitoring usage on web-based applications, enter the title of the window (or portion thereof) to match in order to uniquely identify when the application is being used.  Also, when monitoring usage on web-based applications, make sure you specify all possible web browser images, semi-colon-separated, in the Image Name setting.  This tells the usage monitor to find the windows being controlled by any one of the images and look at the window captions to see if they match the caption entered here.

Fire this workflow when usage falls below ...

Base on minimum usage criteria entered, fire this workflow whenever usage for a given authorization falls below the criteria.

Create one workflow per authorization record

When a workflow has been specified to be fired, it can be set to create only one workflow for all authorizations that fall below the specified usage, or it can be set to fire one workflow for every authorization.  Leaving this box unchecked will cause only one workflow to be created for all matching authorizations.  When one workflow is created for all matching authorizations, a CSV file is attached to the workflow thread that contains all authorizations that matched the criteria.  This can be used as a report and can be sent to various recipients as specified by the workflow.   When this setting is checked, a single workflow thread will be created for every authorization that matches the low utilization criteria.  This may be used, for example, when automatically notifying users of their low utilization and instructing them on what will happen next (or what they may do).

Harvest on low utilization

If this box is checked, all authorizations that match the low utilization criteria will be staged for harvest.

Fire workflow on low utilization no more frequently

When a workflow is specified to be fired, then workflow threads will be created no more frequently than the number of days specified by this setting.  For instance, if this setting is 30, and a workflow has been fired for a given authorization within the last 30 days, then no workflow will be fired for that authorization at this time, even if the authorization meets the low utilization criteria.  This only applies to workflows (harvest, which is a one-time event, will take place whenever triggered by low utilization)

If this setting is 0, the workflow will be fired each time Consolidate runs for those authorizations meeting the criteria.

Usage type

This specifies which usage type should be used when checking for low utilization. Active means the percentage utilization based on when the user was actually using the monitored title. Loaded means the percentage utilization based on when the watched title was running in the task list.

Consider only this many days in the past

When calculating utilization, go back into the usage log the number of days in the past specified by this setting.  The maximum allowable setting is 90 (which is the maximum length of the usage log).

Minimum usage samples required

Only consider records in the usage log that have at least this many samples when calculating minimum utilization.

Minimum percent utilization required to act

Any record considered based on the other criteria will have the specified action taken (workflow fired and/or harvested) if the specified utilization (active or loaded) is below the number entered here.

NOTE:  All authorizations for a given asset or user (depending on how the authorization is assigned) for a suite must meet the criteria before the specified action will be taken.  For example, if Access, Excel, and Word are all being monitored, and all three have been set to be part of the Office suite per the MSL settings, then all three authorizations for a given user or asset must meet the minimum criteria before action will be taken.  And, when action is taken, it is taken against the corresponding suite's authorization record - not any of the individual components' authorization records.  In the case of this example, if harvesting is specified as an action to take, then Office will be harvested, not Word, Excel, or Access.