I have no idea what this "engineer" is so I can't say.
A Xerox tech probably wouldn't, they are the hardware guys, they may know the software, but they are not at all required to.
Any 2nd level rep absolutely would know, any Analyst (The software/network guys that are not part of your contract) should know, and they have us in 2nd level support to help them as well. (Any Analyst won't be a pro at every machine, they support every device made by Xerox and get sent for a multitude of reasons, where as 2nd level support is much more specialised, we deal directly with a specific subset of devices, and for that reason, we will always know the little glitches, bugs, limitations of the machines we support that someone who does not deal with them couldn't possibly know)
To add to this, would this not be something an engineer would know or be able to advise?
You have no idea how stupid i feel. I have spend days trying to figure this out and that must be the one menu i did not look in to find this option.
Thanks very much, I will now check the rest of my machines to make sure this option is set.
Sounds like it was set to retain all jobs instead of deleting when printed/released, so you are filling the drive. Or people are just printing and not ever releasing them which does the same thing.
So check the setting here:
The machine will not delete Secure Print jobs via the Secure Disk Image Overwrite option, that only removes cached data from jobs that were printed/copied/scanned previously.
There is no reason to Altboot these devices anymore, the new installer tool I already linked you on a previous post has ended the Altboot method, deleting the jobs that are stuck would be done faster and easier by running s Secure Disk Image Overwrite manually
Slowly but surely our fleet of 5855's are experiencing the same issue. It would seem that the internal memory is not clearing down.
All the devices are set to Secure Print by default and they get to a point where they only have the capacity to hold onto a very small number (2 or 3) of jobs. The rest of the jobs sit in the server print queue until a job is released from the printer then the next one will jump into the printer.
They are all set to do a full override every day at 2am but i have noticed that comming in in the morning the jobs that were left the night before are still there.
Until now i have been getting an engineer to perform a forced alboot and reapply firmware but i wanted to know if there was anything else i could do.
Cloning from a working machine makes no diference.
Solved! Go to Solution.