Clients, Locations and Printers
Every client, location and printer has its own page with its own address. You can bookmark them, paste them into a ticket, and use the browser’s back button to step back up. Start from Clients in the sidebar. Each page has a breadcrumb back to the level above.
Clients
Clients in the sidebar opens the clients column: every client you can see. A client or location with something that needs a look gets a coloured dot and a count, from the same list the dashboard’s Needs attention shows:
- Red, something to act on: failed installs, endpoints waiting for approval, stale assignments.
- Amber, something to review: missing or unconfirmed printers, new printers found by a scan, printers answering on a new IP address, printers with Raw printing (port 9100) turned off, a location no endpoint has scanned in the last 7 days, removals that didn’t happen, queue settings a printer refused.
Hover the count to see how it splits. Config drift, low supplies and duplicate queues show on the dashboard only. You only count what your role can see. The filter box matches client and location names, and issues first puts red before amber, most first; that choice is remembered in your browser.
The column stays beside every client, location and printer page, open on the client you’re in and marking where you are, so you can jump between clients and locations without going back. Click the arrow next to another client to see its locations. Long names are cut short; hover one for the full name. The column keeps its filter and scroll position as you move from page to page. On a narrow screen it sits under the top bar, above the page.
Search
The search box at the top of every page finds clients, locations, printers, endpoints and queues. Type at least two characters: a name, a hostname, a user account or sign-in name (when your workspace collects them), an IP address, a serial number, or a MAC address in any format (AA:BB:CC:DD:EE:FF, aa-bb-cc-dd-ee-ff or aabbccddeeff). The box shows the first few matches of each kind; press Enter for all of them. A printer opens its printer page, a queue its queue page; an endpoint opens its location’s Endpoints tab, filtered to that endpoint. You only find what your role can see.
Client page
/clients/<id> shows one card per location with its printer, queue and endpoint counts, and a short list of what needs attention there:
- failed installs
- endpoints waiting for approval
- missing printers
- printers answering on a new IP address
- printers with the Raw port (9100) closed
- new printers found by a scan
A location with none of these says so. Click a card to open the location. Queues at the top opens every queue at the client.
History below the cards (if your role can see the audit log) shows recent changes anywhere under the client: its locations, printers, queues, groups and endpoints. Full audit log opens the audit log filtered to the client; clear the Client chip there to see everything. Entries written before ZenPrint recorded the client on each change only show there when they were about the client or one of its locations. Routine script reports (scans and reconcile runs) stay out of the client view; they’re in the full audit log.
Location page
The location page is where most day-to-day work happens. It has four tabs, and the address remembers the open one (#unmanaged, #endpoints, #groups), so a bookmark or a reload opens the same tab. Assign queues at the top picks which queues every endpoint at the location gets. History (recent changes to the location, its printers and their queues, if your role can see the audit log) sits below the tabs. When no endpoint has scanned the location in the last 7 days, an amber line under its name says so and names the endpoint that scanned it last; the Endpoints tab shows whether that endpoint still checks in. Under the location name the header also shows its address, the networks its scans sweep (Auto-detect when none are set; change them under Edit location) and its notes.
Printers tab
Every printer at the location, with its IP address, hostname, MAC address, serial number, status and toner levels, so two printers of the same model are easy to tell apart. Under the status, Seen 3h ago says when a scan last saw it: amber with a ⚠ when no endpoint has confirmed it in the last 7 days, red once every endpoint that used to see it has scanned without finding it. When the whole location hasn’t been scanned in that time, the printers stay grey: the header’s warning covers them, since nothing is known to be wrong with the printers themselves. Hover it to see which endpoint confirmed it last. A tray icon means a driver capture is pending; Capture driver and Cancel capture are in the printer’s ⋯ menu. Each printer’s queues sit directly under it: the driver, the queue’s settings (duplex, colour, paper size, collate), where it’s assigned and how the install went. Click a queue’s name to open its queue page, or its install badge to jump straight to its endpoints. Add printer at the top adds one here; each printer’s ⋯ menu adds a queue or edits the printer, and each queue’s menu assigns, edits or deletes it.
Under each printer, one coloured dot per toner or ink cartridge shows its level, red when low. When another supply is low, such as a waste box or a maintenance kit, a warning says so; the printer page has the full list.
Dismissed printers are hidden from the list. They’re collected under Dismissed below it, each with Restore.
Unmanaged tab
Queues the scan found on endpoints here that ZenPrint didn’t create. The same queue on several endpoints is one row, with the endpoints named, the queue’s driver and its port type (WSD, TCP/IP, USB and so on). When reconcile couldn’t remove a queue you marked, the row says so in red, with the reason. The tab’s label counts the rows still to decide (allowed ones aren’t counted), and says how many are duplicates you can remove right away.
Endpoints tab
Every endpoint at the location with its OS, group, last check-in and status. When your workspace collects user accounts, the account signed in (or used most recently) shows under the hostname, the drawer lists every account used in the last 30 days, and the search box matches them:
- Active: registered and reporting normally.
- Pending: checked in, waiting for your approval. It won’t install any queues until you approve it; ZenPrint never approves one on its own.
- Inactive: deactivated, no longer reconciling.
Tick endpoints to approve or deactivate them in one go, or to move them into a group. The tab’s label shows how many are waiting for approval. The Unmanaged filter narrows the list to endpoints that report queues ZenPrint doesn’t manage, or to the ones that don’t: useful when you’re taking over from another print tool and want to watch the leftovers disappear.
Click a row to open the endpoint’s drawer. It puts what ZenPrint wants on the endpoint next to what the endpoint reports, with a state between them:
- In sync: assigned, installed, and its settings match.
- Config drift: installed, but its settings on the machine differ from the queue’s.
- Install failed: the last attempt failed; the endpoint’s error is on the row.
- Pending install: assigned, not on the machine yet. It lands on the next reconcile.
- Missing on endpoint: ZenPrint installed it, but the endpoint stopped reporting it, usually because someone deleted it. The next reconcile puts it back.
- Removing: queued for removal on the next reconcile.
- Not assigned: ZenPrint installed it, but nothing assigns it here any more. The next reconcile removes it unless you assign it back.
Problems sort to the top. Each row says where the assignment comes from (Direct, a group, or the location); you can unassign a direct one right there, and change an inherited one at its group or location. Assign queues in the drawer picks which queues this endpoint gets directly. Below, the drawer lists the endpoint’s unmanaged queues with the same actions as the Unmanaged tab.
Groups tab
Each endpoint group with how many endpoints are in it and how many queues are assigned to it. Add group, Edit and Delete manage the groups; Assign queues picks which queues the whole group gets. Move endpoints into a group from the Endpoints tab.
Filters
Every list can be filtered. Endpoints have a search box plus status and unmanaged filters. Printers, unmanaged queues, groups and (on the client page) locations have a filter box; all but groups also have a status filter next to it: printer status, unmanaged state, or Needs attention for locations.
Where a queue is assigned
The assignment is always one line, counted by type: for example Whole location, Group: Front desk, or Whole location · 2 groups · 40 endpoints. Endpoints assigned one by one are counted, not listed, so a queue on 300 endpoints doesn’t fill the page. Assign in the queue’s menu opens its Assignments page, which lists every target.
Install state
The badge next to each queue counts the endpoints it should be on and how many are in sync. When something is wrong the worst problem leads:
| Badge | Meaning |
|---|---|
| 2 failing · 36 of 38 in sync | The install failed on 2 endpoints, or ZenPrint recorded it as installed and the endpoint no longer reports it. |
| 3 drifted · 35 of 38 in sync | Installed, but the settings on 3 endpoints differ from the queue’s configuration. |
| 4 pending · 34 of 38 in sync | Waiting for the endpoints’ next reconcile run. |
| 38 of 38 in sync | Installed everywhere it’s assigned. |
Unmanaged states
Each row on the Unmanaged tab says why it’s there and what fixes it. Hover Deploy queue or Create queue: a ZenPrint queue with the same name takes the existing queue over instead of duplicating it.
| Badge | What it means | Action |
|---|---|---|
| Redundant | A ZenPrint queue for the same printer is assigned to these endpoints and installed on them. | Remove duplicate marks the old queue for removal. It’s removed on the next reconcile, and only once the ZenPrint queue is confirmed installed; if it can’t be confirmed, the queue stays. |
| Allowed | A queue you allowed to stay, whatever its state was. It stays on the endpoints and is no longer counted on the tab or, for a duplicate, the dashboard. | Flag again puts it back in its state. |
| Deployable | ZenPrint has a queue for this printer, but it isn’t installed on these endpoints yet. | Deploy queue assigns the queue(s) you pick to each of these endpoints. |
| Needs queue | ZenPrint knows the printer but has no queue for it. | Create queue for that printer. |
| Unknown | Not a printer ZenPrint knows at this location: a USB or home printer, a queue from another print tool, a WSD queue it can’t resolve. | Remove from endpoints removes it on the next reconcile. Nothing replaces it, so anyone printing to it loses it. |
Every row also has Allow: for a queue that belongs on the endpoints as it is, such as a USB label printer or a home printer, or a duplicate you want to keep. It stays where it is, moves to the bottom as Allowed, and stops being flagged.
Nothing is ever removed on its own. Reconcile also refuses to remove a queue ZenPrint has since taken over.
Printer page
The printer page shows:
- Device: IP address, hostname, MAC address, serial number, placement, how it was found, when it was first and last seen by a scan, which endpoint last confirmed it, and whatever the printer reports about itself (firmware, print languages, colour, page count, contact, uptime). Those last facts are for information only.
- Health: Confirmed by a recent scan when an endpoint’s scan saw it in the last 7 days, Not confirmed recently when none has, and Not seen by any endpoint once every endpoint that used to see it has scanned again without finding it. That last one also fires the
printer.offlinewebhook once. Scans run when your RMM runs them, so health only moves when they do. - Supplies: every supply the printer reports, with when it was last polled, sorted toner and ink first.
- Queues: the printer’s queues, listed as on the location page: driver, settings, where each is assigned and its install state. Click one to open its queue page, which lists every endpoint with the actual error when an install failed.
- History: recent changes to the printer and its queues.
From the printer page you can edit or delete the printer, add a queue, and assign, edit or delete each queue from its ⋯ menu. You can also request or cancel a driver capture, accept or dismiss a new IP address, dismiss a discovered or missing printer if it has no queues, and restore a dismissed one. A dismissed printer’s MAC address stays blocked, so later scans don’t add it back. Deleting a printer takes you back to its location.
Placement is a free-text note for where the printer sits within the site, such as “Reception, 2nd floor”. If the printer reports an SNMP location, the first scan fills it in; your own edit always wins.
Supply states
Not every printer reports a percentage, and the table says so rather than inventing one:
- OK: a normal reading.
- Low: at or below the alert threshold (15%).
- No percentage: a real level on a scale that can’t become a percentage, such as sheets or grams. It can’t raise a low-supply alert.
- Some remaining: the printer only says there is some left. It rules out empty, so it doesn’t alert either. Current Brother lasers report toner this way over standard SNMP, so ZenPrint reads their toner percentage from Brother’s own maintenance data instead and they show a normal reading; an older Brother can still show this state.
- Unknown: the printer reported nothing usable.
The last three are limits of the device, not faults in the reading. Supplies come from the supply poll script, which your RMM runs on its own schedule; one endpoint at a site covers its printers. ZenPrint reads SNMP v1 and v2c with the public community, so printers with SNMP off, locked to v3 or on another community don’t report supplies.
Queue page
/queues/<id> is one queue under its printer: the breadcrumb runs Clients › client › location › printer › queue. The header shows the queue’s status, its install state, the printer it prints to, its driver and its settings, with Edit, Delete and Assign. Deleting a queue takes you back to its printer.
Endpoints lists every endpoint the queue should be on, with the assignment summary above it:
- Assigned via: direct, a group, or the location. That tells you where to change it.
- State: in sync, pending install, config drift, install failed, missing on endpoint, or not assigned any more, with the endpoint’s error when an install failed.
- On the endpoint: the queue’s name and driver as the endpoint reports them.
- Last verified: when a reconcile last confirmed it.
A direct assignment can be removed from its row (Unassign); one that comes from a group or the location is changed there. History shows changes to the queue and to its assignments, including removed ones.
Queues page
/queues lists queues across your clients. It isn’t in the sidebar: Queues on a client page opens it for that client, and a driver’s queue count on the Drivers page opens it for that driver. Filter by client, status or text; a driver or location filter shows as a chip you can clear.
Click a queue’s name to open its queue page, or its assignment count to see its endpoints right in the list (with Open queue to go to its page). Tick queues to act on them together:
- Assign to… / Unassign from…: one location, group or endpoint. Pick a single client in the filter first, since the target belongs to one client.
- Change driver: move the selected queues to another driver, for example after capturing a newer one. It takes effect on the next reconcile.
- Delete: removes the queues; endpoints remove them on their next reconcile.
Endpoints with no location
An endpoint that checks in without a location (its RMM group isn’t mapped yet) appears on the dashboard under No location, which opens a list of them with the RMM group each reports. Move to location puts one at a client’s location. Mapping the group under Settings → Group mapping places every endpoint in it at once. Only roles that aren’t limited to certain clients see these, because an endpoint with no location belongs to no client yet.
Permissions
The pages follow your role. You only see clients your role is scoped to, and each section appears only if you can view what it shows: printers need printer access, queues need queue access, the Unmanaged, Endpoints and Groups tabs need endpoint access, and History needs audit log access.