Next Topic

Previous Topic

Book Contents

Network Health Score

The Network Health Score section of the Executive Summary report gives you a summary view of the health and usability of selected machines as a group. The score is broken into categories. Each category is assigned one of five possible percentage scores—typically 100%, 75%, 50%, 25% and 0%—based on a count of a specified criteria. In most cases, you can customize the counts used to assign percentage scores.

  • You can adjust how heavily each category effects the final score by adjusting the weight value for each category. Set the weight to 0 to turn off that category.
  • You can modify the percentage scores assigned the OS Score.
  • You cannot modify the Patch Score criteria.

The final network health score computes the weighted average of the above percentage scores and normalizes them to provide the final percentage score. 100% represents perfect.

For example, say you set one category to 10 and seven other weight categories to 1. The total weight is 17. The percentage associated with the 10 category is multiplied by 10/17 in the final percentage score calculation. In contrast, the percentages associated with the other seven weight categories are multiplied only by 1/17 in the final percentage score calculation.

Note: Ticketing is ignored when calculating the overall network health score.

Patch Score - This score is calculated using the average number of missing patches on each machine. Each machine is scored based on the number of missing patches as follows:

Fully patched

100%

missing 1-2 patches

75%

missing 3-5 patches

50%

missing > 5 patches

25%

unscanned machines

0%

OS Score - Modern operating systems score higher than older operating systems. The overall OS score is an average of each machine's score calculated as follows:

Vista/2008

100%

XP/2003

100%

2000

75%

Mac OS

100%

All others

0%

Note: The OS score weighting can be customized. You can individually weight the OS score given to Vista, 2003, XP and 2000. Enter the % weights (0 to 100) in the four columns normally used for % score. All legacy OSs are given a zero. If you have a large number of legacy OSs deployed, considered turning off the OS score.

Disk Score - Full disk drives can have a severe negative impact on your system. As such disk space used contributes to the overall system score. Disk score is computed as follows:

0% to 65% full

100%

65% to 75% full

75%

75% to 85% full

50%

85% to 95% full

25%

100% full

0%

Ticket Score - Past due tickets assigned to machines are scored as follows:

0 past due

100%

1 or 2 past due

75%

3 to 5 past due

50%

6 to 10 past due

25%

more than 10 past due

0%

Note: The system does not delete tickets when deleting machine IDs. The ticket summary chart includes tickets matching the machine ID / group ID filter. Because no machine data exists for deleted machine IDs, views are not applied to this table.

Event Log Score - Monitored event log alerts represent potential system problems. The number of event log alerts generated by each machine over the specified period of time is scored as follows:

0 alerts

100%

1 to 4 alerts

75%

5 to 10 alerts

50%

11 to 20 alerts

25%

more than 20 alerts

0%

Backup Score - Counts days since the backup last ran. The older the backup is, the lower the score.

0 to 3 days since last backup ran

100%

4 to 7 days since last backup ran

75%

8 to 14 days since last backup ran

50%

15 to 30 days since last backup ran

25%

more than 30 days since last backup ran

0%

Alarm Score - The fewer alarms generated, the higher the score.

0 to 3 alarms

100%

4 to 9 alarms

75%

10 to 19 alarms

50%

20 or more alarms

25%

Security Score - Untreated threats represent potential system problems. The number of untreated threats generated by each machine over the specified period of time is scored as follows:

0 untreated threats

100%

1 to 4 untreated threats

75%

5 to 10 untreated threats

50%

11 to 19 untreated threats

25%

more than 20 untreated threats

0%

Note: The Security Score only displays if you have separately purchased the Kaseya Endpoint Security addon module.

Script Score - Scripts provide a recurring beneficial service to a machine. The more often the script runs, the better shape that machine is likely to be in. The longer it has been since the script ran, the lower the score. The weighted thresholds for the script score count the number of days since the script last ran on the machines. The default values provide the following score:

1

0 to 3 days since script ran

100%

2

4 to 9 days since script ran

75%

3

10 to 19 days since script ran

50%

4

20 or more days since script ran

25%