December 2022
Hello, these are the December 2022 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/Client HP 5.21.9
USB reader showing different readings for the same card (OmniKey, TWN4, DMZ and HP readers) ➜
Failure in the process of adding printers that have a password with the character "_" ➜
Accounting failure on “Scanner” devices without authentication ➜
Accounting failed due to restoring printer factory default template ➜
Accounting failed due to not enabling printer statistics service ➜
NDD Print Client Kyocera 5.7.9
NDD Print Releaser 5.24.0
NDD Print MF/Client Konica 5.7.11
NDD Print Host 5.51.14
NDD Print Agent 5.23.10
NDD Print MF/Client Epson 5.3.2
Problems running NDD Print Releaser "Smart Release" feature ➜
Module installation fails in Windows Server 2008 R2 environments ➜
NDD Print MF/Client HP 5.21.9
Released on December 28
Fixes
Failure during add printer wizard
How did the problem happen? While adding a printer, in the last step of the wizard, the process stopped without completing the addition, causing the service to use the remaining available CPU.
When did the problem happen? During add printer process.
Where was the problem? On NDD Print MF HP Authentication.
What was done to fix it? Improvements were made to the process of registering printers when adding them to NDD Print MF.
Duplicity in accounting
How did the problem happen? In equipment that contained a list of jobs that have already been performed greater than the manufacturer's limit (256 jobs), it generated duplicate accounting.
When did the problem happen? During the accounting data capture process.
Where was the problem? In the accounting service.
What was done to fix it? Improvements in the process of capturing and displaying the list of jobs done by the printer.
USB reader showing different readings for the same card (OmniKey, TWN4, DMZ and HP readers)
How did the problem happen? When the user tried to authenticate using a card in OmniKey, TWN4, DMZ and HP readers, eventually the card registration screen appeared for the user, even with the card already registered.
When did the problem happen? During authentication process using card authentication method with OmniKey, TWN4, DMZ and HP readers.
Where was the problem? On NDD Print MF HP Authentication.
What was done to fix it? The reading process for OmniKey, TWN4, DMZ and HP readers has been improved.
Failure in process of adding configuration of HP readers
How did the problem happen? While configuring HP readers in the NDD Print MF HP Admin interface. When trying to save the configuration, the success message was displayed, but the configurations in the reader were not applied.
When did the problem happen? When trying to save the configuration of HP readers in the Admin interface of the NDD Print MF HP.
Where was the problem? In the NDD Print MF HP module.
What was done to fix it? The setup process on HP readers has been fixed.
Failure in the process of adding printers that have a password with the character "_"
How did the problem happen? After adding printers that contain the “_” character in the password, the module began to show inconsistencies in some features (authentication, accounting, quota discount and HP reader configuration).
When did the problem happen? When accessing/using affected feature (authentication, accounting, quota discounting, and HP reader configuration).
Where was the problem? In the NDD Print MF HP module.
What was done to fix it? Fixed the setup process on HP readers and password management for NDD Print MF HP.
Accounting failure on “Scanner” devices without authentication
How did the problem happen? Accountings failure for "Scanner" devices that were added to the NDD Print MF HP without authentication, due to the lack of the general job counter feature.
When did the problem happen? When a “Scanner“ device was added to the NDD Print MF HP without the authentication feature.
Where was the problem? In the NDD Print MF HP module.
What was done to fix it? Arrangements were made for all HP equipment that has OXPd to stop using the printer's general counter and start using the “ordinal id” provided by the printer's OXPd to carry out the accounting.
Accounting failed due to restoring printer factory default template
How did the problem happen? When the printer was reset to the factory default model, which resulted in the printer changing the internal counter to 0 (zero). In our previous implementation, the MF HP waited for the printer's internal counter to equal the NDD Print MF HP counter to start accounting again.
When did the problem happen? When the printer was reset to the factory default model.
Where was the problem? In accounting for NDD Print MF HP.
What was done to fix it? We improved the existing accounting process, adding one more validation to consider the situation in which the printer is restored to the factory default model.
Accounting failed due to not enabling printer statistics service
How did the problem happen? Due to some factors (e.g. new devices, devices that did not have their registration enabled or devices that were reset to factory default), the printer statistics service was not being activated while adding the printer in the NDD Print MF HP module, causing the accounting service to become disabled.
When did the problem happen? During the accounting process.
Where was the problem? In the NDD Print MF HP module.
What was done to fix it? We added the printer statistics service record during the printer add process in HP NDD Print MF.
NDD Print Client Kyocera 5.7.9
Released on December 28
Fixes
Failed when user tried to access Kyocera NDD Print Client
How did the problem happen? When trying to use the NDD Print Client Kyocera, the following error was displayed: "Activation Error Expansion Authentication is disabled. Turn the main power switch off and on.".
When did the problem happen? When opening the NDD Print Client Kyocera.
Where was the problem? On printers that do not support Java 1.6.
What was done to fix it? We made the correction, including the Java package in version 1.4.
NDD Print Releaser 5.24.0
Released on December 27
Fixes
Failed to print PDF documents
How did the problem happen? When printing multiple copies of a held PDF document, either by upload or hold by email, the following failures occurred:
When printing multiple simplex copies, the pages printed out of order;
When printing in duplex, if the last and first pages of one of the copies were odd number, they were printed on the same page.
When did the problem happen? When performing PDF document printing.
Where was the problem? In PDF documents.
What was done to fix it? The flow of printing PDF documents has been changed.
Improvements
Support for the new form of Office365 authentication
What purpose? Allow the functionality of sending and receiving emails to be used through Office365 online.
What was done? A new Office365 connection method was implemented, which uses Azure application registration;
What will be affected?
Email sending features:
Sending an email to the delegated document owner, when it is printed by the user who received the delegation;
Sending an email to the user when receiving a delegated document;
Sending an email to the user when receiving a shared document;
Sending an email to the user when receiving a document delegated by affinity;
Sending email to user when successfully retaining a document held by email;
Sending an email to the user when there is a failure to retain a document retained by email.
Email receiving features:
Retention of PDF files by email;
Retention of Office files by email;
E-mail body retention.
What is the impact on the environment? There will be no impact on the application for those using SMTP, POP3 or IMAP through another provider. However, if you use Microsoft's online Exchange, the authentication must be migrated to the new form, without login and password
Observations? For this feature, the product prerequisites were changed:
.NET Framework update to version 4.6.2;
We have removed compatibility with Windows Server 2003 and Server 2008 SP2.
NDD Print MF/Client Konica 5.7.11
Released on December 21
Fixes
Failed to enable NDD Print Client while adding equipment in NDD Print MF Konica
How did the problem happen? It was not possible to add the printer (C300i) in the NDD Print MF with the Client enabled due to an error related to the OpenApi platform.
When did the problem happen? At the time of enabling the Client function on the printer.
Where was the problem? NDD Print MF Konica
What was done to fix it? Updated OpenApi platform versions supported by NDD Print MF.
Slowness in the printing and accounting process
How did the problem happen? During the accounting process there was an accumulation of calls according to the number of printers added in the NDD Print MF Konica, increasing the processing of the server's CPU.
When did the problem happen? During the accounting or printing process.
Where was the problem? NDD Print MF Konica
What was done to fix it? Adjustments were made in the way data from jobs performed on the printer are collected.
NDD Print Host 5.51.14
Released on December 16
Approvals
Approved printers for collecting counters and network supplies.
Approved models?
LEXMARK MX611dhe
HP LASERJET PRO MFP M428fdw
CANON GM4000 GM4010
EPSON L396 Series
EPSON WF-C5390
HP LASERJET PRO MFP 4103fdw
HP LASERJET PRO 4003dw
HP COLOR LASERJET E55040
Observations? Not available.
NDD Print Agent 5.23.10
Released on December 16
Fixes
Equipment set up for monitoring USB meters and supplies
XEROX B310
XEROX C315 COLOR MFP
Approvals
Approved printers for collection of USB meters and supplies.
Approved models?
HP LASERJET PRO MFP 4103fdw
HP LASERJET PRO 4003dw
HP LASERJET P1505n
RICOH P502
EPSON L396 Series
EPSON L1300
EPSON WF-C5390
RICOH P 311
Observations? Not available.
NDD Print MF/Client Epson 5.3.2
Released on December 2
Fixes
Problems running NDD Print Releaser "Smart Release" feature
How did the problem happen? Failed to execute the "Smart Release" feature, after configuring the "Initial actions" option in the "Release terminals" tab of the NDD Print Releaser module. After authenticating to the printer, the Epson NDD Print Client did not apply the setting made in the NDD Print Releaser.
When did the problem happen? After authenticating on the printer.
Where was the problem? NDD Print Client Epson.
What was done to fix it? We have fixed a NDD Print MF Epson method to correctly return the “Smart Release” functionality.
Module installation fails in Windows Server 2008 R2 environments
How did the problem happen? When trying to install NDD Print MF Epson in Windows Server 2008 R2 environments, the module returned the following error: “This version of NDDigital nddPrint MF Epson requires a Server operating system.”
When did the problem happen? During module installation in Windows Server 2008 R2 environments.
Where was the problem? In the NDD Print MF Epson module installer.
What was done to fix it? We have fixed the installer to identify all operating systems that support NDD Print MF Epson.