Deploy Agent for End User Devices to Multiple Windows PCs

To mass deploy the Agent on all your Windows devices, run the command line setup (a standard msi file) inside your software distribution system.

Deploy Agent for End User Devices with your software distribution system

The setup package and the extracted Agent files are secure, signed with our certificate. After you set up the Agent, it can communicate securely with the server using the HTTPS protocol on port 443. Learn more about security.

Before you begin

Before performing a mass rollout of the Agent, first test the deployment on selected PCs. Learn more.

To deploy the Agent for End User Devices for Windows, make sure each Windows device conforms to the following minimum system requirements:

Attribute Requirement

Windows operating system

Device must have:

  • (For servers): Windows Server 2016 64-bit, Windows Server 2012 R2 64-bit, or Windows Server 2008 R2 64-bit.

  • (For devices with Agent up to 12.0.x): Microsoft Windows 10, 8.1, or Windows 7 SP1 (with KB3125574) Enterprise / Professional 32-bit and 64-bit (32-bit requires Agent 9.0.6 or later).

  • (For devices with Agent 12.1 or later): Microsoft Windows 11, Microsoft Windows Server 2016 64-bit, or Microsoft Windows Server 2012 R2 64-bit, or Microsoft Windows 10, or Microsoft Windows 8.1, or Microsoft Windows Server 2008 R2 or later 64-bit (Enterprise / Professional), or Windows 7 SP1 (with KB3125574) or later 64-bit (Enterprise / Professional).

Monitored web applications

Agent 11.x can monitor a web (cloud) application running in any of the following Windows browsers:

  • Chromium-based Microsoft Edge version 88 and above.

  • Monitor any web application in any version of Google Chrome released in the past two years. For legacy Agents (on Windows until Agent 9.1.x or on Mac until Agent for Mac 2.3), you must also manually add the Aternity Extension for Chrome to monitor web page load events (WPM) and usage. Without this, Aternity only monitors clicking a link, back, forward, direct URL, HTTP GET and POST events.

  • Monitor only managed applications with custom activities or page load activities (WPM) in Firefox (beta) single process mode versions 38 ESR, 45 ESR or 52 ESR. Contact Customer Services if you have versions 45 ESR or 52 ESR to enable monitoring of custom activities, and to ensure they are compatible with your Firefox.

Agent 12.0.x (unlike Agent 11.x) monitors managed applications with custom activities or page load activities (WPM) in Firefox (beta) version 60.4 and above.


The Agent sends monitoring data to Aternity (including IP v6 for Agent 11 or later) using HTTPS over port 443.


Aternity gathers and stores detailed performance data. To view older data, it displays a condensed summary (aggregated data), like an hourly or daily summary.

The Agent for End User Devices reports data to Aternity once every minute. If its status becomes disconnected and it cannot send data after trying for five minutes, it locally stores up to 50 minutes of retention data in offline mode, and then sends it when it renews its connection.

The device continuously tries to reconnect to Aternity in ever-increasing intervals, after ½ minute, one minute, two minutes, four minutes, eight minutes, 16 minutes, 32 minutes, and if it still fails, the Agent restarts itself and tries again to connect, restarting this cycle again.

Resource usage

A local Agent in Windows typically uses:

  • CPU: Total utilization across all cores approx. 0.12%. For virtual application servers and MS Terminal Server: typically 5-15%.

  • RAM: Approx. 120MB physical memory (private working set). For virtual application servers and MS Terminal Server, add 40MB per session.

  • Storage: Approx. 110MB, plus Agent log files (10MB to log only errors, or up to 740MB for complete logs). In rare support-led troubleshooting cases, log files can reach up to 3GB.

  • Bandwidth: Network traffic load overhead increases by approx. 0.02 kilobytes per second (KBps) incoming to the device, and approx. 0.05KBps reporting data to Aternity.

Microsoft .NET

(For Agent for End User Devices 12.0 or earlier) Device must have Microsoft .NET v4.5 SP1 or later to use security (TLS 1.2).

(For Agent for End User Devices 12.1 or later) Device must have Microsoft .NET v4.6 SP2 or later to use security (TLS 1.2).

Install privileges

You must run the Agent setup with administrator privileges on the device.


  • The Agent must have write access to the registry during the installation and while the Agent is running.
  • The Agent must have permissions to write to the allusersprofile\aternity directory.

Global security policies

Enable and configure accordingly the Global Security Policies such as GPOs to ensure the Aternity Agent is able to inject into the desired monitored application. Aternity HTML hook is needed to monitor any web based application. If Enable third-party browser extensions is disabled, the hook will be unable to inject. This setting must be enabled or a GPO must be created and/or modified to add our hook to the exclusions.


If you deploy antivirus software on devices, exclude the following Agent's Windows processes:
  • %systemdrive%\Program Files (x86)\Aternity Information Systems\Agent\A180AG.exe

  • %systemdrive%\Program Files (x86)\Aternity Information Systems\Agent\A180CM.exe

  • %systemdrive%\Program Files (x86)\Aternity Information Systems\Agent\A180WD.exe

  • %systemdrive%\Program Files (x86)\Aternity Information Systems\Agent\A180RS.exe

  • %systemdrive%\Program Files (x86)\Aternity Information Systems\a180powershellcollector.exe

  • %systemdrive%\Program Files (x86)\Aternity Information Systems\A180Remediation.exe

Exclude the folders, such as:
  • %systemdrive%\Program Files\Aternity Information Systems\

  • %systemdrive%\Program Files (x86)\Aternity Information Systems\

  • %allusersprofile%\Application Data\Aternity\

  • %allusersprofile%\Aternity\

If your enterprise deploys Ivanti (AppSense), configure the exclusion list to add the process called A180AG.exe in the AppSense Application Manager and AppSense Environment Manager.


Aternity on-premise 12.2 requires that devices run Agent for End User Devices 12.2.x or below (Agent 11.0.x, 12.0.x or 12.1.x).

Product Supported Agent for End User Devices
Aternity 12.2

Agent 11.0.x, 12.0.x, 12.1.x, or 12.2.x

Aternity 12.0-12.1

Agent 11.0.x, 12.0.x or Agent 12.1.x

Aternity 11.x

Agent 9.0, 9.1.7, 9.2.x, or Agent 11.0.x

Aternity monitors performance in a wide range of virtual applications and virtual desktops. The virtual servers must be housed in one of the following operating systems:

Attribute Requirement

Virtual server operating system

Windows Server 2016, 2012 R2, 2012, 2008 R2 or 2019.


  1. Step 1 Deploy the Agent as you would normally run a command line installation on devices in your enterprise, using your software distribution system.

    In your software distribution system, select the target group of devices scheduled for update, then run the command line on each target device using the parameters you tested earlier in your batch file. Learn more.

    Deploy Agent for End User Devices with your software distribution system
  2. Step 2 You can verify the Agent is running by checking the device itself or viewing the device in Aternity's dashboards.

    The Agent runs the following processes on Windows:

    • A180AG.exe is the Agent's core process, performing most of the data collection, operations, and configuration.

    • A180CM.exe manages communication between the Agent and Aternity.

    • A180RS.exe runs under the user's name and collects user experience data.

    • A180WD.exe is the Agent watchdog, a Windows service which checks the Agent is functioning and communicating properly with Aternity. If it detects a problem, it restarts the Agent.

    • A180AA.exe is the back end Windows service of the Aternity Recorder. It only records if an end user manually starts the Recorder (when creating a custom activity).

    1. a Go to the Windows Control Panel > Apps & Features or Programs and Features. Search for Aternity and verify it displays the Agent for End User Devices with the correct version number.
      Verify successful setup
    2. b Open a browser and sign in to Aternity.
    3. c Select the device icon in the top bar of any dashboard to view details of your computer.
      Verify the number of monitored devices
  3. Step 3 (Agent 9.0.x or 9.1.x only) To monitor web applications running in the Chrome browser, deploy the Aternity Extension for Chrome.

    Learn more.


    Setup deploys this automatically from Agent 9.2.x or Agent for Mac 2.4. However, it requires that the device is part of the enterprise's domain, and it can download from the Chrome Web store. Just restart Chrome to automatically start monitoring web applications.

    Monitor web applications running in Chrome with the Aternity Extension for Chrome
  4. Step 4 If the Agent for End User Devices did not install successfully, check the log (.log) file in the same directory as the installer files (.msi and .bat files), to search for the following text:
    • You do not have sufficient privileges to complete this installation indicates you must run the installer with administrator privileges. This also applies to the message Non-assigned apps are disabled for non-admin users

      To resolve, close and re-open the command prompt window, remembering this time to right-click and select Run as administrator.

    • Address parsing failed. Invalid protocol indicates the protocol of an Aggregation Server address is incorrect.

      To resolve, edit the batch file and verify the protocol is either http or https.

    • Address parsing failed. EPM URI is invalid indicates the address or port number of an Aggregation Server address is incorrect.

      To resolve, edit the batch file and verify accuracy of the address and port number of the Aggregation Server.

    • same component with higher versioned keyfile exists indicates that you tried to run the fresh setup batch file instead of the batch file dedicated for downgrades.

      If you are downgrading your setup, make sure you activate the downgrade batch file.