Common end-user tickets and how to triage them

Most Printix tickets cluster into three buckets: the user can’t sign in, the user can’t see the printer they want, or the user submitted a job and nothing happened. Each bucket has a small set of likely causes, and the Administrator surfaces all of them. The trick is asking the right four questions in the right order.

The four-question triage

flowchart TD
    Q1[1. Can the user sign in<br/>to the Printix Client?] -->|No| F1[Sign-in path:<br/>identity, conditional access,<br/>Microsoft Entra join state]
    Q1 -->|Yes| Q2
    Q2[2. Is the Printix Client<br/>online on their computer?] -->|No| F2[Agent path:<br/>service running, network,<br/>proxy config]
    Q2 -->|Yes| Q3
    Q3[3. Can they see the right<br/>print queue?] -->|No| F3[Visibility path:<br/>group membership,<br/>site/network match,<br/>queue active]
    Q3 -->|Yes| Q4
    Q4[4. Did the job actually<br/>reach the printer?] -->|No| F4[Job path:<br/>App History,<br/>Computer Diagnostics,<br/>printer status]
    Q4 -->|Yes| OK[Issue is at the printer<br/>or the document]

Each question has a console move. None of them require touching settings.

1. Can the user sign in?

The Printix Client opens to a sign-in screen. If sign-in fails, three documented causes:

• Conditional Access blocked them. The error “Your sign-in was successful but does not meet the criteria to access this resource” means the customer’s Microsoft Entra Conditional Access policy denied Printix. Outside frontline scope unless the customer has explicitly granted you the change.
• Microsoft Entra join state. On a Microsoft Entra-joined Windows 10 or 11 machine sign-in is supposed to be automatic. The first sign-in sometimes isn’t, and a restart usually fixes it.
• Loop back to sign-in page. Repeated bouncing back to the sign-in page is its own documented troubleshooting path; collect logs and escalate.
• PIN-code lockout at the printer. A user who fails the 4-digit PIN at a Printix Go touchscreen three times has the PIN disabled. They have to re-enrol from the Printix App before card or PIN sign-in works again at the device.

2. Is the Printix Client online?

Menu, Computers, find the user’s hostname. Status column says Online or Offline.

If Offline:

• The Printix Service might not be running. The user (or remote-management tool) restarts the service.
• The computer might not have Internet to *.printix.net. Check the customer’s web proxy / firewall rules.
• For Mac, Jamf or Addigy may have updated the agent in a way that broke the install. Reinstall via the Software page.

3. Can they see the right print queue?

Open the Printix Client. Menu, Printers. The list is filtered by group membership and current network.

If the queue is missing:

• Group access. Printer’s print queue properties has a Groups tab. Open Administrator, Printers, the printer, Print queues, the specific queue, Groups. Confirm the user’s Microsoft Entra group is listed (and group sync is healthy).
• Network mismatch. The user’s computer is on a network that doesn’t have access to that printer. Computer properties shows the current network. If they’re on a home network, this is expected; tell them to use Print Anywhere or Home Office printing if enabled.
• Queue inactive. Administrator-only printers show with a star ★ after the printer ID for admins, and don’t show at all for users. Check the Print queue properties for the Active flag.

4. Did the job reach the printer?

Two log surfaces:

• The user’s Printix App History. Print history for the last 30 days. If the document is missing, the user didn’t actually submit (or submitted via Print Later and hasn’t released yet).
• The Computer’s Diagnostics tab. Per-machine counts since the last service restart, including New (jobs queued by the Printix Client) and Printed in total (jobs the client has actually delivered to a printer). If “New” went up but “Printed in total” didn’t, the job is stranded somewhere between Printix Client and printer.

A worked ticket: Northwind Logistics

Northwind Logistics is a mid-market warehouse with shift work. A driver opens a ticket: “I sent shipping labels to BNM Loading Dock at 6am, nothing came out, my shift’s over.”

1. Sign-in OK?

   Driver signs in fine to the Printix Client. Skip question 1.

2. Computer online?

   Administrator, Computers. Driver’s tablet last reported online at 06:14. Currently Offline (driver took the tablet and left). The job was submitted, but Print Later jobs need the source computer up to release.

3. Queue visible?

   Driver could see and select BNM Loading Dock. Skip question 3.

4. Job reached the printer?

   BNM Loading Dock’s History shows zero entries for the user that morning. Confirms the job never reached the printer; it was stuck on the offline tablet.

5. Resolve and prevent

   The driver reopens the tablet on the dock network, the job releases, the labels print. Document the recurrence, escalate to the customer’s account lead to enable Azure Blob Storage so shift workers don’t have this exact problem next week.

Loading quiz…

What this is NOT

• Not a print-driver troubleshooting flow. “Document is empty” or “garbled output” usually points at a print driver issue (wrong driver, missing tray, bad PDF processing). That’s a different lesson, in the Intermediate course’s driver-delivery section.
• Not for Printix Go device-side issues. When the user signs in fine on the touchscreen but a Capture or scan fails, that’s vendor-specific (Brother, Canon, HP, Konica Minolta troubleshooting). Beginner course doesn’t cover those.