As a note, I have a mix of labs, and office computers. And I'd really like to prevent lab users from modifying the printer list. Which I note is something I can set via a policy, but I'm unsure if the printers have to be managed via the printer policy, as well.

Not sure why you're choosing to go the package / Composer route with regards to printers ...

Why not add the printers with the specified drivers with Casper Admin, create a policy to choose the printers you want to install, and then scope the policy to a group of computers you want to have the printers installed on?

If your users aren't admins they won't be able to add printers without admin credentials.

We have users access printers not automatically installed via Self Service.

Why not include the printer in the configuration, then deploy your settings package. Are lab users admin? They shouldn't have rights to modify the printers

@aporlebeke That's what I'd like to do, but how do I then deal with custom settings (color printers default to BW, setting the proper finishers, etc)? I guess I could create a policy for each printer, and have the settings adjust with lpadmin... or will that command run "after" the printer is added?

@staze Just to be clear, you want to set a default setting for the "Finisher" for a printer, for example?

@staze It's been a while since I've used Casper Admin to capture printers, but I do believe that Casper Admin will capture the custom PPDs.

I use lpadmin myself to add printers and to configure default settings, like B&W only, what finisher tray, etc. I have a script for each printer, and then have a policy for each printer that I place in Self Service. The policy just calls the proper script.

@stevewood That makes sense... the only issue being, how do you then remove a printer from a client?

@stevewood you are correct. Casper Admin will grab those PPDs when you add a printer, so as long as your computers have the necessary drivers, when you install the printer via policy you'll be good-to-go

@staze you create a policy with the Printer payload and choose Uninstall from the dropdown options underneath the printer (instead of the Install)

@aporlebeke Great, thanks!

@staze in my case, I have another policy for removal that just issues lpadmin -x <printername>.

Okay, so, let me make sure I understand.

Create an installer that installs drivers (either apple ones, or company specific ones), and map that to a policy to install it. Configure printer on my machine, and then capture via Casper Admin (which should grab the modified PPD). Then just create policies to add printers in question. Maybe even have the smart group check for the existence of the driver before adding the printer.

Seem reasonable? Is there any way to combine the pkg that installs the drivers into the policy that add's the printers?

@staze yes, you do not have to have two policies, just one to install the drivers and the printer at the same time.

@staze, I have a workflow for installing printer drivers on an as-needed basis as part of setting up the printer. For the details, please see the posts linked below:

https://derflounder.wordpress.com/2014/02/06/deploying-canon-print-drivers-with-printer-setups-via-caspers-self-service/

https://derflounder.wordpress.com/2014/02/10/deploying-xerox-print-drivers-on-a-per-os-basis-via-caspers-self-service/

@rtrouton to the rescue!