We are using PaperCut to manage some printers. In short, it takes the print job from the computer, and passes it off to any printer that the user swipes their badge. You set up ONE printer on the Mac and it will let you print to any of the printers in the Building/Company.
We have a building where they have printers of different makes (HP / Canon / Konica Minolta / Whatever). That requires the one printer setup to use the "Generic Postscript Driver" that is included in the Mac OS, rather than a printer/company specific driver. The idea being the generic driver is the lowest common denominator and should work across all devices.
JAMF shows the way to add a printer is to set it up on a Mac like you normally would for a user, then import it into JAMF with JAMF Admin. Then create a policy to deploy that printer plus do an install of the driver for the printer and scope it out as normal.
I did that - however there is no "Generic Postscript Driver" install .pkg to add to the policy. I figured it was already installed on every Mac for the past decade, so should be good to go.
NOPE
I run the policy through Self Service on a couple test machines. On my M1 with Monterey, it tries to install and fails - but there is no failure of the install listed in the JAMF console when I look at that Macs history. On my Intel Mac running Catalina - the Self Service policy spins indefinitely, also creating no printer and no log.
I have other policies that I have created with a driver for a specific model printer and it works fine. The main difference is that I am trying to use the built-in generic driver and don't have a package to deploy with that driver.
I have seen some threads talking about scripting this out, but was not sure they fit my scenario, and they were about 5 years old - so not even sure if those solutions would still work.
Anyone else able to deploy a printer with a generic PS driver via policy? How?