Papercut Install License

[Lucrecio Poinson]

Thissection covers the initial installation and configuration of PaperCut NG/MF in your network environment. Initial installation takes only a few minutes on a currently configured server. This guide walks you through installation and configuration step-by-step. The process is summarized below:

When using Release Stations or account selection popups, PaperCut NG/MF pauses jobs on the Windows print queue to hold jobs prior to printing. It is important, especially in charging environments, that the queue is secured to prevent users from resuming jobs themselves and bypassing PaperCut NG/MF. There are two ways a Windows print queue can be secured:

The PaperCut TCP/IP port is required if you are using hardware page count validation. For more information about configuring the PaperCut TCP/IP port, see Windows printer queue configuration. To check which port is being used, have a look at the Printer Properties > Ports tab.

After the download is complete, run the setup wizard as an administrator. A system restart is not usually required, but you should install on live production systems during periods of low activity, for example, not during backup operations or other administration activities.

This selection determines which system defaults are used. For example, in a Professional (Client Billing) organization, where it is useful to charge-back printing to customers, an advanced client popup is provided with additional features useful for dealing with large numbers of client (shared) accounts. You can change these default settings chosen for an organization type after installation.

Selected organizational units; then either click Copy from Verify user credentials or click Add and select the units from the list. (Use this to limit syncing to users in a subset of groups.)

In the Read group information section, click the switch to set it to On; then click ADD LDAP CLIENT. Google displays a confirmation message and information about downloading the certificate.

In environments where user interaction for Account Selection is required and the user has both options - User Client and printing device - running the User Client may be optional. Hence, deploying it immediately is also optional. If you choose not to deploy it now, you can still deploy it in the future. However, in environments where user interaction for Account Selection is required and can only be done via the User Client (and cannot be done at the printing device), running the User Client is mandatory. Hence, deploying it immediately is also mandatory. If not, the user is unable to carry out the configured user interaction for Account Selection, and the job remains paused in the print queue and does not appear on the printing device. The User Client can be deployed directly from a network share (which is automatically configured on Windows). There is also the option to install the software locally on each workstation, however, this is not usually recommended because it makes the process of updating the User Client more complicated. For more information about the Account Selection options with and without user interaction (via the User Client or printing device), see Shared accounts, User Client, and Allocating accounts to print jobs at the device.

Take some time to explore the features of PaperCut NG/MF before continuing reading at Implementation by example or Tour. Business users might be interested in trying the popup client software as covered in Client software. If desired, the client software should also be deployed to other workstations. This procedure is detailed in User Client.

Using pc-client-local-cache.exe is recommended on large networks. It does, however, require a globally writable cache directory. By default, the cache is created in a directory on the system drive (normally C:\Cache). You can specify an alternate cache with the --cache command-line switch. Administrators should ensure that standard users have write access to the system drive, or manually create the cache directory if required.

The User Client software is available as a silent-install MSI (no clicks or wizards). This option is available for advanced sites that already leverage MSI packages for automated software deployment and upgrades using Active Directory Group Policy options. We recommend using the pc-client-local-cache.exe version of the User Client for most deployments, as all updates are automatically pushed to client machines. The MSI option discussed here must be manually updated.

The MSI package is a great option for organizations managing staged rollouts via Group Policy Filters. It is common in large organizations to progressively roll out new software as a series of small steps, for example, the IT department might get the software first, followed by a roll out across the organization.

When the Windows 8 user interface is in Metro mode, Windows desktop applications are not visible. This includes notifications, such as the PaperCut Client popup. Therefore, the Client popup could be missed.

The client software (pc-client.exe or PCClient.app) is optional and is only required if you wish to offer real-time feedback such as account balance, popup messages, and/or popup account selection. It is not used as part of the print control process - all this is implemented on the server-side. The client software is best described as a viewing tool and acts on the direction of server-side logic.

During the server installation, PaperCut will set up a read-only network share called PCClient. You will find the client software for Windows, Mac and Linux workstations located in this share. This approach ensures that you have the matching client version always available via this share.

The client software is located at [app-path]/client. The directory again contains the client software for all platforms. You may optionally opt to share this directory using an appropriate technology.

The PCClient.app is already installed on the mac lab machines. I also have a JAMF Policy set up which seems to correctly install the Launchd com.papercut.client.plist to /Library/LaunchAgents. I just need a Launchctl kickstart which I assume means scripting???

When I tried setting this up manually at a specific computer, per Launchd it all worked fine (I was using the default KeepAlive setting which is what I want), so I think all I have left to do to make it all work through Jamf is to set up Process 4 of this document which changes the ownership and permissions of the com.papercut.client.plist. Not knowing scripting, it seems to me that I could add an Execute command to Files and Processes in the Launchd plist Policy I have and insert the three commands there separated by semi colons. Does this sound feasible?

Step 6 in the instructions you posted has the launchctl command needed to load the agent once it's in place and has the right permissions and ownership. However, be aware that putting that exact command in a script run by a Jamf policy won't work, because policies run as root, and a LaunchAgent has to be loaded as the user. You can get around this by running launchctl as the user. Or, you can simply allow the LaunchAgent to kick in naturally after a logout/login or a reboot and login.

Hello @alstos and welcome to our community. For us, we configure the config.properties file located in /Applications/Contents/Resources folder. The configuration is the server IP address, port and server name. Once configured, we ensure the com.papercut.client.plist is located in the /Library/LaunchAgents folder with the permissions described by @mm2270 mentioned above. I do this all using Composer to capture the files during an snapshot install. Then I package these files up and install using Jamf. The files are installed into the right location with the correct permissions. I don't have the script a thing. The launch agent runs for all users and this has worked for us for a number of years now.

Jamf's purpose is to simplify work by helping organizations manage and secure an Apple experience that end users love and organizations trust. Jamf is the only company in the world that provides a complete management and security solution for an Apple-first environment that is enterprise secure, consumer simple and protects personal privacy. Learn about Jamf.

This site contains User Content submitted by Jamf Nation community members. Jamf does not review User Content submitted by members or other third parties before it is posted. All content on Jamf Nation is for informational purposes only. Information and posts may be out of date when you view them. Jamf is not responsible for, nor assumes any liability for any User Content or other third-party content appearing on Jamf Nation.

3a8082e126