Set Up Agent for Windows Locally on a PC

To monitor a Windows device, run the setup of the Agent for End User Devices. Start by monitoring a few select PCs to evaluate its features, then you can mass-deploy the Agent to all devices in your enterprise. There are several ways to install the Agent for End User Devices on Windows:

  • Install the Agent for End User Devices locally on a Windows desktop or laptop.

  • On virtual desktops (VDIs), install the Agent inside the desktop image which is dynamically created for every session.

  • Monitor virtual applications (even if you do not monitor the device which runs the virtual session) by installing the Agent on the virtual application server.

Install the Agent for End User Devices on a PC securely (setup and connection)

If you deploy antivirus software on devices, exclude the Agent's Windows processes: A180AG.exe, A180CM.exe, A180RS.exe, A180WD.exe, and A180AA.exe.

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.

Before you begin

Each monitored Windows device must have the following minimum system requirements to install the Agent for End User Devices locally:

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.

  • 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).

Monitored web applications

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

  • 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 any web application in Microsoft Internet Explorer v9, 10 or 11. For legacy until Agent 9.2.3, monitor discovered web apps by disabling IE's compatibility mode (learn more).

  • 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.


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

Device must have Microsoft .NET v4.5 SP1 or later to use security (TLS 1.2).

Install privileges

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


Aternity on-premise 11.x requires that devices ONLY run Agent 9.0, 9.1.7, 9.2.x, or Agent 11.0.

Product Supported Agent for End User Devices
Aternity 11.x

Agent for End User Devices 9.0, 9.1.7, 9.2.x, or Agent 11.0

Aternity 10.x

Agent for End User Devices 9.0.x, 9.1.7 or 9.2.5 ONLY.

Aternity 9.x

Agent for End User Devices 9.0.x ONLY.

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.

The Windows Agent supports virtual devices and/or virtual applications with any of the following requirements:

Attribute Requirement

Citrix virtual application servers

Citrix XenApp 6.5, 7.6, 7.8, 7.15, 7.18, 7.19.

Citrix virtual desktop servers

Citrix XenDesktop 6.5, 7.6, 7.8, 7.15, 7.18, 7.19.

VMWare Enterprise VDI

VDI support is for VMWare Horizon View 6.x and 7.x up to 7.2, and support for 7.15. Aternity does not monitor the ESXi hypervisor. VMWare ThinApp is NOT supported.

Microsoft RDC

Microsoft Remote Desktop Services 6.1, 8.1, 10.0.

Microsoft virtual application servers

Microsoft App-V 4.6 SP3, 5.0, 5.1.


  1. Step 1 Set up the Agent for End User Devices on a single PC using the command line installer, which you can download from the Riverbed support site.

    Copy the batch files to a directory where the logged in user has permissions to create and write files. The setup creates log files in the same directory as the batch file.


    Aternity on-premise 11.x requires that devices ONLY run Agent 9.0, 9.1.7, 9.2.x, or Agent 11.0.

    Product Supported Agent for End User Devices
    Aternity 11.x

    Agent for End User Devices 9.0, 9.1.7, 9.2.x, or Agent 11.0

    Aternity 10.x

    Agent for End User Devices 9.0.x, 9.1.7 or 9.2.5 ONLY.

    Aternity 9.x

    Agent for End User Devices 9.0.x ONLY.

    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.

    1. a Download and open the Agent setup package.

      The command line Agent setup is a standard .msi file (Aternity_Agent_xx.msi), and an accompanying batch file (Aternity_Agent_xx_Install.bat) which contains the default parameters to run the setup.

      Filename Description


      Use this batch file to launch the setup for Windows PCs.


      The core setup file, which a batch file launches.


      Hash file to verify the authenticity of the msi file.


      Use this batch file to launch the setup on a virtual application server.


      Use this batch file to launch the setup to be part of the image of a virtual desktop (VDI).


      Use the settings in this batch file to perform a mass-uninstall of the Agent on multiple devices.

    2. b (Optional) Configure the command line setup by editing its parameters in the batch file (learn more).

      The default settings in the batch file fit most enterprises. However, for VDIs or virtual applications, or for a dedicated proxy server just for Agent connections, configure the parameters manually. Learn more.

      Field Description




      Do NOT change or remove these parameters. They are standard Microsoft .msi parameters required for a successful setup with log files.


      Enter the list of Agent features to deploy on this device. For example, by default it adds:


      Learn more.


      Enter this parameter to specify if this device is a local desktop setup, or a VDI (virtual desktop infrastructure) like VMWare vSphere, or a virtual application server (like Citrix XenApp).

      Learn more


      For Aternity on-premise deployments, set this parameter to the address of your Aternity Aggregation Server. Use https for secure connections (learn more).

      To implement failover to switch to a redundant (set of) Aggregation Servers if the main one fails, enter the redundant server's address after this one (learn more).

      To communicate via a proxy server, add its address as part of the Aggregation Server address.

      Learn more.


      Remove this parameter for Aternity on-premise deployments.

      (Service Providers only) If you are a service provider with a multi-tenant deployment, use this parameter to add the customer's account key. To find the key for each tenant, select the Gear Icon > Accounts > Account Key


      (Optional) Enter this parameter to configure the Agent to report data anonymously, by encrypting personally identifiable information (PII).

      Learn more.


      (Optional) Enter the address of Aternity's Chrome Store to download the Aternity Extension for Chrome, if your enterprise blocks access to the Google Chrome Store.

      Learn more.


      (Optional, advanced) Add this parameter to force the setup to look for a PAC or JS file which routes to different proxy servers.

      Learn more.

    3. c Open a command prompt as an administrator.

      Search for cmd on your computer, right-click and select Run as Administrator.

      Open the computer's command prompt as an administrator
    4. d Navigate to the location of the batch file.
    5. e Run the batch file from inside the command prompt.

      You're done!

  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.