Fleet locates a problem quickly; Printer 360 explains it by combining current state with toner trends, counters, prior service and recurring faults.
Before you begin
- Know the serial number, internal label or site.
- Check telemetry age; stale data may not reflect current state.
- Before sending a command, check whether service is in progress.
Fleet is scope-aware
Fleet displays only devices available to the signed-in user. Use country, city, site, status, model and text filters.
Printer 360
The detail combines telemetry, toner, counters, service history, photos, audit and recurring faults. It is the primary source before service work.
Device commands
Use test print and other commands only on authorized devices. Each command has a status and traceable result.
Recommended practice
- Diagnose from availability through alarms to history.
- Use photos for orientation and configuration confirmation.
- Compare recurring alarms with material used in the previous repair.
Common pitfalls
- Online does not automatically mean healthy printing.
- A test print without someone on site may waste paper.
- Manual status changes without notes weaken service history.
How to verify the result
The operator gains one traceable device view before choosing remote resolution or a visit.
✓
Continuously updated for the current Printexus release.
Still need help? Contact support.