Hi All,
Apologies if this has been discussed elsewhere. I did my best to search existing threads.
In the past, when deploying printers with Casper I've used a workflow where, on a packaging computer or VM, I install the printer drivers and add the printer to OS X via the gui, then suck the printer into the JSS using casper admin.
Next I would typically use the CUPS web interface (http://localhost:631) to go and modify all the defaults that I wanted to get pushed out with the printer object (for example, default to single-sided, black and white, etc.). In the past, applying changes to defaults using the CUPS interface would modify the .ppd file in /etc/cups/ppd which i would then add as a custom ppd to the printer object in the JSS
For deployment i'd have a policy with the driver package and the printer object with the custom .ppd file. This has always worked great.
I've just been attempting to package up a printer in this manner in 10.11 and noticed that any changes to defaults made with the cups web interface no longer stick. I assume this is due to SIP not allowing the CUPS interface to modify /etc/cups/ppd/*
Has anyone been using the cupswebctl to successfully modify printer defaults in El Capitan? If so, any pointers? An alternate workflow for customizing the PPD would also be useful! Open to suggestions.
Best regards,
Neil
