Forum Discussion
All printers printing slow.
As seen above many print jobs are taking +30 seconds regularly to print. Printer acknowledgement time is oddly high in this case but among other printers (we have +50 using universal print, all very slow when compared to operating on local network) the time delay may be more due to upload/download. The larger file sizes on average take longer as expected but not in all cases, some times very small 1 page print jobs just take a long time despite the printer not doing anything when the job was issued.
- All,
After much back-and-forth between MS and Kyocera I can confirm this painful issue has been solved.... it was indeed a firmware issue on Kyocera side. The printer was not able to communicate with the queue during sleep mode.
Not fixed yet in official firmware but will be soon I hope. I got an onofficial one...
Kr
Christiaan
14 Replies
Hi,
This is Kevin from Kyocera Document Solutions Development America.
We are currently investigating this issue.
We will provide an update regarding this issue after ongoing investigation, and will also provide an update on how to contact the correct communication channel with Kyocera support soon.
Regards,
Kevin- Hi Kevin, thanks for taking the time to reply. I eagerly await your response. I did contact Kyocera in the Netherlands and they have registered my question under 12330130. No response yet though.
regards,
Christiaan- All,
After much back-and-forth between MS and Kyocera I can confirm this painful issue has been solved.... it was indeed a firmware issue on Kyocera side. The printer was not able to communicate with the queue during sleep mode.
Not fixed yet in official firmware but will be soon I hope. I got an onofficial one...
Kr
Christiaan
- Hello, I on the other hand think your time from Created to Final are fast or at least what to be expected compared to many of the regular times I have seen.
From what I have seen the total time can increase depending on the bandwidth of the office and the physical distance between the office and the, in our case, connector server.
There will of course be more of a delay when using MS UP compared to using a local network solution since you are introducing several steps, most notably uploading the print job to and downloading it from Azure.
You can check of the full steps used by UP on the below link and then compare it to a local network setup.
https://learn.microsoft.com/en-us/universal-print/fundamentals/universal-print-troubleshooting-print-job-journeyThank you for the response and documentation. While it does grant me insight into the process, my goal is to improve these time metrics as the business which is piloting Universal Print prints thousands of pages a day; many individual user workflows will exceed 100+ individual print jobs per day. So, going from a 2 second response to a 45 second response for each one is simply not viable to sustain their workflow. Naturally we can try to reduce the need for such high printing traffic, but the point of Universal Print is...to print, I believe - and the organization is very interested in continuing to print at the same rate for now.
Universal Print is failing to "keep up" with their printing traffic needs, essentially.
The printer management benefits on the other hand are quite useful to the organization so if I am able to improve the print times in any manner then it is still possible to retain their use of Universal Print.
While I know you have implied that we cannot expect any improvement in performance from Microsoft's end on this in the near future, I am hopeful that you can disclose what type of network traffic Universal Print uses so that we may attempt Quality of Service and traffic shaping measures to improve these slow print times.
Any other tactics which you may recommend beyond "don't use the connector" would also be welcome; I only use the connector for models which do not support universal print, however, in my experience the print times are not noticeably different regardless of whether the connector is in use or not.Here is an article published by Microsoft themselves which discusses the topics I linked previously but more in depth.
To be more specific the article goes through each step of the "print job journey" and the impact each step has on the latency of a print job which in turn points you to where you can make improvements to reduce the bottlenecks.
Keep business going with Universal Print - Microsoft Community Hub
