Asset Management Releases

We added a new field that shows the last time an asset’s agent reported data. This provides clearer visibility into agent connectivity and helps teams quickly identify devices that may not be reporting properly.

Application Services discovery now includes Linux devices. Services exposed by running software on Linux machines are automatically detected and can be created as Configuration Items.

This feature enables users to filter CIs by identifying properties that are empty or unset, improving data quality visibility and cleanup workflows. It introduces a new filter operator that allows users to explicitly specify whether a field is empty (yes/no), making it easier to surface incomplete records and enforce data consistency. By providing a native way to query missing values directly within existing filtering capabilities, the feature supports auditing, reporting, and operational use cases where completeness of CI attributes is critical.

This feature supports audit use cases by enabling reporting on Windows computers that contain local users with administrative privileges. A new filter, “Has local privileged users,” will be added to the Computers family and exposed in the standard search bar, along with two new columns in the asset Explorer: “Has local privileged users,” which indicates whether the condition is met (empty for non-Windows assets), and “Local privileged users,” which lists the qualifying administrator accounts. The goal is to give auditors a quick, centralized way to identify machines with privileged local access.

We fixed an issue where computer usage time was not displayed in some cases, even though activity had been recorded. Usage information is now shown correctly whenever activity data is available, ensuring accurate visibility into device usage.

vCenter datastore profiles now correctly display storage capacity values from the VMware integration instead of showing 0 MB.

Business Application diagrams now automatically suggest relationships with consumed Application Services, helping you build dependency maps faster and keep them accurate with less manual effort.

We improved how Android devices are named when created in IGAM. Previously, devices were identified using the phone model, which could make it difficult to distinguish between multiple devices of the same model. Devices are now named using their hostname, providing clearer and more accurate identification.