Download Agent for End User Devices or Aternity Mobile (Agent Deployment)

You can download the Agent for End User Devices for Windows or the Agent for Mac directly from within Aternity. The Agent for End User Devices monitors end user experience by measuring device and application performance. Furthermore, to monitor mobile apps, you can download the Aternity Wrapper or the Aternity Mobile SDK to embed monitoring functionality into the app.

There are two types of Agent setups:

  • Run a graphical setup to add the Agent to a single computer, or

    Install the Agent for End User Devices on a PC securely (setup and connection)
  • Run a command line setup to mass-deploy the Agent across all devices in your organization.

    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.

Tip

To try a beta version of the Agent which resolves a specific issue, contact the Aternity Beta Team.

Before you begin

Your Aternity username must have the Download Agent Installers privilege, typically granted to the Account Administrator.

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.

  • (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 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 9.x and above 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.

Connectivity

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

Tip

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.

Permissions

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

Antivirus

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

(Legacy naming up to v7.18) Citrix XenApp 6.5, 7.6, 7.8, 7.15, 7.18

(New naming from v7.19) Citrix Virtual Apps 7.19.

Citrix virtual desktop servers

(Legacy naming up to v7.18) Citrix XenDesktop 6.5, 7.6, 7.8, 7.15, 7.18

(New naming from v7.19) Citrix Virtual Desktops 7.19

VMWare Enterprise VDI

VDI support is for VMWare Horizon View up to 8.0. 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.

Azure Windows Virtual Desktop (WVD)

Windows 10 Enterprise multi-session or Windows 10 Enterprise

Procedure

  1. Step 1 Select the Gear Icon > Agent Deployment.
    Access the page to download the Agent for End User Devices or Aternity Mobile
  2. Step 2 Download the Agent setup for your device type, either for a single device or to mass-deploy to multiple devices.
    Select the type of setup to download
    Field Description
    Install on One Device

    Download the graphical setup program which adds the Agent on a single device.

    Mass Deploy

    Download the command line setup program, which you can use in your mass distribution system to deploy to many devices at once.

  3. Step 3 Set up the Agent. Learn more how to deploy Agents
    Install the Agent for End User Devices on a PC securely (setup and connection)
  4. Step 4 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

    Also, exclude the Aternity 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.

  5. Step 5 (For Agent 12.2.0 and later) Update Agents remotely to a newer version if necessary. Learn more.