We don’t use this product. But maybe this will help?

• PCClient.app
• https://www.papercut.com/kb/Main/MacClientAutomatedDeployment/

• Sounds like you need to get the app from your server and package it yourself

What does the contents of the “vYear-Month-Day-Time” folders look like? 

We don’t have this product locally either (although a couple of our gateway campuses in Europe do use it).  Copilot seems to agree with ​@mvu .

I looked at that web link earlier also

That PCCclient.app is something I seen earlier but it's not in that directory listed on that web link.

The Papercut client is packaged by someone here and installed using JAMF.

The month date year folder gas an .app in it but I'm but even sure why that folder keeps getting created every time.

We use PaperCut but we don’t install the client on our Macs. We install the drivers for the copier/printer and the printers. What are you using the client for?

We deploy a plist file via a profile and then install the pkg based on who has the plist installed via a smart group. This was recommended for macs.  If you have that in place it might be another source for a smart group for you.

​@ktrojano  based on your reply I might be  confused on what is actually getting installed here.

Looks like probably what you said is what is happening in my environment.

Do you get a papercut popup for the user to login, then once they login it adds the printers?

Isn't that the papercut client?

​@ktrojano how do I know if it's the  client being installed versus just the drivers and printers?

Do you have that Papercut Print Deploy Client folder in your macs \Applications  folder?

​@tcandela I looked at our policy in Jamf and confirmed the package we are deploying only contains the printer drivers and the printers. Are you deploying Papercut to your Macs via a Jamf policy?

​@ktrojano yes we are using JAMF to deploy papercut to our macs.

It looks like it's installing the client and eventually the xerox drivers and printer.

Once the policy runs the papercut client pops up for the user to login. Once the user logs in,  it installs the drivers and printer. 

If the user doesn't login the papercut continously pops up  (real annoying) until they do login.

do you have anything for papercutin your \applications 

​@mvu  it might actually be that PCCient.app to use in my smart group to see what macs.have the Papercut client installed. 

I'll edit the group and check the results 

here is the Extension Attribute that i use to pull the Papercut Print Deploy Client version. 
Then use the Extension Attribute results to scope the smart group
 

#!/bin/sh
# If PaperCut Print Deploy is installed, get version

if i -d "/Applications/PaperCut Print Deploy Client" ]; then
    result=`ls -rd "/Applications/PaperCut Print Deploy Client/v"* | head -1 | tr "/" "\n" | tail -1`
    echo "<result>$result</result>"
else
    echo "<result>Not Installed</result>"
fi

We’ve never used the client. I can’t imagine the increase in support calls to the help desk due to that pop-up. With just the drivers and printers installed, the user is prompted to enter their credentials when they print. That way if they never print they aren’t prompted. 

I do deploy the client but you don’t need it.  They can check everything from the Papercut web portal.  I date most of my packages or have a version number attached to most packages and I show this package as not being changed since Feb 2020 for me.  Not saying there hasn’t been an updated version but that probably shows how much complaints I get regarding it.  You need to get the package from the Papercut Admin Portal if I remember correctly.  It’s been awhile.

​@mickgrant in my opening post I have the directory screen shot. From that screen shot where is it gonna find the VERSION?

​@mickgrant  So I added the extension attribute and have a couple results so far.  I don’t think it’s an accurate PaperCut Client version number it’s pulling based on the version number that shows up on the PaperCut Client vs the Extension Attribute results.

(No PCClient.app shows up in the \Applications folder)

I’ve done screen shots.  

PaperCut Client shows v1.9.1618

Extension attribute result shows v2025-08-11-1742

What are those multiple ‘folders’ that start with ‘v’  and then a date ?

Refreshing my memory on this just now.  Follow the instructions here:
https://printing.its.uiowa.edu:9192/content/help/clienttool/topics/user-client-install-mac.html

Get the app from the server’s share.
 

​@tcandela the version that the extension attribute is is reporting is the current client version being distributed by your server, and you can see it in the Papercut Print Deploy Client folder in you applications directory along side all the previous version (Which follow the same naming format)

To show you this i have taken a screenshot of the PaperCut Print Deploy Client.pkg that i just downloaded from my PaperCut instance as a DMG and then examined with Suspicious Package.

In the screen shot i have highlighted the .version file, which has a modified date of 11/08/2025, files starting with “.” are hidden by finder so you cant see it in your installed directory. but when you open the .version file it contains only one string - “2025-08-11-1742”

The installer also only contains one folder with the same naming scheme as you are being reported by the extension, v2025-08-11-1742. 

​@mickgrant all my screen shots did not upload on my last reply. The papercut client interface has a version number like v1.9.618 and and so do the logs. I don't see anything indicating version 1742 anywhere in the logs and client interface. 

I'll reply back tomorrow with the other screenshots that didn't upload.

That Number is from your web console and it is your Print Deploy server version.

It is not the version of the Print deploy client that is installed, which is the Universal Print connector version, and i already explained how to get that version.

But if you want the offical documentation (although this only refers to the windows paths) you can find that here - https://www.papercut.com/kb/Main/how-to-check-version-numbers/

​@mickgrant when the papercut print client pops up for the user to login it shows v1.9.618 

I don't see how this coincides with any of those V folders. 

I checked the log file from in the papercut print deploy client folder and it also says client v1.9.618

I'm expecting the extension attribute to display something related to  v1.9.618

​@dletkeman 

​@ktrojano 

Open up the log file and see what version of the client it says you have installed 

​@tcandela we aren’t installing the client in our environment.

Hi ​@tcandela ,
 

If you would like to retrieve the currently running version of PaperCut, you can create a script for an Extension Attribute (EA) based on the PaperCut log file located at:

/Applications/PaperCut Print Deploy Client/data/logs/pc-print-deploy-client.log

You can identify the version by searching for the following string within the log:
PaperCut Print Deploy Client running on version
 

​@mickgrant 

​@agungsujiwo 

The log file looks to hold the papercut client version but then the script has to check the most recent data because the log holds a bunch of previous papercut client versions.  The log has a bunch of dates that has the version at the time the log had data added to it. 

See the attached picture. Bottom right hand corner looks.to be where Papercut displays the papercut client version. 

​@mickgrant 

​@agungsujiwo 

The log file looks to hold the papercut client version but then the script has to check the most recent data because the log holds a bunch of previous papercut client versions.  The log has a bunch of dates that has the version at the time the log had data added to it. 

See the attached picture. Bottom right hand corner looks.to be where Papercut displays the papercut client version. 

 

Hi ​@tcandela 

Here is a script to find the latest running version.

#!/bin/bash
# Create by Agung Sujiwo 
# Path ke log file PaperCut
LOGFILE="/Applications/PaperCut Print Deploy Client/data/logs/pc-print-deploy-client.log"

if r  -f "$LOGFILE" ]]; then
    # Retrieve the latest line based on the date (the timestamp at the beginning of the log: YYYY/MM/DD ...)
    LAST_LINE=$(grep "PaperCut Print Deploy Client running on version" "$LOGFILE" | sort | tail -1)

    # Search for the version pattern (number format x.x.x)
    VERSION=$(echo "$LAST_LINE" | grep -oE " 0-9]+\.-0-9]+\.90-9]+")
else
    VERSION="Not Found"
fi

# Output ke Jamf Extension Attribute
echo "<result>$VERSION</result>"