Posted on 02-09-2022 01:48 PM
has anyone setup through a policy the installation of the PaperCut Print Deploy Client.pkg to a lab of computers and had the printer successfully install on the Macs?
Posted on 02-09-2022 03:37 PM
We have just started implementing this in our labs successfully. A lot of stuff was done through our printer admins but it was pretty smooth installing on the computer. Are you having any issues? I can relay the message to our printer admin.
Posted on 02-09-2022 03:46 PM
I have the client pkg from the person that setup papercut but he hasnt done much with it regarding testing on AD joined macs.
Id rather install from a jamf policy vs going to each mac 1 by 1.
I haven't tried anything yet. Looking for input.
Posted on 02-09-2022 04:18 PM
Yes definitely, we did basically that. We created a custom tigger policy and rolled it to different OS / hardware (M1 etc.)to make sure it was a smooth run. We then had some of our IT with Macs test it on there machines since we also did it for Fac/Staff as well. It went pretty smooth when we started spring semester
Posted on 02-09-2022 06:34 PM
We're any of the macs AD joined? Or single user macs?
What triggered your policy? Did it just install the ppcliient without anything extra like a script to do something?
Posted on 02-10-2022 04:49 AM
We did both bound to AD and ones using Jamf Connect (Since we are still testing before going live) the ones the were bound automatically logged the users in to the client. We did have to push out a manage preference with the plist that is required so when the print deploy is install it knows which server to use. There is actually a whole guide in paper cut's website for Jamf deployments: https://www.papercut.com/help/manuals/print-deploy/roll-out-the-client/deploy-jamf/
After the manage preference is in the computer we just used the package that comes inside the paper cut server no scripts needed.
This is a little extra but we also created a smart group for when they receive the manage preferences they are able to install paper cut from Self Service.
After testing with custom trigger and Self Service, we pushed it out at check in.
Posted on 02-10-2022 06:02 AM
Also consider not deploying the client at all. Instead deliver a .webloc to https://papercut.server.domain:9192/client
It might be that paper cut web server could be configured to support SSO with kerberos so a client running Apple Kerberos SSO extension or Jamf Connect would automatically logged in tho I have not tried this.
Also this works with any platform.
Posted on 02-24-2022 02:34 PM
We're working to set up PaperCut deploy in a similar way, working from the PaperCut guide gabe2385 linked to. But I've run into an issue with getting the .plist file to user computers. I've made the configuration policy the way the guide suggests, but it doesn't seem to get added to the computer. The guide has a note about the .plist file needing to go in /Library/Managed Preferences, but there's where to set the location. If I manually copy the .plist, then the .pkg install seems to work the way it's intended, but without that .plist file, the Deploy Client won't connect to the server.
Any advice on how to set up the configuration profile to add the .plist properly? Or do I need to add the .plist some other way?
Posted on 02-24-2022 03:45 PM
Hello @jzc_SKHIT Here is how we were able to get it working in our environment,
This is the Configuration Profile we setup to deploy to the machines I just blurred the string where you put your Paper cut server. One thing we did that I would suggest, we only deployed the print deploy packages to the ones that successfully receive the profile, otherwise print deploy acts funny when its installed and the profile comes after. Sometimes a restart would fix it but we decided to make a smart group and auto deploy it to the ones that fall into the smart group:
Hope this helps point to the right direction.