June 2025
Hello, these are the june 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 Sharp 5.4.1
IMPROVEMENTS
NDD Print Client Lexmark 5.16.1
IMPROVEMENTS
NDD Print Host 5.63.1
FIXES
NDD Print MF Xerox 5.16.1
IMPROVEMENTS
NDD Print n-MF Kyocera 4.7.0
IMPROVEMENTS
NDD Print Host 5.63.0
FIXES
NDD Print 360 Mobile iOS 6.3.1
IMPROVEMENTS
NDD Print 360 Mobile Android 6.4.2
IMPROVEMENTS
NDD Print Agent 5.24.15
FIXES
APPROVALS
NDD Print Releaser 5.30.1
FIXES
NDD Print Host 5.62.4
FIXES
NDD Print Sharp 5.4.1
Released on 30 June
Improvements
Enable accounting collection in NDD Print MF Sharp via the HTTPS protocol - port 443
What is the purpose? The main purpose of this update is to enhance communication security in the NDD Print MF Sharp module by adopting the HTTPS protocol. This improvement ensures greater protection when exchanging data between systems and is in line with best practices in information security and the compliance requirements of various customers.
What has been done?
To enable secure communication via HTTPS, the following actions have been implemented:
Creation of specific configuration keys to activate the secure protocol;
Adjustments to IIS (Internet Information Services) to support HTTPS connections;
Inclusion of support for the use of valid digital certificates;
Reconfiguration of printers integrated with the Sharp MF module to use the new protocol.
What will be affected?
BP70M31 family printers: Implementation will be compatible only with devices from this provider, so compatibility must be verified before activation.
Environments with IIS configured: System administrators will need to apply the necessary adjustments according to the new configuration guidelines.
Local integrations: It may be necessary to review the use of digital certificates and network/firewall settings to ensure proper operation under HTTPS.
NDD Print Client Lexmark – 5.16.1
Released on 24 June
Improvements
Maintain compatibility of Lexmark embedded devices with previous versions of NDD Print Host
What is the purpose? To ensure that customers can continue using their current versions of NDD Print Host without the need to immediately update their entire environment, promoting greater flexibility and reducing operational impacts.
What has been done? An update has been made to the Lexmark client module to preserve compatibility with previous versions of NDD Print Host, specifically in cases where the MS Enter ID feature is not in use.
This adjustment ensures that the Lexmark NDD Print Client application installed on printers continues to operate normally even in environments that have not yet been updated to the latest version of NDD Print Host.
What will be affected?
Environments with previous versions of NDD Print Host: will continue to function normally even when using the latest version of Lexmark NDD Print Client.
Use of more advanced features (such as MS Enter ID): will require upgrading to the latest version of NDD Print Host, where Lexmark NDD Print Client must also be updated.
NDD Print Host 5.63.1
Released on June 24
Fixes
Error when switching MS Entra ID domains in NDD Print Host
How did the problem happen? The error occurred in the domains area in NDD Print Host. Specifically, when switching from an MS Entra ID domain to a non-MS EntraID domain, where the GetPrintersV2 route was triggered and the system returned an empty array of printers, even though data was available.
When did the problem happen? After switching domains (from MS Entra ID to a non-MS EntraID domain) and immediately triggering the GetPrintersV2 route.
Where did the problem happen? In the Host module, when using the GetPrintersV2 route.
What was done to fix it? A correction was made to the code responsible for managing the domain context. Now, when switching to a domain other than MD Entra ID, the system ensures that the settings and associated printers are loaded properly, preventing empty arrays from being returned.
Fixes
Part Number not displaying for HP PageWide Color MFP E77650
How did the problem happen? The PartNumber field for supplies was no longer displaying during the monitoring process.
When did the problem happen? During monitoring of supplies for the HP PageWide Color MFP E77650 model.
Where was the problem ? In the supplies monitoring feature performed through NDD Print Host
What was done to fix it? A fix was made to the PartNumber capture mechanism, using the device's MIB, in addition to adjustments to the information handling. As a result, the data is now interpreted and displayed correctly by the system.
NDD Print MF Xerox 5.16.1
Released on 13 June
Improvements
Printer registration by hostname
It is now possible to register printers using the hostname instead of the IP address. This update provides greater flexibility in printer management, as it eliminates the need for changes to IP addresses, making system administration easier.
Benefits:
Greater stability: Eliminating the dependence on static IPs allows for more stable printer administration, even on dynamic networks.
Flexibility: Allows printers to be registered regardless of changes in IP addresses, making the process faster and less prone to errors.
Simplified management: Printer configuration is simpler, especially in environments with frequent network changes.
NDD Print n-MF Kyocera 4.7.0
Released on 13 June
Improvements
Job accounting by e-mail
It is now possible to configure job monitoring via an e-mail box.
Configuring Monitored Job Types
Configure which types of jobs should be monitored by n-MF Kyocera directly from the Settings menu.
Inbox integration for processing job records
The new e-mail accounting option allows n-MF Kyocera to perform historical processing of job records sent to a specified e-mail box.
Encryption of Sensitive Information
To ensure security, sensitive information such as email usernames and passwords is encrypted.
NDD Print Host 5.63.0
Released on 12 June
Fixes
Error in updating the NDD print Host module: DatabaseVersion field in the Parameters table set to value 11
How did the problem occur? During the NDD Print Host update process, it was identified that the version stored in the database was not properly updated. This resulted in failures in the continuity of the update activity, breaking the expected flow.
When did the problem occur? This problem occurred whenever an attempt was made to update NDD Print Host. The inconsistency in versioning prevented the operation from being completed correctly.
Where did the problem occur? The failure directly affected the stability of the NDD Print Host update process, potentially compromising data integrity and the correct functioning of the application.
What was done to fix it? A change was made to the code responsible for the update, ensuring that the version in the database is correctly updated during the process. With this fix, the Host update flow started working normally.
The filtering work function behaved incorrectly when unchecking child OUs in the integration with Active Directory.
How did the problem occur? When selecting a parent OU in the LDAP search filters, all child OUs were automatically selected. Similarly, when deselecting a child OU, the parent OU was also deselected. This logic prevented the individual selection of specific OUs, reducing the accuracy of the configuration — although this was not an error, but rather the expected behaviour of the application.
When did the problem occur? Whenever the user accessed the filters tab within the domain integration properties and interacted with the OU options.
Where did the problem occur? In the LDAP filters tab, used in the domain integration configuration.
What was done to fix it? The marking logic was modified in the code to allow independent selection between parent and child OUs. Now, it is possible to select only some child OUs without affecting the status of the parent OU, and vice versa, providing greater control and accuracy in the configuration of LDAP filters.
NDD Print 360 Mobile iOS 6.3.1
Released on June 11
Improvements
Compatibility with iOS 18
Compatibility with iOS Updated: The app has been adjusted to work correctly on the latest version of iOS available at the time of publication of the NDD Print 360 Mobile iOS module.
Data persistence on the home screen
Now, the information entered on the initial configuration screen (NDD Print Host server IP, NDD Print Releaser server IP, and domain) will be stored, eliminating the need to enter it manually each time you access the app.
Configuration Storage: After filling in the information and logging in, the Host IP, Releaser IP, and domain data will be stored in the cache.
Automatic Filling: The next time you log in, the previously entered data will appear automatically filled in, providing greater convenience to the user.
Manual Editing: If the user wishes to change the data, it can be edited manually before proceeding.
Password Security: The password will not be stored, ensuring the security of the user's credentials.
NDD Print 360 Mobile Android 6.4.2
Released on 11 June
Improvements
Minimum version compatibility
Minimum version requirement:
The minimum supported version of Android has been updated to 8.1 (API 27).
This must be the Android operating system version to use version 6.4.2 of NDD Print 360 Mobile Android.
Data persistence on the home screen
Now, the information entered on the initial configuration screen (NDD Print Host server IP, NDD Print Releaser server IP, and domain) will be stored, eliminating the need to enter it manually each time you access the app.
Configuration Storage: After filling in the information and logging in, the Host IP, Releaser IP, and domain data will be stored in the cache.
Automatic Filling: The next time you log in, the previously entered data will appear automatically filled in, providing greater convenience to the user.
Manual Editing: If the user wishes to change the data, it can be edited manually before proceeding.
Password Security: The password will not be stored, ensuring the security of the user's credentials.
Application layout adjustment
To provide a more intuitive and comfortable experience, adjustments have been made to the application layout, focusing on optimising the usability of physical buttons. The changes aim to make navigation more practical and efficient for the user.
NDD Print Agent 5.24.15
Released on may 12
Fixes
Supply set to “toner” instead of “INK”.
How did the problem happen? The supply type was displayed incorrectly as “Ink”.
When did the problem happen? During monitoring of supplies for the Brother DCP-T820DW model.
Where was the problem? Monitoring of supplies via NDD Print Agent.
What was done to fix it? An adjustment was made to the display of the types, ensuring that they are correctly displayed as “Toner”.
Approvals
Approved printers for collecting counters and network supplies
RICOH-P 501
RICOH-MP 3055
RICOH-IM 4000
RICOH-SP 3710DN
HP-LASER MFP 137fnw
RICOH-P 311
BROTHER-DCP-T820DW
RICOH-IM 430
RICOH-SP 3710SF
NDD Print Releaser 5.30.1
Released on 5 june
Fixes
Error 411 (Length Required) from NDD Print Releaser recorded in Windows events
How did the problem happen? Error 411 (Length Required) was frequently recorded in Windows events.
When did the problem happen? The error was logged when NDD Print Releaser made a call without specifying the length in the header.
Where did the problem happen? The occurrence was logged in Windows event logs.
What was done to fix it? The call length was added to the header, fixing the problem.
NDD Print Host 5.62.4
Released on 3 june
Fixes
HostMsEntraIdIdentityToken not being updated when changing company in the NDD Print Host installation
How did the problem happen? The error occurred when switching companies in NDD Print Host, preventing HostMsEntraIdIdentityToken from being updated properly.
When did the problem happen? The error occurred when switching companies, specifically when triggering the call, resulting in the token not being updated.
Where did the problem happen? It occurred in NDD Print Host, affecting the identity token update process.
What was done to fix it? An update was made to the source code, directly addressing the identified problem, ensuring that HostMsEntraIdIdentityToken is correctly updated when switching companies.
NDD Print Client Ricoh not displaying all domains added to NDD Print Host
How did the problem happen? When requesting domains for the NDD Print Host, the embedded devices received only some domains, instead of all available ones.
When did the problem happen? The problem occurred when the embedded devices requested domains from the NDD Print Host, causing an incomplete response.
Where did the problem happen? The failure manifested itself directly on the embedded devices, affecting the proper receipt of domains.
What was done to fix it? An adjustment was made to the NDD Print Host code, ensuring that all integrated domains available are returned to the embedded devices, eliminating the previous restrictions.
Brother DCP-L5512DW printer registering colour meters
How did the problem happen? During the monitoring of the meters of the Brother DCP-L5512DW model, the monochrome equipment was incorrectly displaying values for colour meters.
When did the problem happen? The problem was identified in the process of monitoring the meters through the NDD Print Host.
Where did the problem happen? It manifested directly in the counter monitoring interface within the NDD Print Host.
What was done to fix it? An adjustment was made to the presentation of the counters, ensuring that only the totalising and monochrome counters were displayed, shielding the presentation of colour counters.