Why Follow-Me Pull Printing Won’t Release Jobs and How to Fix It

Joe B.

Expert ★★★★★ 27,853 satisfied customers

Specialities: Windows Server 2016/2019/2022, Azure AD, Microsoft Universal Print, PaperCut MF/NG, uniFLOW, PrinterLogic, MFPs

Pull printing not releasing — PaperCut / uniFLOW / PrinterLogic on Windows Server

Technician

Hi! We’ll get Follow-Me / secure pull printing releasing again. Tell me your environment: Windows print server version (2016/2019/2022), the solution you use (PaperCut MF/NG, uniFLOW, PrinterLogic, Mobility Print, or Microsoft Universal Print), and the release method (card swipe/PIN at the MFP, release station, or Embedded app). Also share if print queues are Type 3 or Type 4 drivers and whether jobs show as Held in a queue or disappear.

Customer

Windows Server 2019 with a PaperCut MF server. Users send to the Follow-Me virtual queue, the job appears but won’t release at the copier. Sometimes it says “No jobs found” on the embedded release screen.

Technician

Thanks. When Follow-Me printing is not releasing jobs, the common root causes are:
• Ownership mismatch: the server captures the job under a different user/SID (e.g., service account, “SYSTEM”, or UPN vs sAMAccountName), so the release app can’t match the job to the logged-in user.
• Queue permissions: “Manage documents” or “Print” rights missing for domain users, or Point and Print restrictions blocking delegation.
• Print Spooler or application server services out of sync: PaperCut Print Provider not connected to Application Server, or Spooler cache corruption (PRINTERS folder).
• Driver/model mismatch: using Type 4 class drivers with advanced finishing or accounting; some pull-print flows require Type 3 or vendor UPD (PCL/PS).
• Release station/Embedded connectivity: blocked ports (9191/9192/9195), TLS/SSL trust, or time skew breaking device authentication.
We’ll verify identity mapping, permissions, services, then test with a clean vendor Universal Print Driver on the queue.

Customer

How do I check the job ownership and identity mapping in PaperCut?

Technician

Verify user mapping for secure print release:
1) In PaperCut Admin → Logs → Job Log, locate the print job and confirm the Username equals the user’s AD sAMAccountName that signs into the MFP. If it shows a card number or UPN mismatch, enable Identity → User/Group Sync and map card IDs to accounts.
2) On the Print Server (Windows 2019/2022), open the queue → See what’s printing → confirm the job’s Owner matches. If it shows “SYSTEM”, enable Render print jobs on client computers (for Type 3) or disable client-side rendering for Type 4, then test.
3) If using a Release Station, check release-station.properties and server hostname/SSL certificate trust. Time skew >5 minutes breaks SSO and card auth.

Customer

Permissions might be the issue. What should the queue permissions be for a shared “Follow-Me” queue?

Technician

Recommended print queue permissions (AD/GPO deployment):
• Security: grant Domain Users → Print; the PaperCut/uniFLOW service account → Manage Printers and Manage Documents.
• If you deploy via GPO printer connections, confirm Point and Print Restrictions allow the server as a trusted print provider; set Package Point and Print — Approved Servers to your FQDN(s).
• Clear stale Deployed Printers policy objects and re-apply (gpupdate /force). On clients remove old queues (especially migrated from 2008 R2).
• On the queue’s Advanced tab: test with Type 3 vendor driver (UPD PCL/PS) instead of Type 4 class driver; disable bidirectional support temporarily and set Spool print documents → Start printing after last page is spooled.

Customer

Jobs still don’t appear at the MFP. The service shows connected, but nothing releases.

Technician

Reset print services and cache (safe steps):
1) On the print server, stop Print Spooler and your solution’s service (e.g., PaperCut Print Provider / uniFLOW Server).
2) Clear %systemroot%\\System32\\spool\\PRINTERS (leave folders, delete files only).
3) Start Print Spooler then the application service; confirm the Application Server is reachable on required ports (PaperCut 9191/9192/9195, uniFLOW 8000+).
4) Print a 1-page test to the Follow-Me virtual queue; check server job logs and device embedded logs for authentication errors, quota/credit limits, or device channel offline.

Customer

We moved users to Azure AD with Hybrid Join. Could that affect pull print release?

Technician

Yes — identity changes can break secure print release mapping.
• Ensure your solution syncs users from the same source used at devices (Azure AD / Entra ID vs on-prem AD). Align UPN and sAMAccountName and re-associate card numbers/PINs.
• For Microsoft Universal Print + PaperCut/uniFLOW, verify the connector and UP printer share permissions; grant users Printer Share access in Entra ID and re-register printers after directory scope changes.
• If you see “User not found” at the device, resync the directory and restart the authentication provider (IdP) module on the server.

Customer

Any network or driver settings that typically block Follow-Me release?

Technician

Driver & network checklist:
• Use the vendor Universal Print Driver (PCL/PS/XPS) or a stable Type 3 package; avoid Microsoft IPP Class Driver for Follow-Me queues requiring accounting/finishing.
• Match the queue port to the device: RAW 9100 or LPR with correct queue name; disable SNMP status while testing to avoid false offline.
• Keep time sync (NTP) across server and MFPs; JWT/SSO tokens fail with skew. Check firewall rules between devices and the app server.
• If using Secure Print / Hold Print at the device, disable local hold features that conflict with server-side pull printing.

Customer

Great. Can you summarize the fastest fix path we can try right now?

Technician

Quick path to restore pull printing: align user identity (owner = AD account), grant queue Print/Manage Documents, restart Spooler and the solution service, clear spool cache, and swap to a vendor Type 3 driver/UPD. If needed, re-pair the release station/Embedded to the server and test a 1-page job. Need help doing this live? Open the chat.

Quick answer: the accepted fix

Accepted fix when Follow-Me / pull printing is not releasing jobs: verify job ownership mapping (user ↔ card/UPN), correct queue permissions, restart Print Spooler and application service, clear spool\\PRINTERS, and test using a vendor Type 3/Universal Print Driver. Reconnect the release station/Embedded app and ensure ports 9191/9192/9195 are open.

FAQ

Step-by-step (Windows Server 2019/2022)

1. Open the Follow-Me virtual queue → Printer properties → switch to a Type 3 vendor UPD (PCL/PS); set Start printing after last page is spooled.
2. On Security tab, grant Domain Users = Print, service account = Manage Printers & Manage Documents.
3. Restart Print Spooler and your solution’s service; clear %systemroot%\\System32\\spool\\PRINTERS files.
4. Test release at the MFP; if missing, verify ports 9100/LPR and 9191/9192/9195, time sync, and directory sync.

Step-by-step (clients: Windows 10/11 & macOS)

1. Re-deploy the Follow-Me queue via GPO or vendor client; approve the server in Package Point and Print — Approved Servers.
2. Align usernames (UPN vs sAMAccountName) and relink cards/PINs for secure release.
3. Update client drivers to match the server’s UPD; disable client-side rendering if Type 4 caused ownership issues.

Sources

• Microsoft — Windows Print Server
• PaperCut — Knowledge Base
• Canon — uniFLOW
• PrinterLogic — Knowledge Base

Matt ● replies in < 1 min

Technician Expert

⭐⭐⭐⭐⭐ Trusted by 27,000+ customers

Alex · Expert's Assistant

Start Chat

5 Tech Support Specialists are online right now.