@tjhall no it isn't installed with a post script. I just literally fill up the printer detail in "Printer" and deploy it as a policy
@tjhall no thats tthru PaperCut. the ip address on the screenshot is to the papercut queue server.
when I run lpstat - s i get the following:
system default destination: Secure_Print
device for printername: ///dev/null
device for Secure_Print: lpd://10.1.1.61
One thing of notice is that there is an "_" added to the name which shouldn't be there.
As i said previously, when I setup the printing on a mac manually using the settings, the PaperCut secure printing works perfectly, I just go to any of the printers and use my id card to release the print.
is this the right format for the script?
@tjhall @mainelysteve @Chris_Hafner thanks guys for your comments, will try those and let you know. I am very new to Jamf we only just started using it and am still trying to figure things out. We primary have windows pcs and just about 25 macs.
The puzzling thing is that when I setup the printer via below, it works but not when deployed thru Jamf. I suspect the issue might be because the secure print share name has a space in it.
@Chris_Hafner can you explain how to create the smart group that tracks paused print queue
@bodeo Listen to @mainelysteve and use DNS names. As for the scope question.
1) Create an Extension Attribute with the script I included above
#!/bin/bash
# echo $(lpstat -p | grep -EB1 "Paused")
# echo $(lpstat -p | grep -w "disabled" | awk '{print$2}')
RESULT=$(lpstat -p | grep -w "disabled" | awk '{print$2}')
echo "<result>$RESULT</result>"2) Create a new SMART group as follows:
CRITERIA of "NAME OF EXTENSION ATTRIBUTE"
OPERATOR: "is not"
VALUE: (leave blank)
It should look something like this:
