At this point I've used PapercutNG along with a virtual print queue to have the software direct print jobs - this has created a kind of pooling environment. The problem still remains that any print jobs a machine is currently holding when it goes down are not transferred to the other unit. Alas, this may be the best solution at this point as I have been unable to find any documentation on this, or anyone who has successfully pooled.
The last GPD I used didn't have accounting as an option, but I see that the newest does. Not sure how old the last one was.
Regardless, pooling still does not work correctly. Is it even possible to have these units pool?
We have two 5150's set up on the same queue (Windows Server 2008 R2) and have pooling enabled on this queue. The low-IP printer prints first (as normal) but jobs continually stack on this machine and none are ever sent to the other unit. Also, when this unit jams or has a problem that stops printing services, jobs continue to pile up on this unit.
Is there something on the printer itself I need to adjust? Anyone had any experience with this?