The Windows IPP service bypasses the standard Windows printing process and this can cause problems with the PaperCut user client print popups (e.g. account selection or authentication popups).
The Windows IPP service runs in IIS and when it accepts jobs over HTTP it then inserts the jobs into the standard Windows printer queue. When it does this it loses some important meta-data from the print job that PaperCut uses to determine where to send the popup. (This important meta-data includes the client workstation name/IP-address and the user that printed the document).
For example, jobs that are submitted through the Windows IPP service report the following attributes:
Client/Workstation: the print server name/IP Username: the IIS username The PaperCut user client uses this meta-data (client IP and username) to determine where the job was printed from, and where to deliver the popup notification.
We recommend not using the Windows IPP service for printing when you use the user client popups.
Articles in this section
- Manually Generating and Installing iOS AirPrint Profiles for Mobility Print (When Auto Setup Fails)
- Common Xerox Issues and how to fix them
- PaperCut NG/MF Security Bulletin (May 2025)
- How to permit users to cancel print jobs at HP MFD
- How to remove a print job from the queue
- Upgrading the PaperCut Hive Ricoh Full Embedded App
- Share ARM64 Drivers from Windows Print Servers
- Printing from Microsoft Edge Browser and other Windows 10 and 11 Store Apps
- Top 10 best practices for implementing Print Quotas in education
- PaperCut Hive and SentinelOne
Comments
0 comments
Please sign in to leave a comment.