June 2026 | Help Center

The NDD - Queues Monitor is no longer installed and run as a standalone service; it now functions as a component integrated into the DCA and Cloud Connector agent, which is required for the NDD - Supply Watch service to operate.

With this change, the NDD - Queues Monitor now acts

as an orchestrator between the service and the NDD - Print Processor, and is responsible for its installation, configuration, and management in the print queues. In addition, it ensures that the NDD - Print Processor remains installed in the queues, even if changes occur or removal attempts are made, keeping the environment consistent and ready for the proper functioning of EcoPrint.

The NDD - Print Processor is a library (DLL) installed on all print queues, including those not linked to EcoPrint. Its function is to intercept the flow of print jobs and enable communication with systems, allowing information to be processed without impacting or interrupting printing.

Note

Versions 5.25 through 5.30 of the NDD Print Agent are incompatible with the NDD - Queues Monitor component. To install or update the DCA and Cloud Connector in environments using these versions, you must first update the NDD Print Agent to version 5.31.0 or later. After updating the NDD Print Agent to a compatible version, you can perform the installation or update of the DCA and Cloud Connector as usual.

When removing the DCA and Cloud Connector, the behavior of the NDD - Print Processor depends on whether the NDD Print Agent is present on the machine:

If the NDD Print Agent is not installed, the NDD - Print Processor will be removed from the print queues, and the printers will revert to using the original print processor.
If the NDD Print Agent is installed, the NDD - Print Processor will remain in the print queues.

Warning

The DCA and Cloud Connector (Windows) agent must be updated to version 1.2.23 and the NDD - Supply Watch (Windows) service to version 1.3.0, respectively, as instructed at Update the DCA and Cloud Connector agent, Gateway Connector, or services version via the portal.

Automatic configuration of print queue driver properties (Service: NDD - Supply Watch)

To ensure the solution functions correctly, the NDD - Queues Monitor component will automatically monitor and configure certain settings for the print queue drivers:

Advanced tab in the driver properties:
- Start printing after last page is spooled: enabled.
- Print spooled documents first: enabled.
- Keep printed documents: disabled.
Sharing tab in the driver properties (for shared queues only):
- Render print jobs on client computers: disabled.

Note

The settings apply to all print queues on the computer, including those not linked to EcoPrint or NDD Orbix (printers not registered with or monitored by the platform).

The NDD - Supply Watch service automatically monitors and configures the following parameter:

Advanced tab in the driver properties:
- Enable advanced printing features: disabled. If this option remains enabled, the driver language may change during printing, preventing the savings from taking effect.

Note

This configuration applies to all print queues associated with monitored and managed printers by NDD Orbix.

Warning

Stability improvements (Service: NDD - Thermal Monitor)

We have implemented stability improvements for the service.

Warning

The DCA and Cloud Connector (Windows) agent must be updated to version 1.2.23 and the NDD - Thermal Monitor (Windows) service to version 1.3.8, respectively, as instructed at Update the DCA and Cloud Connector agent, Gateway Connector, or services version via the portal.

June 22, 2026

New features

Monitoring software usage time

We have implemented a new feature that increases visibility into the actual usage of software installed on devices. In addition to identifying which applications are present, the system now displays the daily average hours of use for each software program over the last 30 days.

With this data, software programs are automatically classified and categorized, providing a quick and accurate reading of the level of usage. The total cumulative hours of use for each software program up to the time of the last update is also displayed.

For more information, access View computer inventory and View software inventory.

Warning

The DCA and Cloud Connector (Windows) agent must be updated to version 1.2.22 and the NDD - Software Monitor (Windows) service to version 1.3.0, respectively, as instructed at Update the DCA and Cloud Connector agent, Gateway Connector, or services version via the portal.

Analysis of software usage and performance indicators

We have added a new sub-tab called Indicators to the Software tab in the computer properties, created to increase visibility into application usage and its impact on machine features.

The sub-tab brings together two new views that are essential for in-depth analysis:

Most used software: lists the 10 software programs used for the longest duration during the period, with a classification by usage level.
Usage indicators: shows the percentage of processor and RAM memory usage by software, making it easier to identify applications that affect system performance.

In addition, the Most used software indicator has also been included in the predefined Tactical computer inventory report, allowing you to view this information in a consolidated and strategic manner directly within the reports.

These new indicators strengthen continuous monitoring of the environment, providing greater clarity, accuracy, and capacity for action. Integrated analysis of resource usage and consumption makes IT asset management more strategic, efficient, and secure.

Warning

News in the Computers API

GET /v1/softwares/{computerId}: new response fields added:
- usageTimeStatus: reports the usage status (daily average of actual hours of use over the last 30 days) of the software.
- usageTime: reports the cumulative total of hours the software has been used.
GET /v1/softwares/{computerId}/indicators: new endpoint that returns the percentage of system resources (CPU and RAM) used by each software. Usage metrics are available via the API for up to 90 days.
GET /v1/softwares/{computerId}/usage-time: new endpoint that returns the 10 most-used software titles on the computer over the past 30 days.

News in the Software API

GET /v1/softwares: new response fields added:
- averageUsageTime: reports the daily average of effective usage hours for the software over the past 30 days.
- usageTimeStatus: reports the usage status (daily average of effective usage hours over the past 30 days) of the software.

June 11, 2026

Improvements

Improved traceability of data collection and sending processes (Service: NDD - Printer Monitor)

There was limited visibility into certain stages of alert processing and information sending, making it difficult to perform analyses and diagnostics when unexpected behavior occurred.

During the collection of alerts and the sending of data to the platform, especially in scenarios that required investigation or validation of the processing performed.

We expanded the system’s traceability by adding and improving diagnostic logs at strategic points in the processing. This makes it easier to identify behaviors, analyze incidents, and streamline support and investigation actions.

Warning

The DCA and Cloud Connector (Windows) agent must be updated to version 1.2.21, and the NDD - Printer Monitor (Windows) service to version 1.1.34, as instructed at Update the DCA and Cloud Connector agent, Gateway Connector, or services version via the portal.

Fixes

Active alerts on the equipment were not displayed on the portal (Service: NDD - Printer Monitor)

In some situations, active alerts on the equipment might not be recorded on the portal, generating discrepancies between the equipment’s status and the information displayed on the platform.

This behavior could occur when the equipment was not yet available for processing on the portal or when a temporary failure occurred during the processing of the alert message.

To fix this, we implemented a mechanism to resend opening and closing alerts, making periodic retries while the alert remains active. This increases the reliability of synchronization and reduces the possibility of inconsistencies in the status of alerts displayed on the portal.

Warning

Alerts that had been closed on the equipment were still active on the portal (Service: NDD - Printer Monitor)

In some situations, closed alerts might not be recorded on the portal, generating discrepancies between the equipment’s status and the information displayed on the platform.

This behavior could occur when the equipment was not yet available for processing on the portal or when a temporary failure occurred during the processing of the alert message.

To fix this, we implemented a mechanism to resend closure alerts, making periodic retries until the alert is resolved. This increases the reliability of synchronization and reduces the possibility of inconsistencies in the status of alerts displayed on the portal.

Warning

Agent closes alert incorrectly after a reading error (Service: NDD - Printer Monitor)

In certain situations, active device alerts could be closed incorrectly following a temporary communication failure during monitoring.

This behavior could occur during device monitoring routines when there was an interruption or failure in communication with the device.

To fix this, we adjusted how communication failures are handled during alert monitoring, preventing active alerts from being closed improperly. As a result, alerts remain open until a new valid data collection confirms their resolution.

Warning

Error in SNMP calls (Service: NDD - Printer Monitor)

In certain situations, DCA and Cloud Connector might use incorrect SNMP credentials to communicate with the equipment, hindering the collection of information, including alerts, meters, and supplies.

This behavior could occur during the validation of SNMP configurations, especially in scenarios where the equipment was unavailable or there were network communication failures.

To fix this, we have improved the SNMP configuration validation process, ensuring greater reliability in identifying and using the correct credentials to communicate with the equipment.

Warning

Duplicate alerts and printers (Service: NDD - Printer Monitor)

In specific situations, the same printer could be registered more than once, resulting in duplicate alerts.

This behavior could occur during service startup, when discovery and monitoring routines for equipment not yet registered locally were executed simultaneously.

To fix this, we adjusted the execution control of the collection and monitoring routines, preventing the simultaneous processing of the same equipment. This eliminates the possibility of duplicate records and alerts caused by concurrency during service initialization.

Warning

Computers were incorrectly identified as virtual machines (Service: NDD - Computer Monitor)

Virtual machine detection could generate incorrect results by treating network adapters as evidence of virtualization. In some scenarios, physical computers that had virtual interfaces, host-only adapters, or residual components from virtualization solutions installed were incorrectly classified as virtual machines.

This behavior occurred during the execution of the services’ virtual machine identification routine, specifically during the network adapter analysis step.

To fix this, we removed the virtual machine validation based on network adapters. The classification now considers only the other existing detection mechanisms, significantly reducing the occurrence of false positives caused by virtual interfaces or remnants of virtualization software installed on the equipment.

Warning

The DCA and Cloud Connector (Windows) agent must be updated to version 1.2.21, and the NDD - Computer Monitor (Windows) service to version 1.4.7, as instructed at Update the DCA and Cloud Connector agent, Gateway Connector, or services version via the portal.

Error sending computer data due to failure to identify manufacturer and model (Service: NDD - Computer Monitor)

The agent was unable to identify the computer’s manufacturer and model on certain machines. The system’s primary information source returned empty data for these fields, and the secondary source (motherboard) also did not have this information recorded. Since there was no third alternative for querying, the agent closed the collection cycle with an error, without sending any computer data to the platform.

This behavior occurred persistently in every collection cycle on machines whose firmware does not correctly expose manufacturer and model information via the operating system’s default query sources.

To fix this, we added a third query layer to the computer identification process. When the two previous sources do not return a manufacturer or model, the agent now queries the equipment’s firmware information table (SMBIOS) directly, which is the origin of all system data and is more likely to contain the correct information, even on machines with incomplete operating system configurations.

Warning

June 10, 2026

New features

Generating meter reports for multiple customers

We offer the ability to generate export reports containing meter data from multiple customers in a single file.

With this update, providers who handle billing processes in an ERP system can consolidate data from different customers into a single export, making the import of this information faster, more convenient, and more efficient.

Once generation is complete, the report will be sent as a CSV file to the requesting user’s email address. Depending on the quantity of data processed, sending the report may take a few minutes.

To generate reports, access Generate predefined reports.

Automatic integration of supply demands and equipment movements between NDD Orbix/NDD Print MPS, the ASM portal, and the ERP

We now offer automatic integration of supply demand information and equipment location movements between NDD Orbix/NDD Print MPS, the ASM portal, and the ERP.

With this update, open and completed demands are now automatically synchronized across systems, along with information on items to be received, available balance, location, and projected needs.

In addition, equipment movements between customers made on the ASM portal are now automatically reflected on the equipment’s site in NDD Orbix and NDD Print MPS.

This update reduces manual operational tasks and eliminates the need to develop customized integrations via API, making operations simpler, more agile, and more reliable.

June 08, 2026

Fixes

Failure in message processing by the Computer Insights module

There was a flaw in the processing of integration events received by the Computer Insights module that could result in some messages not being delivered, affecting features that depended on these integrations.

To fix this, we adjusted the processing and routing of integration messages, ensuring that events are received and forwarded correctly. As a result, communication has been restored to normal.

June 03, 2026

Improvements

New columns in the planning and completed demand grids

To make it easier to identify and manage information related to supply demands, we have added new columns to the grids in the Supplies > Demand planning and Supplies > Completed demands menus:

Printer location: displays the address of the printer linked to the demand.
Printer contact phone number: displays the phone number of the printer contact linked to the demand.
Printer contact: displays the name of the printer contact linked to the demand.
Additional fields: displays the information entered in the additional fields for the printer linked to the demand.

Columns can be added through the grid column configuration. For more information, visit Edit grid columns.

In safety demands, these fields will display a dash (-), as this type of demand is not linked to a device.

Last updated: July 15, 2026