Three students reported that when printing more than one copy of something there was strange behavior. One student reported that when requesting 3 copies it printed 9 copies and when printing 5 copies it printed 25.
A second student reported that she noticed when she requested to print 3 copies of something it was going to charge her double (for 6 copies) so she did not release the job and instead sent three separate single copy jobs to the printer which charged her the appropriate amount.
A third student has just printed a job for 5 copies and received 25. It looks like at the printer that it is sending the job 5 times, because it says printing 1 of 5, 2 of 5
All,
"Mopier Mode" is functionally a toggle between "in-job collation" and "electronic collation." When Disabled, it causes multiple copy requests by the end user to wind up as discrete jobs within the actual print file (so if you ask for 2 copies of a page, two copies of the job data are written to the file). Enabled and you end up with one copy of the job data with a command to basically "while n < x, do."
I am also a big fan of PCL5 and a detractor of PCL6 (I'm an even bigger fan of PostScript, but that's really just a personal preference).
In other news:
Colleen, if this printer is being deployed via a Package with the Updater module installed, you can make some material change on the server's queue and basically recreate the new printer on all installed clients (which is a great thing). Then, ensure that the "Copy printer settings" option is enabled for the queue in Pharos Administrator, and rebuild the Package. When your clients perform their next update check, their local queue instance will be deleted and recreated with your new settings.
Scott