<< Click to Display Table of Contents >> Navigation:  Modules > Asset Management > Process > Audit > Asset Record Health

The MIE can be set to test the "health" of asset records - essentially scoring each active record based on criteria that is provided via several system settings.

Asset Health is a server-side health check, in that it checks for accuracy and completeness of data as stored in the MIE. Asset Health does not “hit” the workstation. This is in contrast to the ActiveX-detected WDA check that is performed when running certain catchpoint screens. Additionally, the Asset Health report data is batch-generated by a task under Housekeeping; therefore, changes in the asset are not immediately reflected in the Asset Health report.

 
An asset’s health score is computed by:

•        The date the WDA was installed

•        The types of catchpoint screens run, their frequency, and the length of time since they were last run

•        Duplicates in asset number, serial number, and/or computer name

•        Days since scanned

•        Completeness of the record in the assets table of the MIE

 
Specifically, Asset Health checks for:

•        Computer name is missing or duplicated

•        Serial number is missing or duplicated

•        Machine GUID duplicated

•        Last scan date missing or too old

•        WDA Scheduler version missing or incorrect

•        Catchpoint history does not exist or is too old

•        Check asset in registry (or equivalent(s)) catchpoint never run

•        WDA scanner has never been run or has been too long since last run

 
A score is assigned for each condition tested by Asset Health, via settings (described later). An Asset’s health score starts at zero and as conditions are discovered that affect the ITAM health of an asset, the score of each applicable condition is subtracted from the total score. For example, if an asset is discovered to have the same serial number as another asset, the score for the duplicate serial number condition is subtracted from the asset’s total health score.

The more negative the score, the worse the health of the asset record.

Many of the conditions tested have multiple settings for controlling how the test is performed for that condition. For example, if there is a regular scanning catchpoint that should be run at regular intervals, the catchpoint number is set by the AH_CPNO_REQ_REG_1 setting, the number of days between scans is set by AH_CPNO_REQ_REG_1_MIN_DAYS, and the value that should be subtracted from the asset’s health if that test fails is set by AH_SCORE_REQ_CP_1_TOO_OLD (if the test reveals that it has been too long since running that catchpoint) and AH_SCORE_REQ_CP_1_NOT_RUN (if the test reveals that the asset has never been scanned).

In interpreting the asset’s health score, bear in mind that the lower the number of the asset’s health score, the more serious the asset’s conditions are in the ITAM system, and the more important it is to examine that asset to remedy the situation. All conditions are reported in the Asset Health Report.