August 6, 2026

NEW | New waste toner almost full alert

• Location: Settings > Warnings

We have added the Waste toner almost full alert to enhance monitoring of the supplies for conventional network and USB printers.

With this new alert, you can identify when the ink or toner waste storage compartment is nearing its maximum capacity, allowing you to plan maintenance before the container becomes completely full and interrupts printer operation.

IMPROVEMENT | Version update of the Microsoft .NET Runtime and Microsoft ASP.NET Core Runtime prerequisites

The Microsoft .NET Runtime and Microsoft ASP.NET Core Runtime prerequisites have been updated to version 8.0.29.

IMPROVEMENT | Automatic closure of alerts for blocked printers for monitoring

When a printer is blocked by the monitoring filter:
- open or in processing alerts will be automatically closed;
- new alerts will not be generated.

Alerts originating from stock, even if linked to a blocked printer, will not be automatically closed.

IMPROVEMENT | Automatic closure of alerts for printers that have not communicated for more than 30 days

We have improved the handling of alerts for conventional, network, or USB printers that have not sent data for more than 30 days.

In these cases, open or in processing alerts will be automatically closed.

The following will not be automatically closed:
- Offline printer alerts;
- alerts originating from stock.

APPROVAL | Approved printers

• Network

  • Meters and supplies

    • FUJIFILM APEOS 5330

APPROVAL | Adjusted printers models

• Network

  • FUJIFILM APEOS C3570

DOCUMENTATION | Documentation improvement based on feedback

• Pages: Configure network printer search for the service e Configure USB printer search for the service

Based on feedback sent via the “What did you think of this page?” option, we have added information to the documentation regarding what happens after a printer is excluded from the Supervised printers tab. When performing a new search, the printer may not appear immediately; it may reappear only during the next scheduled synchronization routine, provided there is communication with the device.

IMPROVEMENT | Update to internal libraries and the SDK

We have updated the agent's internal libraries, including the ndd.Agents.Sdk package, which has been updated to version 7.5.1, and the Vanara libraries.

FIX | Duplicate computers due to an invalid UniqueIdentifier

On certain pieces of equipment, the BIOS or WMI firmware returned generic values or placeholders for the UniqueIdentifier (such as 03000200-0400-0500-0006-000700080009 or FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF). When these identifiers were considered valid by the agent, multiple different computers could be registered under the same key, or a single piece of equipment would end up generating duplicate records on the platform.

To fix this, we added validations to `UniqueIdentifierWindowsHelper` to identify and discard GUIDs known to be invalid or placeholders, both in the main flow and in the fallback mechanisms. If the primary source returns one of these invalid identifiers, the agent automatically triggers the fallbacks to search for a valid identifier for the equipment.