We just started using Papercut for our printers. At this same time, we purchased all new HP printers. I used the Papercut article for mapping the printers to our iMacs https://www.papercut.com/kb/Main/UseJamfProToDeployPrintersOnManagedMacOSDevices
This script works well in Jamf to push out the mappings, except the clients are not using the proper driver (printer kind says "Unknown-AirPrint). So basic black&white printing will work, but users are unable to change any settings on the printer such as color. It looks to just be using a basic AirPrint driver. HP doesn't have any basic drivers to put on the machine as the new way of printing is to use AirPrint which is driverless. If I use the HP utilities to search for a network printer and map manually, it works fine (printer kind says "Secure AirPrint"). Wondering if anyone else has come across this and if they found way to rectify.
Jumping on here to share my experience with a new papercut setup -- so glad I found this thread.
We are installing certain Papercut printers via Jamf -- our virtual Print-Release queues. We are currently using Papercut v20.0.2 and Mobility Print v1.0.2916
I used the script found in the Papercut knowledge base article mentioned in the original post above:
In the article jump down to the steps.
I made a few additions to the script just before the #CleanUp stage:
Turn off printer sharing
lpadmin -p "$name" -o printer-is-shared="False"
Set this queue as the default printer (we are setting our Print-Release queues as the default printers for each of our locations)
lpoptions -d "$name"
Following onto Asnyder's post, we originally tried the simple import into Jamf Admin. Since we are requiring authentication, the authentication prompt SHOULD pop up at the first use of a new print queue. For print queues imported from a client machine into Jamf Admin, then deployed via policy, the authentication prompt did not pop up for the user. Their first print job was held in the print queue waiting authentication. The second time the user printed to the same queue, the authentication prompt appeared, and the job was sent as expected. When installing print queues via script instead of printer package, we had none of those issues.