JSS is running on Windows (2K8R2, MySQL 5.6.10 with strict checking disabled)
Mac clients are running 10.8.4
Printers are all HP, the Apple-hosted HP drivers (current version: 2.14) are baked into the imaging workflow, but I've independently confirmed that all of the clients have the current version of the drivers/PPDs.
I recently added 35 printers to the JSS (and created Self Service policies for their deployment), and had one user complain that the printer, as installed by Casper policy, does not show all of the options it should. I confirmed this (by deleting the printer and adding it manually). Sure enough.
I started looking at /etc/cups/printers.conf - there were some subtle/slight differences to the actual keys, and the order, between adding it manually vs. adding via Casper policy. I also discovered, if I enabled the web interface to CUPS, modified the printer (which required me to authenticate), and re-selected the PPD, it would rewrite the printers.conf file and all of the printer options would show up correctly. There was no difference between the /etc/cups/ppd/printer.ppd file between manually setting up the printer, vs Casper deployment, vs editing the Casper-deployed printer through the web interface.
I did run this past support and we did verify/check a number of things; ultimately I figured out the correct lpoptions so I can use lpadmin to create the printer. Of course, I now need to check the other 34 printers to make sure that they don't have configuration issues as well...
Wondering if anyone has seen anything similar to this.
