AnsweredAssumed Answered

Why is a Job Sent before UniUpdater?

Question asked by Richard Smith Jr on Oct 16, 2014
Latest reply on Oct 16, 2014 by Steven English

We have recently completed a major overhaul of our printing infrastructure:  2008 VMWare to 2012 R2 HyperV, UniPrint 8.3 - 9 and a brand change of each printer we use that communicate with Pharos.


One of our bigger hurdles was that while the updater would pick up these changes and update accordingly, the users job was still sent and would charge/print an error page.  Is there a spooler or other Windows service/issue leading to the way this currently works or can it be changed?  To be more specific:


Current: Popup client information entered -> users job is sent -> uniupdater is launched, etc.

Proposed: Popup client information entered -> uniupdater is launched -> users job is sent once the 'No Updates' or 'Finished updates' process is complete


Forgive me if this has been addressed in the past,