July 2025

Hello, these are the july 2025 Release Notes of NDD Print, we have a lot of news, and we hope you like it.

Here you can download the latest versions.

See a summary of all updates and click on the links to navigate each one.

NDD Print MF HP 5.30.1

IMPROVEMENTS

• Expanded compatibility of the PostgreSQL database with NDD Print MF Epson

NDD Print MF Epson 5.8.1

IMPROVEMENTS

• Expanded compatibility of the PostgreSQL database with NDD Print MF Epson

FIXES

• IIS security enhancements for Epson NDD Print

NDD Print MF HP 5.30.0

NEW FEATURES

• HP - Integration with Azure AD / Microsoft Entra ID domains

FIXES

• Error saving settings in ACCOUNTING /CSV

• NDD Print MF HP loses the reference of the reader connected to the HP device

NDD Print MF Epson 5.8.0

IMPROVEMENTS

• Compatibility of Epson NDD Print MF with SNMP v3 protocol

NDD Print Host 5.63.3

FIXES

• Full user synchronisation removed all users from NDD Print Portal 360

• SQL database configuration was not saved correctly for one of the databases

NDD Print Host 5.63.2

FIXES

• Failure to send NPL files due to file size

• Black toner load displayed incorrectly for Brother MFC-L5715DW

NDD Print Digital Shift HP 5.3.3

FIXES

• Configuration not being applied when OCR is configured in the scan flow

NDD Print MF Brother 5.11.0

NEW FEATURES

• Removal of background from scanned pages

APPROVALS

• Printers approved for use with the automatic blank page removal feature during scanning (Skip Blank Page)

FIXES

• User receiving INCORRECT PIN message when authenticating on Brother printer

• Error displayed when using the colour to monochrome conversion suggestion policy

• Expired certificate error when adding equipment with BSI accounting

NDD Print Client Ricoh Android 5.13.1 and NDD Print ECT 1.6.4

NEW FEATURES

• Standard user authentication on Ricoh for ScanToFolder

NDD Print MF HP 5.29.3

NEW FEATURES

• NDD HP Printer Deploy: Implementation of centralised management for HP devices

• Information about when the maximum number of documents has been reached.

IMPROVEMENTS

• Do not display the database selection screen when updating NDD Print MF HP

FIXES

• Failure to save CSV accounting folder information to NDD Print MF HP

• Button for deleting documents not working correctly in HP Client

• Error after authentication in NDD Print Client HP or when accessing NDD Print Releaser

• Failure displayed on printer panels with NDD Print MF HP embedded

• NDD print MF HP shows two printers with the same address, one with a failure status and the other with a success status

NDD Print MF HP – 5.30.1

Released on 30 July

Improvement

Expanded compatibility of the PostgreSQL database with NDD Print MF HP

What is the purpose? Previously, NDD Print MF HP was only compatible with PostgreSQL version 16. With this improvement, the module now supports PostgreSQL version 17.

What has been done? The NDD Print MF HP installer has been updated to automatically install PostgreSQL 17 during the module update process if PostgreSQL is selected as the database.

What will be affected? NDD Print MF HP module installer

What is the impact on the environment? When updating the NDD Print MF HP module, the existing PostgreSQL will not be updated automatically. Instead, a new instance of PostgreSQL 17 will be installed.

This approach has been taken to avoid the risk of interference with existing databases, as it is not possible to identify whether the current PostgreSQL is used exclusively by the module or by other customer applications. This is especially important in shared environments, such as those of some service providers

NDD Print MF Epson – 5.8.1

Released on 30 July

Improvement

Expanded compatibility of the PostgreSQL database with NDD Print MF Epson

What is the purpose? Previously, NDD Print MF Epson was only compatible with PostgreSQL version 16. With this improvement, the module now supports PostgreSQL version 17.

What has been done? The NDD Print MF Epson installer has been updated to automatically install PostgreSQL 17 during the module update process if PostgreSQL is selected as the database.

What will be affected? NDD Print MF Epson module installer

What is the impact on the environment? When updating the NDD Print MF Epson module, the existing PostgreSQL will not be updated automatically. Instead, a new instance of PostgreSQL 17 will be installed.

This approach has been taken to avoid the risk of interference with existing databases, as it is not possible to identify whether the current PostgreSQL is used exclusively by the module or by other customer applications. This is especially important in shared environments, such as those of some service providers

Corrections

Strengthening security between IIS and the Epson NDD Print module

How did the problem occur? There was an increase in exposure to vulnerabilities due to the use of the LocalSystem account, which has higher permissions, in addition to the use of the IIS wwwroot folder for authentication.

When did the problem occur? Whenever the Epson NDD Print MF module was installed, because the configured pool used the LocalSystem account and authentication was performed via the IIS wwwroot folder.

What was done to fix it? Security improvements were applied to IIS. The application pool now uses the ApplicationPoolIdentity account, replacing the old LocalSystem account, which had excessive permissions and could grant administrative privileges to attackers. In addition, authentication is now installed directly with the MF module, avoiding the use of the IIS wwwroot folder, which is more susceptible to vulnerabilities.

NDD Print MF HP - 5.30.0

Released on 23 July

New features

Integration with MS Entra ID domains

What is the new feature? The new feature consists of the integration of Microsoft Entra ID domains with the NDD Print suite of solutions, allowing users to log in to the HP NDD Print Client using their Azure AD credentials.

What is the benefit of the new feature? The integration provides a more secure, simplified and seamless authentication experience, in line with modern identity management practices.

How does the new feature work? The new feature allows users to use Microsoft Entra ID for authentication directly on the device panel.

The process works as follows:

1. Authentication Methods: Users will be able to access the system using a PIN or Card, ensuring greater security and convenience.

2. Credential Association: A QR Code will be displayed on the printer panel, allowing the user to associate their PIN or Card with their Microsoft Entra ID account.

Comments? The configuration required to integrate the NDD Print suite with Microsoft Entra ID domains will be carried out in the NDD Print Portal 360 module, replacing the previous model, which used NDD Print Host for on-premises domains. For this type of domain (on-premises), the same procedures for configuring the integration continue.

Corrections

Error when saving settings in ACCOUNTING/CSV

How did the problem occur? When the server was unable to communicate with one of the SMB ports (139 or 445), the application performed a connection test when opening the settings page. If the test failed, the port was disabled and the application automatically selected the other available port. This change was interpreted as a modification, and even if the user had not made any changes to the CSV folder configuration, the application identified a change and displayed a communication error with the Default folder.

When did the problem occur? When trying to apply changes on the Accounting / CSV screen.

Where did the problem occur? When saving the NDD Print MF HP settings

What was done to fix it? The communication test with the SMB ports is no longer performed automatically when opening the settings screen. Now, this test is only performed when there is an actual change in the CSV folder configuration area. If there is no communication with the port when applying the changes, the failure is then logged.

NDD Print MF HP losing reference to the reader connected to the HP device

How did the problem occur? A TimeoutException was thrown in the proxy call to LibOXPDStandard, especially on devices with slower response times (such as .115, for example). This caused an exception that prevented the card registration from being completed as expected. This behaviour was more common when switching between HTTP and HTTPS protocols, causing the card addition flow to not recognise the partialData sent by the printer. As a result, the data was not saved to the database, and the card was not registered.

When did the problem occur? During the processing of the OXPD proxy response, when attempting to register the AccessoryOwnedEvent event again after a failure and when executing the reader addition flow, when the printer sent only partialData instead of allData

Where did the problem occur? The settings previously made in the FormSettings tab were not retained. The system returned to the default settings saved in the database, such as the default reader names.

What was done to fix it? Three actions were taken to resolve the issue:

1. A new handling for TimeoutException was implemented, with the call being resent to the AccessoryOwnedEvent event after failure.

2. The code was adjusted to accept both partialData and allData in the addition flow.

3. The information entered in the FormSettings tab is now compared with the existing data in the database. If they are different, the system validates access to the folder and correctly saves the new data in the database.

Epson NDD Print MF – 5.8.0

Released on 21 July

Improvement

Compatibility of Epson NDD Print MF with SNMP v3 protocol

What is the objective? To integrate the NDD Print MF Epson module with the SNMP v3 protocol, expanding compatibility and security in communication with devices.

What has been done? As a prerequisite, the printer must first be added to NDD Print Host using the SNMP v3 protocol. After this step, the same equipment must be included in the NDD Print MF Epson module.

What will be affected? The NDD Print Epson module

What is the impact on the environment? With the update, the SNMP v3 protocol will be available for use in the module, allowing greater security and control in communication with compatible printers.

NDD Print Host – 5.63.3

Released on 17 July

Fixes

Full user synchronisation removed all users from NDD Print Portal 360

How did the problem occur? During the LDAP synchronisation process, when updating the Host to the latest version, all users were being removed from Portal 360. This was due to a bug related to the search scope based on baseDn, which only used the Active Directory (AD) root DC, performing a single search and disregarding child Organisational Units (OUs).

When did the problem occur? During the LDAP synchronisation process, this incorrect behaviour directly affected the integrity of the data in Portal 360.

Where did the problem occur? In the LDAP synchronisation performed by the Host, it was necessary to review the search mechanism used to ensure the consistency of the information.

What was done to fix it? The NDD Print Host code was adjusted to modify the way the search is performed. Now, when the search base in AD is set to only the root DC, the system automatically starts a search for all child OUs in that domain. With this improvement, when updating NDD Print Host, the data will be synchronised correctly and users will no longer be removed from NDD Print Portal 360 incorrectly.

Corrections

SQL database configuration was not saved correctly for one of the databases

How did the problem occur? When running DBManager and changing the database to the SQL Server option, the NddPrintHostCache database was incorrectly configured with the OLEDB option. This caused the version of NddPrintHostCache to be set to 4 instead of 3, which is the correct value for connections to SQL Server, when changing any other database in DBManager.

When did the problem occur? Whenever the database was changed in DBManager to the SQL Server option.

Where did the problem occur? In DBManager, located inside the installer folder

What was done to fix it? The code was adjusted to ensure that when selecting the SQL Server option, the NddPrintHostCache database version is correctly set to 3, as expected for this type of connection.

NDD Print Host – 5.63.2

Released on 8 July

Fixes

Failure to send NPL files due to file size

How did the problem occur? During the consolidation process, two problems were detected:

1. When NPL files were manually moved to the send folder (FilesToSend), this generated an error when sending to the server.

2. Very large files were not consolidated properly because the Host was unable to process them within a reasonable time, causing the process to slow down or fail.

When did the problem occur?

When NDD Print Host performed the consolidation and sending of NPL files.

Where did the problem occur?

In NDD Print Host, specifically when the service started the process of consolidating and sending NPL files.

What was done to fix it? An automatic check was implemented to identify files larger than 5 MB in the FilesToSend folder. These files are now moved back to the Logs folder, ensuring that they go through the consolidation process before being sent.

The component (DLL) responsible for checking NPL files has been optimised, resulting in a significant performance improvement. For example, a 250 MB file that previously took over a week to consolidate is now processed in about 2 minutes. Smaller files are also processed even faster.

Two new registry keys have been created:

• NPLParallelProcessing: allows you to switch between sequential (one file at a time) and parallel (multi-thread) verification.

NPLFastMerge: allows you to choose whether the optimised DLL will be used.

Both keys have a default value of False, maintaining the current behaviour. Enabling them can significantly speed up the consolidation process in environments with many files, provided that sufficient RAM is available, as parallel mode can increase memory consumption.

Black toner load displayed incorrectly for Brother MFC-L5715DW

How did the problem occur? The toner status did not decrease with use, remaining constantly at 100%.

When did the problem occur? During monitoring of supplies for the Brother MFC-L5715DW model.

Where did the problem occur? When monitoring supplies using NDD Print Host.

What was done to fix it? The location where this information is captured in the device's MIB was adjusted to ensure that the toner status is displayed correctly.

NDD Print Digital Shift HP 5.3.3

Released on July 8

Fixes

Configuration not being applied when OCR is configured in the scan flow

How did the problem happen? Even after configuring a flow in Digital Shift via NDD Print Portal 360 with the OCR option disabled, when accessing it in HP Digital Shift, the OCR option was displayed as enabled by default, disregarding the configuration performed.

When did the problem happen? While using NDD Print Digital Shift on HP printers.

Where was the problem? In NDD Digital Shift Client installed on the printer.

What was done to fix it?

The behavior of the OCR checkbox was adjusted so that:

• The option is enabled only when the flow requires OCR, that is, when configured in NDD Print Portal 360.

• Otherwise, the option will be displayed unchecked, and the list of languages will not be displayed.

NDD Print MF Brother 5.11.0

Released on 8 July

New features

Removal of background from scanned pages

What is the new feature? A new Background Removal Level option has been added to the NDD Print MF Brother settings. This feature allows print jobs to be processed without the background colour layer, effectively removing colours from the backgrounds of printed pages.

What is the benefit of the new feature?

• Greater print clarity: improves text visibility by removing dark or distracting background colours.

• Ink and toner savings: reduces ink or toner usage by eliminating background fills.

• Better for document archiving: results in cleaner, more professional-looking prints, especially important for scanned or archived documents.

• Eco-friendly printing: helps reduce environmental impact through lower consumable usage.

How does the new feature work?

1. Configuration point: the feature can be enabled in Brother MF Print NDD by accessing the Settings menu, under the Scan Settings tab. In this section, there will be the option Background Removal Level, which offers four adjustment levels available for selection.

2. Processing behaviour: When enabled, the printer driver or intermediate processing layer analyses the print job for background colour layers. These layers are filtered or set to white/transparent before reaching the printer.

Approvals

Printers approved for use with the automatic blank page removal feature during scanning (Skip Blank Page)

Approved models

• Brother – 20 series

  • MFC-J5945DW

  • MFC-J6945DW

  • MFC-J6947DW,

  • MFC-J6997CDW

  • MFC-J6999CDW

• Brother – 24 series

  • MFC-J5955DW

  • MFC-J6955DW

  • MFC-J6957DW

  • MFC-J6959DW

  • MFC-J7500CDW

  • MFC-J7600CDW

  • MFC-J7700CDW

• Brother – 29 series

  • ADS-4700W

  • ADS-4900W

Corrections

User receiving INCORRECT PIN message when authenticating on Brother printer

How did the problem happen? When attempting to authenticate on the printer, the user received the error message: ‘Incorrect PIN’. However, authentication tests performed using the Troubleshooting tool were successful

When did the problem happen? When the user authenticated using their PIN.

Where was the problem ? In the Brother NDD Print Client

What was done to fix it? The Common. component version was updated. The old version had a parser error when the user name contained the ‘_’ (underscore) character. This limitation has been fixed in the new version of the component.

Error displayed when using the colour to monochrome conversion suggestion policy

How did the problem happen?

The conversion from colour to monochrome worked correctly in the following situations:

• When performed manually using the advanced printing option on the printer screen.

• When previously configured in the printer properties in NDD Print Releaser, with the option to preselect conversion to mono.

However, when activating the conversion suggestion policy and choosing to convert the document, the following error message was displayed on the printer:

‘Error: Object reference not defined for an instance of an object.’

When did the problem happen? When using the colour to monochrome conversion suggestion policy.

Where was the problem ? In NDD Print Client Brother

What was done to fix it? The object information was lost, so when the info is null, we search for the file in the temp folder that contains the information, targetBilling the file

We identified that the object information was being lost during the process. To work around the problem, we implemented a logic that, when detecting null values, recovers the data from a temporary file (temp), which stores the necessary information — file name: targetBilling.

Expired certificate error when adding equipment with BSI accounting

How did the problem happen? When attempting to add new equipment with BSI accounting, an alert about an expired certificate was displayed.

When did the problem happen? When adding equipment with BSI accounting.

Where was the problem ? In the certificate provided by the manufacturer.

What was done to fix it? We contacted the manufacturer to provide a new certificate.

NDD Print Client Ricoh Android 5.13.1 and NDD Print ECT 1.6.4

Released on 3 July

New features

Standard user authentication in Ricoh for ScanToFolder

What is the objective? To improve the user experience in the Scan to Folder work function, as the previous Scan to Folder process required the user to enter their domain credentials for each operation. This procedure made usage slower and impractical, especially in environments with high scan volumes, compromising the user experience.

What has been done? An improvement has been made to the scan to folder (Scan to Folder) functionality, which allows authentication to the destination folder using a default user or proxy, configured and managed centrally by the application, providing greater agility and ease of use on a daily basis.

What will be affected?

A new option has been implemented in the ECT (Embedded Configuration Tool): ‘Enable default user to scan to folder’.

When enabled, three mandatory fields will be displayed to be filled in with the following information:

• Domain

• User

• Pass

This data will be used to access the destination folder, where the scanned jobs will be stored.

What is the impact on the environment? Before the improvement was implemented, users had to manually enter their credentials (username and password) each time they used the Scan to Folder work function. With the new configuration being sent automatically via ECT, this authentication is now performed automatically, eliminating the need to repeat this procedure each time the scan to folder function is used.

NDD Print MF HP 5.29.3

Released on 3 July

New features

NDD HP Printer Deploy: Implementation of centralised management for HP devices

What is the new feature? NDD HP Printer Deploy

This is an intuitive solution that allows IT administrators to configure HP devices directly on the printer screen or through a dedicated portal. The feature centralises the configuration process, making it faster, simpler and more efficient.

What are the benefits of the new feature?

Simplified configuration process: Significantly reduces the number of steps required, making the process faster and more straightforward.

Reduction of manual errors: Automation minimises human error, ensuring greater reliability in print fleet management.

Greater control and efficiency: Centralised deployment provides a broader and more accurate view of devices, facilitating strategic decisions.

Flexibility in administration: The intuitive interface allows for quick and customised adjustments, adapting to different scenarios and operational needs.

Key features

With the new functionality, you will be able to:

• Direct configuration on the device or portal: Perform essential configurations, such as defining the server IP and other settings, directly on the printer screen or via a dedicated portal.

• Profile and group selection: Choose the addition profile and the Releaser group directly on the panel, allowing customisation according to the structure and demands of the IT environment.

• Automatic registration in the system: After configuration, the NDD Print 360 modules (NDD Print MF, NDD Print Client HP and NDD Print Host) will automatically register and integrate the printer, ensuring that all devices are correctly registered and monitored.

Information about when the maximum number of documents has been reached

What is the new feature?

Depending on the equipment model — which implies different screen sizes — an information message will be displayed on the saved documents screen, indicating the limit of retained documents:

1. 4.3-inch screens: limit of 12 documents

2. Other screens: limit of 25 documents

What is the benefit of the new feature?

Before this feature was implemented, due to a hardware limitation — especially related to device memory — when a certain number of documents were retained in the user queue, errors were displayed directly on the printer panel, indicating insufficient memory for the embedded application to function.

With the new feature, the user is now informed in advance when the limit of displayable documents is reached, eliminating the need to wait for the memory failure to occur to understand the problem.

How does the new feature work?

When accessing the saved documents screen, if the number of retained documents reaches the displayable limit, an informative pop-up will appear with the following message:

‘X of Y documents are being displayed. To view the rest, return to the menu.’

This feature ensures that users are aware of the display limitation and know how to access the rest of the documents.

Comments?

As mentioned earlier, it is important to pay attention to the size of the device screen, as this factor directly impacts the limit of documents that can be retained and displayed.

Improvements

Do not display the database selection screen when updating NDD Print MF HP.

What is the objective? Starting with version 5.25.9 of NDD Print MF HP, the database selection screen should not be displayed during the system update process.

What has been done? A validation of the installed version has been implemented so that the database selection option is only displayed when it is really necessary to choose the database.

What will be affected? Check if necessary

What is the impact on the environment? There is no impact for the end user.

In module update scenarios, the database selection screen will no longer be displayed, eliminating a step that was previously presented during the process. This change makes the update simpler and more transparent for the user.

Comments? This change applies only to update scenarios and does not affect new installations or complete reinstallations.

Corrections

Failure to save CSV accounting folder information in NDD Print MF HP

How did the problem happen? During the configuration of version 5.27.4 of NDD Print MF HP, when filling in the destination folder, user and password fields, the system reported that the data had been saved successfully. However, when reopening MF, it was observed that the information was not retained — the fields appeared blank, as if they had never been filled in.

When did the problem happen? This behaviour was observed in environments where NDD Print MF HP was configured to perform print accounting using CSV files.

Where was the problem ? The failure occurred in the NDD Print MF HP module, specifically in the SETTINGS menu, on the ACCOUNTING / CSV tab, where the credentials and folder path were entered.

What was done to fix it? Adjusted the detection logic of the accounting model so that model 432 is correctly assigned as the CSV accounting type.

The detection logic for the accounting model was adjusted so that model 432 is correctly assigned as the CSV accounting type

How did the problem happen? When selecting a document retained in NDD Print Client HP and pressing the delete button, no action was taken. The module simply did not respond to the command, and the document remained in the queue.

When did the problem happen? Whenever the user tried to manually delete a document retained directly on the printer panel using the delete button in NDD Print Client HP.

Where was the problem ? In the NDD Print Client HP module embedded in the printer.

What was done to fix it? Fixed the removal message initialisation process, which at certain times was not initialised properly, causing the removal work function to fail.

Error after authentication in NDD Print Client HP or when accessing NDD Print Releaser

How did the problem happen? On several printers, the system displayed the following error message:

‘Error page: Object reference not set to an instance of an object.’

When did the problem happen? The error was displayed immediately after the user entered the authentication PIN or clicked on NDD Print Releaser. The instability was temporarily resolved by restarting all HP MF services on the main server.

Where was the problem ? In the HP NDD Print Client, embedded in the printers.

What was done to fix it? A concurrency issue was identified during multiple simultaneous authentications, which prevented the user authentication session from being created. A control was implemented to manage this concurrency, resolving the issue.

Failure displayed on printer panels with HP MF NDD Print embedded

How did the problem occur? HP X57594 model printers started displaying the following error message on the panel:

‘MIME type not supported: 45.00.64’

Error: ‘MIME type not supported when communicating with http://<server-IP>/nddPrint/Hp/Access/AuthenticationAgent/OmniUi’

When did the problem happen? The error was displayed when the HP NDD Print Client was started on the printer.

Where did the problem happen? On printers that have the HP NDD Print Client installed.

What was done to fix it? A concurrency issue was identified during multiple simultaneous authentications, which prevented the user authentication session from being created. A control was implemented to manage this concurrency, resolving the issue.

NDD print MF HP shows two printers with the same address, one with a failed status and the other with a successful status

How did the problem happen? Printers initially added with a ‘pending’ status that failed and were then successfully added again ended up being kept in duplicate in the system — both the failed and successful versions.

When did the problem happen? After the pending addition of a printer whose status was failure in Fault Monitoring (FM).

Where was the problem ? On printers that have HP NDD Print Client installed.

What was done to fix it? The system backed up pending printers to update the data in case of failure and removed the pending printer when the addition was successful. The fix ensures that previously failed printers are also removed after successful addition, preventing duplication.