My best guess is that the print jobs fail because of incorrectly entered
job accounting codes (Kyocera configured with Document Boxes). It's hard
to tell, though, when I don't get regular reports of failures and there
are usually multiple backlogged documents in the queues when I am
notified of printing issues.
On 9/24/2014 9:55 AM, Andrew Hendrickson wrote:
> You may want to look at why the print jobs fail? All of our computer labs that have printers are set up with peer to peer printing and we almost never have this problem.
> What are these people printing that cause such frequent failures? Is it that the printer is old or in poor repair? I know for a fact, as an example, that older HP laserjets (2300s and 4000s) will choke hard on commonly encountered PDFs, generating a flashing red error light, “danger Will Robinson”, response.
> It may be far cheaper to replace the printer than to spend your time working around the fact that print jobs get left in the queues.
> On Sep 24, 2014, at 9:52 AM, Avery Bacon <[log in to unmask]> wrote:
>> Hi Folks,
>> I have a network printer set up via IP configuration in one of my labs. The server queue didn't work with the virtual lab implementation and our printer code system, so it had to be set up per machine instead. Print jobs fail frequently enough that a logoff script to clear the local queue seems like a good idea, but I'm not sure how to implement it. Is anyone doing something like to this? Suggestions for other ways to deal with the issue?
>> Avery Bacon
>> IT Support Coordinator
>> College of Nursing and Health Sciences
>> University of Vermont
> Andrew Hendrickson
> CAS IT Administrator
> UVM, College of Arts & Sciences
> [log in to unmask]
> To submit a request for service please use:
IT Support Coordinator
College of Nursing and Health Sciences
University of Vermont