Activity Logs

The Activity Logs record the activities performed on the device, such as configuration tasks, device policies execution, and other operations.

Open this node if you want to know the result of an operation you executed on the device. The Activity Log Details tables below provides detailed information about the selected activity log.

Activity Log

Columns Description

Task Name

Displays the name of the configuration task executed.

When a configuration policy, firmware policy, or an embedded policy is executed, the Task Name will be empty for that task.
Activity Type Displays the type of activity the device performed

  • Task Apply: Shows when running an "Apply" Configuration Task.

  • Task Check: Shows when running a "Check" Configuration Task.

  • Task Reboot: Shows when running a "Reboot" Configuration Task.

  • Policy Apply: Shows when a Device Policy ran with "Apply" enforcement type.

  • Policy Check: Shows when a Device Policy ran with "Check" enforcement type
User The user name of the administrator who initiated the activity.
Date The Date and time the activity started.
Results The result of the activity.

  • Success- The activity was completed successfully.

  • Mismatch- At least one attribute in the template is different from the device.

    This is applicable to "Task Check" and "Policy Check" activity types only.

  • Partial Failure- The activity ran but encountered a failure.

    Please see the Activity Log Details for information about the failure.

    If you run a configuration task with firmware that is not compatible with the target device, you will get a "Partial Failure" result. Please use a compatible firmware.

  • Processing- The activity is still running; please wait.

When an activity is clicked from the Activity Log table, the detail of the activity is displayed in the Activity Log Details.

An example of an activity log and details is displayed below.

Activity Log Details

When you click an activity log, the log details of that activity is displayed in the Activity Log Details table. The table has the following columns.

Columns Description
Attribute Name The name of the setting applied to or checked on the device.

For example, an attribute name is displayed as "Printer|System|Duplex Print" when applying an SDP template with Duplex Print: Off as a setting. The Printer is the category, the System is the sub-category, and the Duplex Print is the setting.

The same way the attributes are displayed when running an XDP template.
Template Value The value that is configured in the template.

In the example above, the value is "Off".
Device Value The value retrieved from the device.

If the device's Duplex Print value is set to "Off", then value is "Off".
Results The result of the activity for the attribute.

If the type is "Task Apply" or "Policy Apply", the following will happen.

  1. The template value will be compared to the device value.

  2. If the value matches, it will return "Match" and no action will be taken.

  3. If the value does not match, it will apply the template value to the device.

  4. If the application succeeds, it will return a success; otherwise, failure.

The following are the possible results.

  • Success - The template value is applied successfully to the device.

  • Failure

    • Indicates that the task fails to apply the template value to the device.

      The details are displayed in the Failure Reason column.

    • When the activity type is "Task Reboot", it would return fail if it failed to restart the device.

    • Regardless of the activity type, if the connection to the device fails, it will return a failed result.

  • Match - The template value matches the device value, so nothing is applied.

  • Not Match - The template value did not match the device value.

    This kind of result is only displayed if the activity type is "Task Check" and "Policy Check".

  • Skip - The attribute is not found in the device.

    For example, if the device does not have FAX, applying a fax attribute to it will return 'Skip'.
Failure Reason The details of the error.

Examples:

  • Bad Data - Invalid request data.

  • Access Denied - No client certificate information.