Previous Releases for Aternity SaaS

See here the full content for Aternity SaaS releases in 2026:

For earlier releases, see

• What's New in Aternity SaaS 2025
• What's New in Aternity SaaS 2024
• What's New in Aternity SaaS 2023
• Releases in 2022 for Aternity SaaS
• Releases in 2021 for Aternity SaaS
• Releases in 2020 for Aternity SaaS
• Releases in 2019 for Aternity SaaS
• Releases in 2018 for Aternity SaaS
• Releases in 2017 for Aternity SaaS
• Releases in 2016 for Aternity SaaS

RELATED LINKS

What's New in Aternity SaaS 2026

Original source

Aternity continuously evolves through frequent updates, delivering a stream of fresh functionality, improved features, and updated dashboards. In addition to our main monthly updates, Aternity introduces new features dynamically throughout the month as part of our agile CI/CD development process. Stay informed about these innovations by regularly checking our live feed (), where new features are promptly listed upon integration. Make it a habit to revisit this page frequently to stay ahead of the curve and explore the latest enhancements to elevate your Aternity experience.

Tip

These features will be rolled out on the SaaS environments as per our release schedule. If you don't see these features in your Aternity console yet, please be patient as your system will be upgraded soon.

This article lists the latest updates to Aternity SaaS in 2026. You can also view Aternity updates from previous years.

New Features and Capabilities Released During May 2026

The scheduled May release provides system maintenance and internal bug fixes to enhance performance and stability.

New Features and Capabilities Released During April 2026

New Advanced Mobile Dashboard

Aternity now includes the Advanced Mobile Multi DS dashboard, offering a flexible, customizable view of the Mobile Application data source. It enables unified analysis of app usage, device attributes, network conditions, and more, allowing you to filter, aggregate, and correlate data in one place.

New Features and Capabilities Released During March 2026

Aternity Module release 26.3 (RC) offers the enhancements for Troubleshoot Device dashboards

• New out-of-the-box Citrix monitoring package, including a set of new data collections and supporting Troubleshoot Device dashboard tab.
  • New Citrix Static Attributes Collection, including:
    • Desktop groups (registry oriented)
    • Catalog Name (the deployed image)
    • Hypervisor Name
    • Desktop Kind (private or shared)
  • New Citrix Monitored Attributes Collection, including:
    • ICA RTT
    • HDX Encode Time
    • Thinwire I/O Average FPS
  • Session Logon Measurement and Breakdown

These metrics are also available in the Advanced Dashboard and through the REST API

• OS Arch detection (Added Arm64)
• Security and performance enhancements

Service Desk Alerts for Mobile Devices Health Events

Service Desk Alerts can now be created using Mobile Devices Health Events. This allows for example to associate runbooks or create ServiceNow tickets automatically to events generated by Android or iOS devices the same way it is done for windows and MacOS. Learn more.

Microsoft Teams solution pack

You can now see a user’s Microsoft Teams call quality in-depth in new dashboards. Search for a given user and view their call quality on the Microsoft Teams Calls tab, then drill-down into any specific call for more details, including relevant business activities and health events that happened during the call.

A new role, View MS Teams package dashboards, controls access to the dashboards and must be granted to users before they can see these screens.

5 new predefined business activities have been added for Microsoft Teams:

• Join Meeting
• Rejoin Meeting
• Share Screen
• Start Video
• We could not connect to the internet

These 5 business activities are the most beneficial for identifying user experience issues during calls that are not directly related to call quality. Repeated occurrences of Join Meeting, Rejoin Meeting, Share Screen or Start Video suggest client-related issues related to joining calls or starting specific streams.

Learn more about predefined activities.

Learn more about MS Teams call quality.

Learn more about MS Teams call details.

Aternity Digital Assistant 24.11.0.174 supports .NET9 and .NET10

Aternity Digital Assistant 24.11.0.174 now supports .NET8 or later.

New Features and Capabilities Released During February 2026

New Release 3.3 of Aternity App for ServiceNow with Interaction support

Aternity ServiceNow integration now supports Interactions, bringing powerful troubleshooting and remediation capabilities earlier into the service workflow. Service Desk Agents can now investigate and resolve user issues directly from Interactions using remediation actions, real-time device data, and quick links to Aternity dashboards. This capability reduces unnecessary incident creation and accelerates time to resolution. Learn More.

New Features and Capabilities Released During January 2026

The scheduled January release provides system maintenance and internal bug fixes to enhance performance and stability.

Original source

The new Agent for End User Devices offers new functionality, features and improvements in performance.

Tip

This release includes all resolved issues starting Agent 12.1.4.

For information about the new features of Agent 12.2.x, see What's New in Agent 12.2.x for Windows.

Deploying This Upgrade

You can deploy the Agent throughout your enterprise to collect data from devices and report to Aternity.

Issues Resolved in This Release

Table 1. Resolved Issues

Description | Resolved in

Security Fix for vulnerability CVE-2023-47470, identified in FFMPEG v 4.1.1. | 12.2.4

Resolved Device Type detection. | 12.2.4

Resolved Network in Use Detection. | 12.2.4

Improved monitor collection during boot. | 12.2.3.73

Resolved an issue of miss calculation of virtual memory usage. | 12.2.3.73

Resolved network traffic monitoring issue in cases of high bandwidth. | 12.2.3.73

Improved UX activity detection when the screen scale is above 100%. | 12.2.3.73

Section 508 of the Rehabilitation Act compliance - In the remediation confirmation message: Section 508 is now supported for Windows 11 devices. | 12.2.3.73

Applied security update: removed and replaced obsolete dependencies. | 12.2.3.73

Aternity Extension for Chrome has been updated to Manifest V3. | 12.2.2.38

A workaround has been enabled for power consumption issues with batteries in laptops with Alder Lake processors. | 12.2.2.38

Section 508 of the Rehabilitation Act compliance - In the remediation confirmation message: Section 508 is supported only for Windows 10 devices. | 12.2.2.38

Security Fix for high severity vulnerability CVE-2022-43997, identified by Jack Ullrich of SpecterOps. | 12.2.2.38

Resolved an issue of reporting Wi-Fi protocol ac/ax names. | 12.2.2

Resolved a case when Windows Event Log monitor was not reporting on certain Windows Logs if another Windows Logs source was larger than 2GB. | 12.2.2

Security Fix for high severity vulnerability CVE-2022-43997, identified by Jack Ullrich of SpecterOps | 12.2.1.146

Microsoft Teams improved performance | 12.2.1

Security updates: removed and replaced obsolete dependencies with latest versions | 12.2.1

Improved Aternity Recorder stability | 12.2.1

Improved Aternity Activity Designer playback stability | 12.2.1

Support for collecting Retransmitted Bytes (Agent latency) in Network Monitoring and displaying in custom advanced dashboards. | 12.2.1

Support for recording activities in Firefox using Aternity Recorder. | 12.2.1

Support for disabling Firefox extension deployment (in this case monitoring of activities in FireFox is not available). | 12.2.1

Resolved a case of remediation action failure if a user confirmation message contains the company logo larger than 64 kilobytes. | 12.2.0

Resolved a case of incorrect license provisioning in Windows Virtual Desktop (WVD) sessions. | 12.2.0

Resolves location mapping issues caused by split-tunneling VPN. | 12.2.0

Improved Recorder ability to record. | 12.2.0

Original source

The new Agent for End User Devices offers new functionality, features and improvements in performance. Be among the first to try Aternity's enhanced monitoring with the new Agent 12.2.

The Agent for End User Devices monitors end user experience by measuring device and application performance. It is a seamless background utility which runs on each monitored device, and reports its data to Aternity.

You can deploy the Agent throughout your enterprise to collect data from devices and report to Aternity.

Before deploying, see the resolved issues.

Deploy Agent to all devices in the organization

Aternity Agent Release States

This section lists different states of Aternity Agent release cycle. The state reflects the stability level of the Agent, and it is not related to functionality. When the Agent of a certain version changes its state (for example, from CA to GA), its functionality remains the same.

Definitions of Release States for Aternity Agent

• Release Candidate (RC) – This is a new Agent version which Aternity intends to make available for customers in the near future. You may request and deploy it to a handful of endpoints to try its features. Please contact Aternity SaaS Admin.
• Controlled Availability (CA) – This is a production-ready, supported Agent with which you may start a limited scale rollout to your organization. It's available upon request. Please contact Aternity SaaS Admin.
• Early Availability (EA) – This is a production-ready, supported Agent with which any customer may start a tiered rollout to their organization. Please contact Aternity SaaS Administration for full deployment confirmation.
• General Availability (GA) – This is a default Agent available for full scale deployment to all environments. For older GA versions, contact Aternity SaaS Admin.
• Beta – This is an Agent version which will not become generally available, but you can request it from the Aternity Beta Team and use it to evaluate new features.

What's New in Agent 12.2.4 (General Availability)

Released for General Availability on June 2024

This release contains the following enhancements:

• MS Teams 2.0 as a managed application: Aternity now supports monitoring MS Teams 2.0 out of the box, including Process Resource Consumption and Desktop Usage Time. Aternity Agent for End User Devices automatically monitors all processes used by MS Teams as a single app, without adding them separately as managed applications.
• Monitoring MS Teams 2.0 Desktop Usage Time: Starting Agent for End User Devices 12.2.4, Aternity monitors Process Resource Consumption and Desktop Usage Time per application by specifying its root process while all its child processes are included implicitly. Agent for End User Devices 12.2.3 and prior versions monitor Process Resource Consumption and Desktop Usage per specific process in Windows.
• Creating business activities for MS Teams 2.0: Starting Agent for End User Devices 12.2.4, customers can create and monitor business activities for MS Teams 2.0 clients.
• Support for Mutual TLS (mTLS): Starting Agent for End User Devices 12.2.4, it is possible to secure data transmission to the Aternity SaaS with Mutual TLS (mTLS). Specify this parameter during deployment of Agent for End User Devices (learn more).
• Support for Cellular networks: Aternity Agent for End User Devices 12.2.4 can detect Cellular networks in use. In the Troubleshoot Device dashboard, users can see the type of network connection of the device: WiFi, LAN, or Cellular.
• Support for Windows 10 IoT Enterprise: Certified for use on Windows 10 IoT Enterprise.
• End of Support for operating systems: The new Agent will no longer support the following operating systems: Windows 7, Windows 8, Windows 8.1, Windows Server 2008, Windows Server 2012.
• Enabler monitor: Teams 2.0 activities do not require an enabler. The old enabler monitor can be deleted.

View bug fixes in this release.

Original source

13.2.0 is an APM Agent GA release. This release contains bug fixes and several security enhancements for the APM agent, including:

• APM Agent Apache Log4j Vulnerability (Issue ID: APMDEV-8243)
• Truncated ps_ef output in agent diagnostic bundle when generated from APM AS (Issue ID: APMDEV-8242)
• POD crashes after APM AS reboot (Issue ID: APMDEV-8216)
• java.lang.ClassCastException - JIDA incorrectly casting DelegatingPreparedStatement to java.sql.Connection (Issue ID: APMDEV-8210)
• Upgrade .NET SDK to 6.0.428 (Issue ID: APMDEV-8201)
• The Agent Details page is not displaying any running processes for the selected device or host (Issue ID: APMDEV-8188)
• Support cgroup v2 to discover containerized applications (Issue ID: APMDEV-8187)
• ProcessDiscovery IllegalStateException due to duplicate keys (Issue ID: APMDEV-8186)
• Change APM Agent Service name from appinternals (Issue ID: APMDEV-8174)
• APM Agent log4j-core vulnerability CVE-2025-68161 (Issue ID: APMDEV-8173)
• APM AS generates Agent bundles incorrectly for devices whose hostnames follow the format like ip-xx-xx-xx-xx.ec2 (Issue ID: APMDEV-8172)
• Added support for LZ4 compression when the .NET Data Aggregator (DA) writes data (Issue ID: APMDEV-8167)
• K8S Java application on Alpine failure - Spring Expression Language runtime failure (Issue ID: APMDEV-8166)
• Operator deployment failure with error - image name riverbed/riverbed-operator:x.x.x returns ambiguous list (Issue ID: APMDEV-8153)
• Add DotNet 9.0 and 10.0 support (Issue ID: APMDEV-8152)
• Thread dump messages in stdout in Java process (Issue ID: APMDEV-8148)
• JVM crash with SIGSEGV after JDK upgrade (Issue ID: APMDEV-8093)
• Upgrade Agent to Jetty 12.x from Jetty 9.x (EOL) (Issue ID: APMDEV-7985)
• Process monikers with double IIS_ prefix (Issue ID: APMDEV-7982)
• Support Ubuntu 22.x for APM Agent (Issue ID: APMDEV-7953)
• Java application shutdown with error socket failed for 127.0.0.1:7073 with error: 24 (Too many open files) (Issue ID: APMDEV-7950)
• Cleanup Registry exceptions appearing in DA-DotNet logs for apps running on Linux (Issue ID: APMDEV-7688)
• JIDARegister.exe breaking APM agent (Issue ID: APMDEV-7672)
• Support SUSE Linux services for APM Agent without requiring insserv-compat (Issue ID: APMDEV-7652)
• Include sestatus or getenforce output (Issue ID: APMDEV-7155)
• Last reboot command output to get system reboot details in log_packager (Issue ID: APMDEV-6901)
• Replace netstat output with ss utility output in diagnostic bundles (Issue ID: APMDEV-6439)

This release also includes the following features and enhancements:

• RHEL 9 and Amazon 2023 support
  The APM 13.2.0 release officially supports system-wide automatic enabling for instrumentation:

  • RHEL 9 support for APM Agent
  • System-wide process injection is unsupported on RHEL 9.x and Amazon 2023
    If systems have already been upgraded from a 13.1.0 agent, you will need to run the following commands this one time to enable the feature:
    sudo /opt/Panorama/hedzup/mn/bin/rpictrl install
    sudo /opt/Panorama/hedzup/mn/bin/rpictrl enable
    Note: RHEL 10 and Ubuntu 22.x+ do not support automatic system-wide enablement for instrumentation in this release.

• Windows Server 2025 and Windows 11 support
  The APM 13.2.0 release officially supports Windows Server 2025 and Windows 11. Windows 11 support is part of APM continued support for new platforms.

Original source

Aternity APM supports instrumenting your application with either APM Native Instrumentation or with OpenTelemetry.

• There are currently two supported deployment modes for Aternity APM Native Instrumentation:

  • With the Agent deployed on your host device. This deployment type also allows for automatic injection of the instrumentation libraries into your application.
  • Agentless mode, where the code instrumentation library is manually added to the application package/container. This mode is often used for Serverless, FaaS, buildpacks, and other environments where auto-injection is not supported and manual application instrumentation is required. Learn more.

• As for OpenTelemetry collection, Aternity OpenTelemetry collector receives spans from the application instrumented with OpenTelemetry libraries, processes the data and sends it to the Aternity APM server. Learn more.

Operating Systems Support

Aternity APM Agent software is supported on the following operating systems:

[Table of supported OS versions and agent support status]

Code Instrumentation Support

Aternity APM can collect transactions and spans by instrumenting.

[Table of supported architectures, versions, and agent support]

OpenTelemetry

Aternity APM OpenTelemetry currently supports spans collection (traces) only. OpenTelemetry metrics and logs support is still under development.

Note

Supportability note: Aternity APM supports the standard protocols to receive spans, however, as this is an open-source library, Riverbed Alluvio does not support the OpenTelemetry library / itself, nor its deployment.

With OpenTelemetry, Aternity APM can collect spans (transactions) from any of the below languages:

• Stable tracing capabilities: C++, Erlang/Elixir, .NET, Go, Java, JavaScript, Python, Ruby
• Alpha, pre-alpha and Beta : PHP, Rust, Swift

Aternity APM OpenTelemetry collector is capable of ingesting spans coming from the OpenTelemetry instrumentation libraries described in this table.

[Table of OpenTelemetry protocols and ports]

Cloud Environments Support

Note

OpenTelemetry can also be used for these environments.

Note

x86_64 images only - ARM Docker images are not supported yet.

Note

Aternity follows RedHat support cycle as described here.

[Table of cloud environment support for Agent 11.x and 12.x]

Cloud Environments Support - Serverless and FaaS Support (Agentless)

Note

OpenTelemetry can also be used for these environments.

[Table of serverless and FaaS environment support]

Riverbed Compatibility and Supportability Notes

If Portal is used in your environment, review the knowledge base article KB 27459 for compatibility issues.

Original source

The APM UI displays Java Management Extensions (JMX) metrics in the Servers/Instances and Custom Metrics tabs. These instructions are for users running instrumented Java applications on Linux, where authentication is required to collect JMX metrics.

Instructions to enable JMX metric authentication are below.

Generate user credentials

Generate the encrypted JMX user credentials using the jmxcreds.sh utility that ships with the APM Agent.

Command format:

/opt/Panorama/hedzup/mn/bin/jmxcreds.sh create --credentials-directory <DIRECTORY> --username <USER> --password <PASSWORD>

Where:

• --credentials-directory: Output directory for the jmxcreds.sh script. Used for the RVBD_JMX_CREDENTIALS_DIR environmental variable below
• --username: JMX username
• --password: JMX username password

Instrumented process configuration

Add environment variables for the Java-instrumented processes to specify the location of the JMX credentials and the configuration details for how the profiler attaches to JMX.

The RVBD_JMX_SERVICE_URL environmental variable

The RVBD_JMX_SERVICE_URL environmental variable attaches JMX to the Java(JVM) application. This connection string is also used in the Java Monitoring & Management Console (JConsole) to connect to a JVM.

Command format:

export RVBD_JMX_SERVICE_URL="service:jmx:rmi:///jndi/rmi://<host>:<port>/jmxrmi"

The RVBD_JMX_CREDENTIALS_DIR environmental variable

The RVBD_JMX_CREDENTIALS_DIR environmental variable defines the credentials directory path the profiler uses to attach to JMX.

Command format:

export RVBD_JMX_CREDENTIALS_DIR=/var/lib/artemis/my-broker/etc/

Restart the instrumented process

Restart the instrumented process to allow the JMX credentials to be loaded by our java instrumentation.

Original source

The Portal™ offers an end-to-end digital experience by enabling you to view data from several products in the Alluvio Suite side by side in a single dashboard. Add the Aternity Data Source to the Portal to view Aternity's data from the past seven days alongside that of other products.

For example, if your users are complaining of slow performance, you can monitor the application's performance on the end user device (Aternity), the network performance (NetProfiler), and the server performance (Aternity APM) all on the same screen, side by side.

View dashboards from different data sources in the Portal

Connect the Portal to the Aternity Data Source

Read more about the Portal in the Portal User Guide > Administrator > Data Source Management > Adding a Data Source.

Tip

You can only view Aternity data for the past seven days.

Before you begin

Aternity supports connection of an Aternity Data Source to Portal™ version .

Procedure

Step 1

Open a browser and sign in to Aternity.

Step 2

Access the Gear Icon > Integration Settings > Portal screen and toggle the switch to On to enable Aternity integration with the portal.

Integration settings for the Portal

Field descriptions:

• Host Name: Displays the base URL to use to access the EUEM Aternity Data Source (or the URL to access the APM Data Source). Make note of this field, required when you add the Aternity Data Source to the Portal.
• Port: Displays the port that Aternity uses to communicate with the Aternity Data Source. Make note of this field, required when you add the Aternity Data Source to the Portal.
• Username/Password: Displays the username and password which you enter in Portal™ to access your Aternity Data Source. The username is specific to your organization, and you cannot change it. Make note of this field, required when you add the Aternity Data Source to the Portal.
• Save: Select to apply the integration.

Step 3

Verify you can access the Aternity Data Source from the Portal server, by going to http:///portal-api/v1/admin/ verify on a machine with a browser in the same subnet as Portal.

Use the Host Name field on the Integration Settings page as the base URL.
Enter the dedicated username and password from Aternity's Integration Settings page to access the Aternity Data Source for Portal.

View the response to your verification request

Possible responses:

• Verified: Displays this single word when you successfully accessed the Aternity Data Source.
• Error during authentication: bad credentials: Displays when the username and password are not recognized as valid Aternity credentials.
• Authorization error: user is not authorized to use this API: Displays when the Aternity username and password are valid but do not have the privileges to use this verify command.
• Other connection errors: If the browser could not access the Aternity data source, configure your proxy server and firewall to allow communication from the Portal server to your Aternity Data Source URL over port 443. If the verification continues to fail, contact for assistance.

Step 4

Access your Portal™ from a browser.

Step 5

Add the Aternity Data Source by selecting Configure > Data Sources > Add.

Add a new data source to Portal

Step 6

Specify the data source's details by selecting Select data source type > Aternity or AppInternal.

Select Aternity or AppInternal as a data source

Field descriptions:

• Use secure communication: Select this option if your Portal connects to the Aternity Data Source over secure port 443.
• Host Name: Enter the base URL of the Aternity Data Source without the protocol. Use the Host Name field on the Integration Settings page as the base URL.
• Port: Enter 443 for secured HTTPS (SSL) communication.
• Username/Password: Enter the dedicated username and password from Aternity's Integration Settings page to access the Aternity Data Source for Portal.

Check the system connected to the Aternity Data Source successfully.

Confirm the Portal successfully connected to the Aternity Data Source

Step 7

Continue by using the predefined Aternity dashboards, or create your own custom panels with Aternity data in the Portal.

Original source

Agent for End User Devices 12.1.x

Agent for End User Devices 12.1.x offers new functionality, features and improvements in performance.

Be among the first to try Aternity's enhanced monitoring with the new Agent 12.1.

The Agent for End User Devices monitors end user experience by measuring device and application performance. It is a seamless background utility which runs on each monitored device, and reports its data to Aternity.

You can deploy the Agent throughout your enterprise to collect data from devices and report to Aternity.

Important

Agent 12.1 setup requires 64-bit Windows 7 SP1 or later, or Windows Server 2008 R2 or later operating system. 32-bit is not supported.

Learn more.

Before deploying, see the resolved issues.

Note

Each Agent release incorporates all functionality from earlier releases (of the same major version 12.1).

This article covers the following sections:

Aternity Agent Release States

This section lists different states of Aternity Agent release cycle. The state reflects the stability level of the Agent, and it is not related to functionality. Each Agent release incorporates all functionality from earlier releases (of the same major version 12.1). When the Agent of a certain version changes its state (for example, from CA to GA), its functionality remains the same.

Definitions of Release States for Aternity Agent

Release Candidate (RC) – This is a new Agent version which Aternity intends to make available for customers in the near future. You may request and deploy it to a handful of endpoints to try its features. Please contact Aternity SaaS Admin.

Controlled Availability (CA) – This is a production-ready, supported Agent with which you may start a limited scale rollout to your organization. It's available upon request. Please contact Aternity SaaS Admin.

Early Availability (EA) – This is a production-ready, supported Agent with which any customer may start a tiered rollout to their organization. Please contact Aternity SaaS Administration for full deployment confirmation.

General Availability (GA) – This is a default Agent available for full scale deployment to all environments. For older GA versions, contact Aternity SaaS Admin.

Beta – This is an Agent version which will not become generally available, but you can request it from the Aternity Beta Team and use it to evaluate new features.

What's New in Agent 12.1.4 (General Availability)

Released for General Availability on 30 December 2021

Agent 12.1.4 does not contain new features, but provides enhancements and bug fixes. It includes all functionality from earlier 12.1.x releases.

Validation Tool

PowerShell scripts can now be tested in the PowerShell Validation Tool without being signed.

Security

For increased security, from now, the Agent runs only signed remediation scripts, and PowerShell execution policy no longer allows Unrestricted scripts. ACTION_EXECUTION_POLICY=Unrestricted is no longer supported.

What's New in Agent 12.1.3.95 (General Availability)

Released for General Availability on August 2021

Agent 12.1.3 includes additional security enhancements on top of earlier 12.1.x releases. And of course it includes all functionality from earlier 12.1.x releases.

Security

Aternity Agent for End User Devices security improvements.

What's New in Agent 12.1.2.90 (General Availability)

Released for General Availability on June 2021

Agent 12.1.2 includes security improvements and other enhancements. It includes all functionality from earlier 12.1.x releases.

Security

Aternity Agent for End User Devices security improvements.

Monitoring Enhancements

Supports monitoring of Java applications published using Java OpenJDK Standard Edition 8 (in addition to previously supported Oracle JDK). OpenJDK is a free and open-source implementation of the Java Platform, Standard Edition.

UI Enhancements

Displays application name and version in English, as reported by Aternity Agent and not in a local operating system language. This affects the Application Usage widget and the Application widget in the Troubleshoot Device dashboard, where we display the app name based on the process name.

Monitoring Enhancements

Supports monitoring of the total size of a physical memory installed on the device. You can analyze this attribute in the Device Details dashboard or view it with REST API DEVICE_INVENTORY (learn more). Not all physically installed memory is available for operating system (for example, some memory is allocated to the Display Driver). In such cases, the recorded physical memory may differ from a usable memory. The new Agent records both values: The Total Physical Memory in addition to the usable physical RAM of the device. For managing your organization inventory, you should analyze the Total Physical Memory (a.k.a Installed Memory); in other cases, you might want to analyze the Usable Memory available for applications running on the device.

What's New in Agent 12.1.1.21 (General Availability)

Released for General Availability on April 2021

Agent 12.1.1.21 includes security improvements. It also includes all functionality from earlier 12.1.x releases.

Security

Aternity Agent for End User Devices security improvements.

What's New in Agent 12.1.1.13 (General Availability)

Released for General Availability on 02 December 2020

This Agent release incorporates all functionality from earlier releases described below in this document as well as all functionality from Agent 12.0.6. In addition, it also includes the following enhancements:

MS Teams Monitoring

(SaaS only) Supports reporting on the scheduled calls in MS Teams (also referred to as Meetings in MS Teams UI).

What's New in Agent 12.1.0.446 (Controlled Availability)

This Agent release incorporates all functionality from earlier releases described below in this document. In addition, it also includes the following enhancements:

Note

This Agent release remains at the Controlled Availability stage and will not be promoted to the General Availability stage. There is another version (see above) that incorporates all functionality from the current release.

Monitoring Enhancements

Supports reporting on user installed applications (per user account, and not only per device).

Recording Enhancements

Supports recording activities in Microsoft's Chromium-based Edge browser.

Recording Validation Enhancements

Supports filtering Incomplete activities in the Recorder’s Validation Summary window. Select to view or deselect to hide the Incomplete activities.

Monitoring Enhancements

For monitored devices, supports monitoring of File Downloads for the files on the white list pages.

Monitoring Web Applications in the New Microsoft Edge

Aternity automatically monitors the performance of web applications in the new Microsoft Edge, a Chromium-based browser. Correlate the performance of custom activities or page load activities with different browsers: Chrome, IE, FireFox, and Chromium-based Edge. Diagnose web application performance issues proactively.

Analyzing Microsoft Teams (SaaS only)

With Agent for End User Devices 12.1, you can monitor Microsoft Teams. To get the Agent, please contact Aternity Beta Team. Aternity provides the new capability to monitor and report on the calls in Microsoft Teams and introduces the new advanced dashboard for analyzing those calls. This dashboard includes many call-specific measurements and advanced attributes. Learn more. Get to know your users' experience with MS Teams for optimizing employees collaboration. Improve meeting audio/video quality in your organization. Learn more about attributes and measurements Aternity collects. Learn how to enable the integration of Aternity with Microsoft Teams.

File Downloads Monitoring in Google Chrome

With Agent for End User Devices 12.1, you can analyze file downloads quality in Google Chrome. Use the new File Downloads (Advanced) dashboard for your analysis. See the file transfer time, speed, or size and its impact on efficiency in your organization. Customize the dashboard to show the relevant information to your business. To get Agent 12.1, please contact Aternity Beta Team Learn more.

Aternity Web Activity Creator (WAC 2.0)

With Agent for End User Devices 12.1, you can monitor the activities created with WAC 2.0. To get the Agent, please contact Aternity Beta Team. The Aternity Web Activity Creator (WAC) enables you to quickly and intuitively create custom activities for web applications directly from the web page. The WAC is an interactive Google Chrome extension that opens as a floating sidebar next to your web page. It offers a simple workflow to create your custom activities all on one PC. With WAC 2.0, you can design and monitor your activities within Internet Explorer in addition to Google Chrome. WAC 2.0 provides extensive collaboration capabilities. It allows different users from the same account to view and edit the same activity. In addition, WAC 2.0 allows indicating the end of a business activity upon multiple events. You can complete an activity on any event or on multiple events you indicate. To do this, apply the And condition. This means that only when all the events completed, then the activity state becomes Complete. You can apply And or Or conditions to complete events.

Enhanced Monitoring

Supports reporting of available PRC information for protected processes (like CPU and IO Read/IO Write, but Memory PRC is unavailable).

Enhanced Monitoring

Supports new attributes, including Battery Capacity Health, BIOS, and SCCM.

Operating System support

Supports 64-bit operating systems only.

Security Protocols

When sending data, the Agent reports securely to Aternity via HTTPS. 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). Note that TLS 1.1 is deprecated.

If you are interested in this functionality, contact Aternity SaaS Admin to get the setup files.

Original source

Agent for End User Devices 12.1.x offers new functionality, features and improvements in performance.
Tip
This release includes all resolved issues from Agent 12.0.x.
For information about the new features of Agent 12.1, see What's New in Agent 12.1.x for Windows (End-of-Support).

Deploying This Upgrade
You can deploy the Agent throughout your enterprise to collect data from devices and report to Aternity.

Known Issues
MS Teams monitoring may cause an increased disk IO activity while calls are made. DEM-7740
On Windows 11, Agent for End User Devices cannot report the correct Server Name and/or IP. Thus, in the advanced dashboards: For Web applications, you may see the domain name instead of the actual Server Name and Server Hostname. For Desktop applications, you may see the IP instead of the actual Server Name and Server Hostname. DEM-7866
The Recorder does not properly work when recording on a device with a non-English operating system using Agent 12.1.3. Please contact Riverbed Support Team for guidance how to resolve the issue. DEM-5963
When monitoring MS Teams on multisession devices (WVD), some calls are missing due to fast reuse of PID. DE24172
Two separate instances of the Agent appear under Installed Applications when installed twice, by running MSI and EXE files, (instead of being upgraded). DE23745
An error message might pop up when uninstalling the Agent 12.1 beta 2. DE23507
Failing to detect the PowerShell scripts timeout in Remediation and other scripts. DE2550 and DE2579

Limitations
Aternity Agent 12.1.3 and later
Recorder may fail to record on certain devices. If this happens, please contact Riverbed Support Team.

Issues Resolved in This Release
Each Agent release includes all fixes from all previous updates.
Security Fix for high severity vulnerability CVE-2022-43997, identified by Jack Ullrich of SpecterOps DEM-14223 N/A 12.1.4.27
Resolved a case where Agent was not reporting MS Teams Group calls. DEM-6621 SF89996 12.1.4
Resolved a case when Agent 12.1.3 fails to record while a device is connected to the Appgate VPN. DEM-7111 SF90240 12.1.4
Resolved a case where Agent 12.1.3 uninstall failed if Recorder was enabled. DEM-6737 N/A 12.1.4
Resolved a case where application installation time was reported in UTC instead of local time zone. DEM-3704 N/A 12.1.4
Resolved a case where PowerShell scripts timeout was not enforced. DEM-2579 N/A 12.1.4
PowerShell scripts can now be tested in the PowerShell Validation Tool without being signed. DEM-2343 N/A 12.1.4
For increased security, PowerShell execution policy no longer allows Unrestricted scripts. DEM-1987 N/A 12.1.4
Resolved a case where Aternity logs in Chrome debugging tool were turned on by default and created additional load on the browser. DEM-2379 SF87020 12.1.4
Resolved a case where System Crash (BSOD) details were not reported. DEM-1753 N/A 12.1.4
Agent security improvements. DEM-6768 N/A 12.1.3.95
Agent security improvements. DEM-5264 N/A 12.1.3.95
Agent security improvements. DEM-2647 SF87284 12.1.2.90
A180AG.exe experienced an unhandled exception when performing the WiFi data collection. (A180AG.exe is the Agent's core process, performing most of the data collection, operations, and configuration.) DEM-1453 N/A 12.1.2.86
Resolved a case of missing calls monitoring and high CPU when using MS Teams on multisession devices (WVD). DE24159 SF86103 12.1.2.76
Resolved a case of an occasional failure in monitoring EventLog on weak VDI devices (devices with low resources compared to the average standard). DE23898 SF85237 12.1.2.76
Resolved a case of an occasional failure in monitoring of virtual network adapters (VPN). DE23947 SF84982 12.1.2.76
Resolved a case of missing device attributes due to multiple reported values (for example, Last Boot could be missing). DE24055 N/A 12.1.2.76
Resolved Registry and Files System namespace usage in PowerShell Scripts to use 64-bit namespace instead of WOW64. Note that the issue does not affect the Validation utility. DE23991 N/A 12.1.2.76
Agent security improvements. N/A N/A 12.1.1.21
(SaaS only) Resolved a case of not reporting on the scheduled calls in MS Teams (also referred to as Meetings in MS Teams UI). N/A N/A 12.1.1.13
Resolved a case when some applications were being reported as device installed applications rather than user applications (installed per user account). DE23744 N/A 12.1.1.13
Resolved a case when deleting local files while canceling remediation actions failed. DE23655 N/A 12.1.1.13
Resolved a case of a memory leak in the Aternity Agent during Network Discovery monitoring. DE23742 N/A 12.1.1.13
Resolved a case of missing reports on MS Teams calls performed on resource constrained machines (for example, virtual machines). DE23854 N/A 12.1.1.13
Resolved a case of security vulnerabilities in Aternity Agent’s Assistant Service. US12625 SF1313694 12.1.0.446
Resolved a case of security vulnerabilities in the Remediation feature. DE23643, DE23683 N/A 12.1.0.446
Resolved a case of a failure to run and get reports on Firefox for WAC designed activities. DE23408 N/A 12.1.0.446
Resolved a case when a cleanup of JAVA_TOOL_OPTIONS failed. DE23566 N/A 12.1.0.446
Resolved a rare case of monitoring failure due to recycling process ID (PID) issues. DE22665 N/A 12.1.0.446
Resolved a case of Agent high CPU consumption due to Microsoft Teams monitoring. DE23347 N/A 12.1.0.397
Temporarily, you cannot open the recorded files. DE23272 N/A 12.1.0.397
Resolved a case of nested Microsoft Teams calls that were not reported: When the second call was answered while the first one put on hold, the second call was not reported. DE23347 N/A 12.1.0.397
Resolved a case of Microsoft Teams calls that were not reported due to users' status (Away, Busy, and others). DE23324 N/A 12.1.0.397
Resolved a case where Microsoft Teams calls were not reported after logging out and logging in again. DE23444 N/A 12.1.0.397
Resolved a case when Agent repeatedly tried to run unsigned scripts. DE23191 N/A 12.1.0.397
Resolved a case where the Agent did not report Microsoft Teams calls with multiple participants. N/A N/A 12.1.0.358
The Agent's A180PowerShellCollector process sometimes crashes when the script encounters unhandled exceptions on unmanaged threads (MS Windows limitation). There is no functional impact on Aternity. DE23297 N/A 12.1.0.358
Resolved a case where the Agent reported the same measurement of the same health event twice. DE21604 SF1318959 12.1.0.358
Resolved a rare case where HTTP authentication through a proxy server failed. It happened only in a rare case where the hostname starts with HTTP like http://http-proxy.defect.com. DE23295 SF1319581 12.1.0.358
Resolved a case where the Agent failed to report the updated type of a device (for example, after changing it from laptop to tablet). DE21872 SF1157077 12.1.0.1348
Resolved a case of a high CPU consumption in Internet Explorer caused by multiple HTTP activities with regex conditions that include wildcards. DE22772 SF1299870 12.1.0.1348
Resolved a case of a missing property in Internet Explorer page destroyed event, which caused some activities to fail. DE20880 N/A 12.1.0.1348
Resolved a case of missing reports for error pages in Google Chrome (with the HTTP error code 4xx or 5xx). DE22279 N/A 12.1.0.1348

Original source

Aternity provides real-time insights and automated remediations for Intel Thunderbolt and WiFi issues.

Riverbed Aternity leverages its Intel partnership to deliver real-time visibility into Thunderbolt™ peripherals and WiFi connectivity, configuration, and performance.

Aternity provides below-the-OS-metrics visibility. Combining Intel’s metrics with Aternity's real-time data collection and analysis, IT can proactively identify and resolve digital experience issues.

Learn more

What's New in the Intel Module 2.50.1 (GA)

This release includes the following enhancements:

Feature Description USB Peripheral Connectivity Errors improvements Now reports USB Vendor name and Product Name in addition to Vendor ID and Product ID

Deploying This Upgrade

Important

Unified Agent is the only way to deploy and distribute the Intel Module 2.50.1 release.

The Intel Module 2.50.1 release requires Aternity Module 25.1.0.13 or higher.

The Riverbed Unified Agent is a versatile container component designed to simplify the deployment, upgrade, and management of Riverbed modules (formerly called as agents) for our valued customers.

With the Unified Agent, you can conveniently deploy different modules (for Windows, Mac, or Linux devices) directly from within the UI, streamlining your workflow and enhancing efficiency.

First, read carefully about software system requirements.

Then, learn how to install the Unified Agent and its module.

Supported Use Cases

This release supports the following use cases:

Field Description USB Peripheral Connectivity Errors Detects connectivity issues with peripherals (such as cameras, mice, and keyboards) and categorizes them by device type and manufacturer Thunderbolt Connectivity Errors Detects connectivity issues with Thunderbolt peripherals Thunderbolt External Screen not Displaying Detects when a user connects their laptop via USB-C to an external display but no output occurs WiFi Disconnected Antenna Detects if a WiFi card in the laptop has one of its antennas disconnected WiFi Suboptimal Driver Property Monitors and remediates when WiFi driver settings on Intel wireless network cards do not align with Intel’s recommended configuration WiFi Bad Coverage Detects when a device has poor WiFi coverage with specific resolutions for home-based and office-based users WiFi Technology Gap Helps network and infrastructure administrators identify access points (APs) that are outdated for the laptop fleet they support. WiFi Roaming Report Provides tracking of all roaming events in the WiFi infrastructure including failures, roaming reasons and RSSI values. WiFi Co-Channel Interference Provides tracking of when laptops determine there is interference on the 5GHz WiFi band with other nearby APs WiFi Non Friendly Channel Usage Provides tracking of when laptops determine there is interference with APs running on optimal 2GHz channels (1, 6 or 11) from access points on non-friendly channels (2-5 or 7-10) WiFi High AP Utilization Identifies when access points are running with high channel utilisation along with the station count and RSSI of laptops connecting to those APs

Issues Resolved in This Release

Description Resolved In Improved reporting of WiFi Bad Coverage event in some edge cases, related to underlying issues in Platform Power State conditions (S3/S4/S5, Suspend, Resume) 2.50.1 All monitors received every event instead of only the module subscribed to it, resulting in increased resource consumption 2.50.1

Known Issues in This Release

Description

When using Aternity Module 25.1.0.13, an Aternity Module that starts while the Intel Module is down won't report Intel events until the next Aternity Module configuration.

When using Aternity Module 25.1.0.13, the Aternity Module may have high CPU consumption due to Intel Module initialization failure following a machine restart.

Release States

This section lists different states of the release cycle. The state reflects the stability level of the module only, and not related to functionality. When the module changes its state (for example, from CA to GA), its functionality remains the same.

Release Candidate (RC) – This is a new version which Riverbed intends to make available for customers in the near future. You may deploy it to a handful of endpoints to try its features.

Controlled Availability (CA) – This is a production-ready, supported module with which you may start a limited scale rollout to your organization.

General Availability (GA) – This is a default module available for full scale deployment to all environments.

Original source

Aternity Agent for Mac offers the ability to gather device metrics and performance of managed and discovered native desktop applications and web applications running on Apple Mac computers. For information about the new features of Aternity Agent for Mac, see What's New in Agent for Mac.

Deploying This Upgrade

You can deploy the Agent throughout your enterprise to collect data from Apple Mac devices and report to Aternity.

Issues Resolved in This Release

• Ignore top process threshold config setting if <=0
• Change the default interval for host metrics from 1 minute to 2 minutes
• App Usage time being reported as more than 24hrs
• Incorrect category and sub-category for device health events (memory pressure, disk health, and so on)
• Agent for Mac 4.3.0 certified for on-premise
• Agent for Mac incorrectly classifying Laptops as Desktop devices
• Agent for Mac 4.2.4 not reporting after macOS 15 upgrade does not fix the permissions on folders
• User space remediations not working
• SoftwareUpdateHistory not working
• Update 3rd party dependencies
• Remove rounding errors in application usage time collection
• Avoid sending WiFi metrics when monitors are disabled
• Numerous minor fixes
• Agent for Mac stops reporting data after macOS Sequoia update
• Agent for Mac is reporting HTTP Status Code not available for all web activities and devices
• Network In Use field reporting LAN incorrectly
• Software update commands possibly stalling macOS updates
• Remediation - Issues with certificate validation/certificate signing
• Remediation signature could not be validated - certificate is not permitted for this usage
• SSID is reported incorrectly as redacted
• Web application for Edge reports Browser as Chrome
• WiFi collector issues with Sonoma 14.4
• Process resource monitor collection/reporting frequency fixes
• More protections against downloading config repeatedly
• Recent software changes showing duplicate uninstall entries
• Remove world writeable permissions on folders
• Mac Agent 4.2.0 reports high boot times
• High memory usage in user collector on Mac Agent 4.2.0
• Correct CPUAttributes, DeviceType for Apple Silicon
• Ensure installer works for usernames with spaces
• Certify 4.2.1 for OnPrem
• Chome extension install fails when installation is managed by MDM
• Agent reports high boot times
• Agent CPU usage spikes
• High UserCollector Memory Usage
• Remediation Scripts fail to access protected folders
• Agent reports incorrect username

Known Issues

• The Agent no longer attempts to install the Chrome extension – this should be done via MDM Configuration Profile.
• To run remediation scripts that access protected folders, the Agent will need to be granted Full Disk Access. Our recommendation is to do this via a PPPC in an MDM Configuration Profile.
• On MacOS Ventura, five background items were added which can be viewed under Settings > General > Login Items (AternityEUECommunicator, AternityEUESystemCollectorUnprivileged, AternityEUESystemCollectorPrivileged, AternityEUEUserCollector, AternityEUEDesktopUsageCollector). Our recommendation is to flag these as managed login items via MDM Configuration Profile.
• The Agent will fail to install if the username of the current user contains spaces.

Original source

Previous Releases for Aternity SaaS

See here the full content for Aternity SaaS releases in 2026:

What's New in Aternity SaaS 2026

For earlier releases, see

• What's New in Aternity SaaS 2025
• What's New in Aternity SaaS 2024
• What's New in Aternity SaaS 2023
• Releases in 2022 for Aternity SaaS
• Releases in 2021 for Aternity SaaS
• Releases in 2020 for Aternity SaaS
• Releases in 2019 for Aternity SaaS
• Releases in 2018 for Aternity SaaS
• Releases in 2017 for Aternity SaaS
• Releases in 2016 for Aternity SaaS

RELATED LINKS

What's New in Aternity SaaS 2026

Original source

Aternity Agent for Mac

Aternity Agent for Mac offers the ability to gather device metrics and performance of managed and discovered native desktop applications and web applications running on Apple Mac computers.
Aternity Agent for Mac works with both Aternity SaaS and on-premise.
About the new Module for MacOS, learn here.

Monitor Macs with the Aternity Agent for Mac

Aternity Agent Release States

This section lists different states of Aternity Agent release cycle. The state reflects the stability level of the Agent, and it is not related to functionality. When the Agent of a certain version changes its state (for example, from CA to GA), its functionality remains the same.

Definitions of Release States for Aternity Agent

• Release Candidate (RC) – This is a new Agent version which Aternity intends to make available for customers in the near future. You may request and deploy it to a handful of endpoints to try its features. Please contact Aternity SaaS Admin.
• Controlled Availability (CA) – This is a production-ready, supported Agent with which you may start a limited scale rollout to your organization. It's available upon request. Please contact Aternity SaaS Admin.
• Early Availability (EA) – This is a production-ready, supported Agent with which any customer may start a tiered rollout to their organization. Please contact Aternity SaaS Administration for full deployment confirmation.
• General Availability (GA) – This is a default Agent available for full scale deployment to all environments. For older GA versions, contact Aternity SaaS Admin.
• Beta – This is an Agent version which will not become generally available, but you can request it from the Aternity Beta Team and use it to evaluate new features.

Enhancements in Agent for Mac 4.5.0 (GA)

Released as General Availability in March 2026
Agent for Mac 4.5.0 provides the enhancements described below:

• Support for jamfconnect to retrieve User Full Name and Email address from the Agent.
• Report OnVPN static attributes.
• Report FreeDiskSpace and TotalDiskSpace static attributes.
• Supports macOS 26 (Tahoe), 15 (Sequoia), 14 (Sonoma) 13 (Ventura).

View resolved issues in this release.

Enhancements in Agent for Mac 4.4.0 (GA)

Released as General Availability in November 2025
Agent for Mac 4.4.0 is a maintenance release that adds support for Aternity Digital Assistant for Mac 1.0 but otherwise includes only bug fixes:

• Supports macOS 26 (Tahoe), 15 (Sequoia), 14 (Sonoma) 13 (Ventura).

macOS 12 (Monterey) is no longer supported.

View resolved issues in this release.

Enhancements in Agent for Mac 4.3.0 (GA)

Agent for Mac 4.3.0 provides the enhancements described below:

• Supports macOS 15 (Sequoia), 14 (Sonoma) 13 (Ventura), 12 (Monterey), 11 (Big Sur)
• New out-of-the-box health events:
  • Low Disk Space
  • Thermal State Health Event
  • Memory Pressure Health Event
  • Battery Health Event
  • Storage Device Health Event
• Custom Device Health Events
  • Detect any arbitrary error condition via shell script and report a new type of health event.

View resolved issues in this release.

Enhancements in Agent for Mac 4.2.4 (SaaS only) (GA)

Agent for Mac 4.2.4 provides the enhancements described below:

• Supports macOS 15.2 Sequoia

View resolved issues in this release.

Enhancements in Agent for Mac 4.2.3 (SaaS only) (GA)

Agent for Mac 4.2.3 is a maintenance release and contains only bug fixes. The Agent includes all functionality from previous Agent releases.

View resolved issues in this release.

Enhancements in Agent for Mac 4.2.2 (GA)

Agent for Mac 4.2.2 is a maintenance release and contains only bug fixes. The Agent includes all functionality from previous Agent releases.

View resolved issues in this release.

Enhancements in Agent for Mac 4.2.1 (RC)

Mac Agent 4.2.1 contains bug fixes. The Agent includes all functionality from previous Agent releases.

View resolved issues in this release.

Enhancements in Agent for Mac 4.2.0 (RC)

Mac Agent 4.2.0 provides the enhancements described below:

• Native support for Apple silicon
• The Agent for Mac is now a full macOS application installed under /Applications
• Feature parity with the 3.7 Agents for Mac
• Supports MacOS 14.1 (Sonoma), MacOS 13.0 (Ventura), MacOS 12.0 (Monterey), 11.0 (Big Sur), and 10.15 (Catalina)
• Supports Chrome extension Manifest V3
• Supports web metrics collection, including web usage and page loads:
  • Web usage reporting
  • Page load monitoring
  • Web page monitoring
  • Web activities

Before deploying, view resolved and known issues in this release.

Enhancements in Agent for Mac 4.0.1 (SaaS only) (GA)

Mac Agent 4.0.1 has been released for general availability and provides new features and enhancements:

• Supports MacOS 13 (Ventura), 12.0 (Monterey), 11.0 (Big Sur), and 10.15 (Catalina)
• Native support for Apple Silicon and Intel chips
• Better performance (CPU and memory) on Apple Silicon and Intel
• Eliminate need on Python for installation
• Eliminate deprecated tools/commands in scripts
• This Agent collects only device metrics. Web usage, page loads and web activities are planned to be part of future releases.

Before deploying, view known issues in this release.

Original source

Aternity continuously evolves through frequent updates, delivering a stream of fresh functionality, improved features, and updated dashboards. In addition to our main monthly updates, Aternity introduces new features dynamically throughout the month as part of our agile CI/CD development process. Stay informed about these innovations by regularly checking our live feed ( ), where new features are promptly listed upon integration. Make it a habit to revisit this page frequently to stay ahead of the curve and explore the latest enhancements to elevate your Aternity experience.

Tip

These features will be rolled out on the SaaS environments as per our release schedule. If you don't see these features in your Aternity console yet, please be patient as your system will be upgraded soon.

This article lists the latest updates to Aternity SaaS in 2026. You can also view Aternity updates from previous years.

New Features and Capabilities Released During April 2026

The scheduled April release provides system maintenance and internal bug fixes to enhance performance and stability.

New Features and Capabilities Released During March 2026

The scheduled March release provides system maintenance and internal bug fixes to enhance performance and stability.

Aternity Module release 26.3 (RC) offers the enhancements for Troubleshoot Device dashboards

New out-of-the-box Citrix monitoring package, including a set of new data collections and supporting Troubleshoot Device dashboard tab. New Citrix Static Attributes Collection, including: Desktop groups (registry oriented) Catalog Name (the deployed image) Hypervisor Name Desktop Kind (private or shared) New Citrix Monitored Attributes Collection, including: ICA RTT HDX Encode Time Thinwire I/O Average FPS Session Logon Measurement and Breakdown These metrics are also available in the Advanced Dashboard and through the REST API OS Arch detection (Added Arm64) Security and performance enhancements

Service Desk Alerts for Mobile Devices Health Events

Service Desk Alerts can now be created using Mobile Devices Health Events. This allows for example to associate runbooks or create ServiceNow tickets automatically to events generated by Android or iOS devices the same way it is done for windows and MacOS. Learn more.

Microsoft Teams solution pack

You can now see a user’s Microsoft Teams call quality in-depth in new dashboards. Search for a given user and view their call quality on the Microsoft Teams Calls tab, then drill-down into any specific call for more details, including relevant business activities and health events that happened during the call.

A new role, View MS Teams package dashboards, controls access to the dashboards and must be granted to users before they can see these screens.

5 new predefined business activities have been added for Microsoft Teams:

• Join Meeting
• Rejoin Meeting
• Share Screen
• Start Video
• We could not connect to the internet

These 5 business activities are the most beneficial for identifying user experience issues during calls that are not directly related to call quality. Repeated occurrences of Join Meeting, Rejoin Meeting, Share Screen or Start Video suggest client-related issues related to joining calls or starting specific streams.

Learn more about predefined activities.

Learn more about MS Teams call quality.

Learn more about MS Teams call details.

Aternity Digital Assistant 24.11.0.174 supports .NET9 and .NET10

Aternity Digital Assistant 24.11.0.174 now supports .NET8 or later.

New Features and Capabilities Released During February 2026

New Release 3.3 of Aternity App for ServiceNow with Interaction support

Aternity ServiceNow integration now supports Interactions, bringing powerful troubleshooting and remediation capabilities earlier into the service workflow.

Service Desk Agents can now investigate and resolve user issues directly from Interactions using remediation actions, real-time device data, and quick links to Aternity dashboards. This capability reduces unnecessary incident creation and accelerates time to resolution.

Learn More.

New Features and Capabilities Released During January 2026

The scheduled January release provides system maintenance and internal bug fixes to enhance performance and stability.

Original source