EN
Español
English
Português
    Description of changes and improvements implemented

    Adjusting the ADM Agent Installation Type for Windows

    The Custom Installation option is removed from the ADM Agent for Windows installer. Starting with this release, the Installation Wizard does not present the selection between Full or Custom Installation and continues directly to the start of the installation with the default system path.

    This setting standardizes the installation of the agent on the default path C:\Program Files (x86)\Aranda\Aranda Agent 9\, in order to respect the security models, permission inheritance, and access controls that Windows manages. ADM installers inherit the permissions (ACLs/ACEs) configured in the installation path; a custom path may have permissions that are different from what you expect and lead to inconsistencies in the execution of the agent, its updates, or associated maintenance processes.

    When additional or more restrictive security configurations are needed, they are applied to the infrastructure using the policies and management mechanisms available to Windows, without modifying the agent’s installation path.

    ⚐ Note: Devices that already have the agent installed on a custom path in previous versions retain that path when they receive the automatic update. The path restriction applies only to new installations from the release 9.25.2.

    Excluding USB-connected disks from device rules

    Disk conditions in device rules are evaluated only on disks connected by an internal device bus, such as SATA, NVMe, SAS, or IDE. USB-connected disks, including removable drives and external optical readers, do not trigger these conditions.

    Adjustment applies to conditions Installed hardware and Hardware removed with the values Disk and Logical Disks, and to the condition Disk occupancy percentage, in both total and incremental inventory. This behavior prevents connecting or disconnecting an external drive from running the rule in an unintended manner and generating alerts, mails, or group associations and disassociations that do not correspond to an actual change in the device’s hardware.

    Disks connected by USB are still inventoried and their information is normally consulted in the device detail.

    ⚠ Warning: Already configured device rules that are activated today when you connect or disconnect a USB drive are no longer activated from the version 9.25.2. We recommend that you review existing rules that use disk conditions to confirm that the range is still as expected.

    ⚐ Note: The installed partition condition begins to evaluate correctly in the update incremental inventory. Rules configured with this condition generate the corresponding notifications in that process.

    Disk partitions on Linux and macOS computers

    The ADM agent for Linux and macOS inventories the partitions on each physical disk, information that was only available on Windows computers. In the device detail, tab Hardware > Discs, is queried for each partition, name, size, free and used space, file system, partition type, and encryption.

    Its main characteristics are:

    • The unpartitioned space on each disk is presented as a single partition Unallocated, which adds up spaces of at least 16 MB; smaller spaces are not taken into account.
    • The encryption is identified on the partition: LUKS on Linux and FileVault on macOS, the latter on the APFS container on the internal disk.
    • LUKS-encrypted partitions show the file system of the decrypted volume when it is open; if the volume is closed or contains LVM, the file system is presented as Not Applicable.
    • Linux and macOS file systems are recognized, such as ext4, xfs, btrfs, vfat (EFI partition), exFAT, NTFS, F2FS, and APFS. Swap partitions and partitions that are part of an LVM or RAID group are presented without a file system.
    • macOS takes inventory only for internal physical disks.
    • Logical disks are not duplicated with partitions: on Linux they correspond to data partitions and decrypted volumes from encrypted partitions; on macOS, to the APFS volume with role Date.
    • The free space and percentage of physical disk usage are calculated from its partitions. The same calculation applies to the Disk occupancy percentage of device rules and in views V_CLIENT_DEVICE_DISK_UCMDB and V_AAM_DEVICE.
    • If the space query with the command fails on Linux df, the agent obtains that data by an alternative method of the operating system and logs the error in its log.

    ⚠ Warning: After you update your Linux agent to the version 9.25.2, it is recommended that you run a total inventory on the devices to avoid inconsistencies in the information on the disks. Starting with this release, the serial of the physical disk corresponds to the manufacturer’s serial and not to the identifier in the partition table, so the disk can be presented only once as removed and added. Virtual disks without hardware serial retain the previous value.

    ⚐ Note: On Linux and macOS, free space is only obtained from linked partitions. Unattached, encrypted, and closed partitions, swaps, or partitions that are part of an LVM or RAID group are presented at 100% utilization. See the documentation for details of this limitation.

    Periodic consultation of pending tasks from the Server.

    When the Repserver fails to deliver an action directly to the Conserver, which is common in networks with inbound communication restrictions, the action is pending and the Conserver obtains it in its next query to the Repserver, which is performed every 5 minutes. In this way, the action is executed without the user having to send it again.

    This mechanism applies to the following actions that are executed from the console:

    • Turn on device (Wake on LAN).
    • Creating Agent Distributions.
    • Log Request (Only for Conserver).
    • Changes in the Conserver Configuration, which are saved from ADM Configuration > Communications.

    If the Preserve restarts before completing a pending action, it resumes it on its next query. Actions that remain more than 24 hours without completing are automatically canceled.

    ⚐ Note: The monitoring settings are not part of this mechanism and retain their usual behavior.