Status definitions

The following table lists default compliance statuses for a policies, servers, and device groups.

Icon

Description

 

Compliant

Policy: All rules or items defined in the policy match the actual server configuration.

Servers: Compliance scan ran successfully and the server configuration matches all rules defined in all policies attached to the server.

Device Groups: Compliance scan ran successfully and the percentage of compliant servers is greater than the minimum threshold set in the Compliance Settings option in the Administration pane. By default, the threshold for a Compliant status is 95% of servers in the group. The compliance threshold definitions for Compliant can be modified.

 

Partial Compliance

Policy: One or more rules or items defined in the policy does not match the actual server configuration, due to an exception applied to one of the rules. This applies only to Windows Patch policies.

Servers: Compliance scan ran successfully and the server configuration did not match at least one of the rules defined in any of the policies attached to the server, due to an exception applied to one of the rules. This applies only to Windows Patch policies.

Device Groups: Compliance scan ran successfully and enough servers in the group meet the threshold criteria for Non-Compliance set in the Compliance Settings in the Administration pane, while the rest of the servers in the group are Compliant. The compliance threshold definitions for Partial Compliance can be modified.

 

Non-compliant

Policy: One or more rules or items defined in the policy does not match the actual server configuration.

Servers: Compliance scan ran and the actual server configuration does not match at least one or more of the rules defined in the policy.

Device Groups: Compliance scan ran and enough servers in the group meet the threshold criteria for Non-Compliance set in the Compliance Settings option in the Administration pane to indicate the group is Non-Compliant. The compliance threshold definitions for Non-Compliance can be modified.

 

Scan Failure

Compliance scan was unable to run.

 

Skipped

Server was skipped.

 

Scan Needed

Results undefined. This status can result if a compliance scan was never run (such as on a new installation) or the configuration on the server (or servers in the device group) changed since the last time information was reported to the SA Client.

 

Scanning: The compliance scan is currently running.


No Tests Defined

No compliance policies of this type are attached to the server or all servers in the device groups, including all servers in any sub-groups.