PaperCut User Client + local Windows accounts + print card authentication (Intune managed devices)

Hi everyone,

I’m trying to design a reliable PaperCut setup for a public/library-style environment and I’m curious how others handle this.

Environment:

•	Devices are Intune managed

•	Users log in with local Windows accounts (no AD / no Entra ID user sessions)

•	Users do not have personal domain accounts

•	They purchase a print card from us with a code

Desired user flow:

1.	User logs in to the PC with a local Windows account

2.	User opens a document and clicks Print

3.	A PaperCut popup appears asking for the code from the print card

4.	User enters the code

5.	User goes to the printer and enters the same code on the device

6.	User releases the job at the printer

The challenge is how to correctly deploy and run the PaperCut User Client on these machines.

These devices:

•	Are not domain joined

•	Only use local Windows accounts

•	Are managed with Intune

•	Do not use the traditional \\PCClient network share “zero install” method

We initially tried using pc-client-local-cache.exe, but this seems intended for the “run from network share and cache locally” scenario, which doesn’t align well when the client files are already deployed locally via Intune.

We are now testing with pc-client.exe deployed locally and started at user logon.

Main question:

👉 What is the recommended and supported way to run the PaperCut User Client in this type of public/library environment with local Windows accounts and print card popup authentication?

Has anyone implemented a similar setup, and if so, how did you deploy the client in a way that aligns with PaperCut best practices?