Key Task: Customize a Dashboard to Analyze Remediation Actions (Advanced)

In order to reduce the number of IT tickets and improve user experience, Aternity developed the Remediation feature. Remediation allows IT help desk personnel to identify issues that can cause problems and remotely fix them before they are escalated. Running remediation actions remotely resolves performance issues on end user Windows devices by one-click reducing the problem-solving time and the risk of human errors. Remediation actions can be triggered automatically based on Service Desk Alerts, manually by IT help desk personnel or from external systems using REST API. For example, identify that a user has low disk space and trigger the Empty Recycle Bin action before end user is out of disk space, or stop Windows service that should not run on the device.

This functionality applies only to Windows end-user devices with Agent 12 or later. Install the Agent for End User Devices locally on a Windows desktop or laptop.

Use the Remediation Actions (Advanced) dashboard to customize the visual representation of all executed remedial actions to investigate and analyze their statuses. For example, if many actions failed, you may want to check the script for errors, if many actions were declined by users, you may want to check if the end user confirmation message is clear enough.

If the data you need for your investigation is not available in the non-advanced Analyze dashboard, use the Advanced version to design your own layout, by customizing and displaying only the data which you need.

This dashboard displays raw data in real time, refreshing every time you access it or whenever you manually refresh the browser page.


Remediation is supported for Windows devices only.

View all executed actions and their states

If you saved this dashboard for later viewing, it opens the main sheet (only) in view mode. To further customize (if you have permission), select Edit.

Field Description
Action Execution Status

The workflow involves writing scripts, adding them to Aternity and then executing remediation actions manually (from the Troubleshoot Device Events dashboard or from the Remediation screen) or automatically (triggered by service desk alerts).

Once the action has been executed, the end user gets a message and has to confirm the operation on the end point. Not necessarily that the action is immediately confirmed, it can happen after some time (for example, if the user is out of the office) or even never (for example, if the user does not want to confirm the operation).

There are several statuses:
  • Completed: The remediation process is completed. Refer to the Action States to learn how it was completed.
  • In progress: The remediation process is running. Refer to the Action States to learn in what stage it is now.

Different states are detailed below in the table.

Action Names Displays the name of the remediation action.

You can change the start time of the data displayed in the dashboard in the Timeframe menu in the top right corner of the dashboard.

You can access data in this dashboard (retention) going back up to 90 days with PII (learn more).

Action States
Completed actions can be of different states:
  • Completed successfully: The remediation has been successfully completed.
  • User declined: The user does not want to run this operation on the device and declined the action.
  • Failed: The script failed for some reason. Examine the Action Output Message to get more information.
  • Rejected by Agent’s signing policy: The action was rejected because of the signing policy predefined for the Aternity Agent.

  • Action Expired: The action did not eventually run during the allowed time period (set in the action definition). It can be that the user was logged out, or did not confirm the notification message, or the Agent for End User Devices was not connected.
  • Action timeout: If the script is running more than five minutes, the Agent for End User Devices stops the action.
Actions that are in progress have different states:
  • Triggered: The remedy action has been sent to Windows monitored device.
  • Agent waiting for user login: A user is not logged in and cannot confirm the action execution.
  • Notification issued to user: A user is logged in and the Agent for End User Devices is waiting for user confirmation to start a remediation.
  • Action running: A user confirmed running a remedy script on the device and the script is running on the Windows monitored device.
Action Output Messages

Displays the output message for the action state.

(For Completed successfully and Failed states only): The output message should be set as part of the script during its creation. In case of failure, the message describes the reason of failure, and in case of success, it brings some additional information about the action. For example, the recycle bin has been cleaned or the Agent has been stopped.

(For Rejected by Agent’s signing policy state only):
  • Signing issue: Script is not signed, or script signature is corrupted - Displayed in case the script is not signed at all or its signature was manipulated.
  • Signing issue: Script signature is not valid - Displayed in case the signature does not match the script.
  • Signing issue: The root certificate is not trusted - Displayed in case the root certificate of the certificate that was used to sign the script is not in the trusted root certification authorities.
  • Signing issue: The certificate is not trusted - Displayed in case the certificate that was used to sign the script is not in the trusted publishers and is not explicitly trusted by the Agent (learn more about trusted certificates).
Action Triggered By

For a manual action - It displays the user name who executed the action. For an automatic action - It displays the name of the SDA alert.

Action Trigger Type

Displays the type of the trigger that started the remediation.


  1. Step 1 Open a browser and sign in to Aternity.
  2. Step 2 Select Main Menu > Analyze > Remediation Actions (Advanced).
    Remediation Actions Dashboard (Advanced)
  3. Step 3 Customize the dashboard by dragging measures and dimensions to the Columns and Rows bar, so that you can compare specific attributes.

    For more information on the full editing capabilities of this dashboard, see View the following training sections:

    • Visual Analytics

    • Calculations

    • Tableau Server

    • How To

  4. Step 4 It is possible to create multiple sheets (widgets) in the advanced custom dashboards.
    Instead of having many custom dashboards with a single section each, you can create a single dashboard with all sections you need. This allows more information to be provided within one dashboard displaying much more holistic view, as well as much stronger analytics by cross filtering between the sheets.
    Create multiple sheets in the same dashboard.
    For more information on how to open multiple dashboard sheets in Tableau, see the Tableau tutorial.

    Timeframe drop-down menu in the top right corner of the screen serves all widgets. Use it to set the required timeframe for each widget if necessary.

    Once you have created several widgets and then a dashboard that uses these widgets, save a new dashboard. Make sure to click Save while focusing on the dashboard (in the bottom of the screen there is a list of all open tabs). Note that if, by mistake, the focus is on a widget, the saved view will display this widget instead of dashboard. Click Edit to make changes.

    Focus on a new dashboard to save it