Summary

The overview page shows a dashboard with six charts, that reflect the currently selected policy or all policies.

The dashboard is refreshed (recalculated) when:

  • opened or the page is refreshed in the browser
  • a different policy is selected
  • autorefreshed - if the autorefresh switch is enabled
  • the refresh button is clicked

Dashboard charts

On this page:

Overview header pane

The Overview header pane has three rows:

Top row:

  • Policies - shows the number of policies currently enabled, and is a shortcut to the Policies administration pane
  • Online - shows the number of devices currently online, and is a shortcut to the Devices administration pane
  • Last 7 days - shows the number of devices seen in the last 7 days, and is a shortcut to the Devices administration pane

Middle row:

  • Policies drop-down list - filter on All policies or an individual policy, for example selection of the Microsoft SCCM Client Health policy displays a filtered overview
  • Autorefresh switch
  • A refresh button
  • A resize button to display the central panes with and without the Guaranteed State border panes

Bottom row:

  • Devices - shows the number of devices targeted by the selected policy, and is a shortcut to the Devices report pane
  • Compliance state - percentage of devices compliant with the selected policy filter - shortcut to the Devices report filtered on State is Compliant
  • Online - Number of devices online - Shortcut to the Devices report filtered on LastSeen is current
  • Online in the last 7 days - Shortcut to Devices Report filtered on LastSeen is current OR LastSeen is 24h OR LastSeen is 7 days


Device State

The state of devices on which Guaranteed State policies have been deployed is represented in this form:

The user has the ability to drill down into the percentage of failures for each group of device states, for example:

Where the meaning of device states and their precedence is as follows:

StateDescription
UnknownThe device has yet to receive, evaluate or report back on its compliance state for at least one rule
Error

The device has failed to evaluate at least one deployed rule

For example a device may report 97% of deployed rules as Non Applicable, but since 3% of the deployed rules reported as Error this means the whole Device State is marked as Error

Not Applicable

At least one rule deployed to the device is not applicable

For example, this would occur if a Windows specific rule was deployed to a non-Windows device

Non-compliant

At least one rule deployed to the device failed compliance checks

For example in the example above 86% of policy rules are Compliant for the high-lighted device, but since 8% of the rules are Non compliant the state of the whole device is marked as Non-compliant

CompliantThe device passed compliance checks for every deployed policy rule


The drill down navigates to the Devices Report filtered on the selected Device State such as Noncompliant


Device State per Criticality Level

This pane presents a breakdown of the number of devices reporting against each compliance state against the device criticality groups

The drill down navigates to the Devices Report filtered by Device State and Criticality, such as State is Noncompliant AND Criticality is High



Last Seen

This panel shows a summary of when devices last made contact with the Tachyon server, grouped by the criticality level assigned to each device.

The drill down navigates to the Devices Report filtered by LastSeen and Criticality, such as LastSeen is Current AND Criticality is High



Policy Rule Effectiveness

Policy rule effectiveness is the usefulness of policy rules and is represented as follows:


StateDescription
DisabledThe rule has not yet been enabled from the Guaranteed State Rule Administration page, so it is not currently active.
Unassigned

The rule is enabled, but has not been deployed to any devices.

To deploy a rule :

  • The rule must be included in at least one policy.
  • That policy must be assigned to a Management Group containing at least one device.
  • The policy must be deployed.
Ineffective

The rule has been deployed, but no devices have changed their compliance position for this rule in the last thirty days

(The thirty day limit is received from the EffectiveThresholdDays row within the SQL TachyonMaster GlobalSetting table).

Effective

The rule has been deployed and at least one device has changed its' compliance position for this rule in the last thirty days

(The thirty day limit is received from the EffectiveThresholdDays row within the SQL TachyonMaster GlobalSetting table).

Effective plus Ineffective gives the total number of Policy Rules deployed.

The drill down navigates to the Rules Report filtered by Effectiveness, such as Effectiveness is Effective


Policy Rule Status

Policy Rule Status is represented as follows:

A user has the ability to drill down into a segment to examine, for example, exactly which policy rules reported failures across all the devices for which is was deployed:

So in the above example, 37 rules were deployed to a representative sample of 5 devices across the IT estate, giving 185 policy rule deployments of which 59 rule deployments reported Compliance giving an overall Policy Rule compliance of 31.9%

StateDescription
CompliantThe proportion of policy rule deployments for which devices reported compliance.
Non-compliantThe proportion of policy rule deployments for which devices reported non-compliance.
ErrorThe proportion of policy rule deployments for which devices reported rule evaluation failure.
Not Applicable

The proportion of policy rule deployments for which devices reported not applicable.

Typically this would occur for devices to which a deployed rule was applicable only for a different platform, such as deploying Windows Client Health policy rules to macOS devices

Unknown

The proportion of policy rule deployments for which devices have yet to receive, evaluate or report back on their compliance position

In the example above 20% of the policy rule deployments report as Unknown because one of the five devices to which policies have been deployed has remained offline for several days.

After hotfix:

StateDescription
Compliantthe rule check passed.
Non-compliantthe rule check failed.
Errorthe rule could not evaluate its precondition, triggers, check or fix
Not Applicable

the rule precondition did not pass.

Typically this would occur for devices to which a deployed rule was applicable only for a different platform, such as deploying Windows Client Health policy rules to macOS devices

Unknown

the rule hasn’t yet been delivered, evaluated or reported a compliance status.

In the example above 20% of the policy rule deployments report as Unknown because one of the five devices to which policies have been deployed has remained offline for several days.

The drill down navigates to the Rules Report filtered by Policy Rule Status, such as Policy Rule Status is Error



Policy Rule Remediations Last 7 days

This pane shows a daily remediation summary applied to non-compliant devices by policy rules

The drill down navigates to the Remediation Report filtered by Remediation Status and Timestamp period, such as Remediation Status is Fixed and Timestamp in the a given time period.