Choose your language

Choose your login

Contact us

macOS User Client Deployment using Packaging & Deployment Tools


For large managed macOS environments, it is generally not feasible to install the User Client ( by hand on each workstation. This document will explain some best practices for automated deployment of the User Client.

🔎 Components

You will need to package the (and launchd.plist if required) and distribute the package to your macOS systems.

User Client

The application is responsible for activity tracking and charging. It can be found inside your PaperCut Application Server’s installation path.

  • Default path is

/Applications/PaperCut [NG/MF]/client/


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 /Library/LaunchAgents/

If you’re deploying the in /Applications/ then you can use our linked plist -

If you’re using a customized location for the Papercut client app (i.e. /Applications/Utilities/ or /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” “”>
   <plist version=“1.0”>


Scenario 1

  • & launchd.plist via launchctl, deployed with management software

Scenario 2

  • launchd.plist set to RunAtLoad.
  • Available to users via a management app, by policy or self-service

Scenario 3

  • deployed via self-service, or alternate printing solutions utilizing PaperCut
    • Mobility Print
    • Email to Print
    • Web Print

🖋️ Notes

Categories: How-to Articles , User Client , Installing, Uninstalling and Migrating

Keywords: macOS , macos , mac , apple , user client , pcclient , launchd , client , login hook , munki , casper , jamf


Last updated April 4, 2024