macOS User Client Deployment using Packaging & Deployment Tools
For large managed macOS environments, it is generally not feasible to install the User Client (
PCClient.app) by hand on each workstation. This document will explain some best practices for automated deployment of the User Client.
You will need to package the
launchd.plist if required) and distribute the package to your macOS systems.
PCClient.app application is responsible for activity tracking and charging. It can be found inside your PaperCut Application Server’s installation path.
- Default path is
For permanently on-site Macs, where the PaperCut Client app needs to launch on user login and stay running for the entire user session, you should install a launchd plist. For best results store the launchd plist in
If you’re deploying the
/Applications/ then you can use our linked plist - PaperCut_LaunchD.zip.
If you’re using a customized location for the Papercut client app (i.e.
/usr/local/) you will need to modify and deploy the following plist. Ensure to replace
PathToApplication with your appropriate path.
<?xml version=“1.0” encoding=“UTF-8”?> <!DOCTYPE plist PUBLIC “-//Apple//DTD PLIST 1.0//EN” “http://www.apple.com/DTDs/PropertyList-1.0.dtd”> <plist version=“1.0”> <dict> <key>Label</key> <string>com.papercut.client.agent</string> <key>ProgramArguments</key> <array> <string>/[PathToApplication]/PCClient.app/MacOS/JavaAppLauncher</string> </array> <key>KeepAlive</key> <true/> </dict> </plist>
launchd.plistvia launchctl, deployed with management software
- Available to users via a management app, by policy or self-service
PCClient.appdeployed via self-service, or alternate printing solutions utilizing PaperCut
- Mobility Print
- Email to Print
- Web Print
Keywords: macOS , macos , mac , apple , user client , pcclient , launchd , client , login hook , munki , casper , jamf
Last updated December 6, 2023