Getting Started
This guide takes you from “I just got a ZenPrint tenant” to “my first endpoint is reporting printers.” Budget 15–20 minutes of hands-on time.
Before you begin
You’ll need:
- A ZenPrint tenant URL (e.g.
acme-msp.zenprint.io) and admin credentials - Admin access to your RMM
- One Windows endpoint at the customer site that’s already managed by that RMM
1. Log in and complete MFA
On first login ZenPrint makes you enrol an authenticator app. Scan the QR code with whichever app you use, then save the ten backup codes somewhere durable, because they’re shown only once.
If you lose your authenticator, enter a backup code at the login screen where it asks for the app code. Each backup code works once, and so does each 6-digit app code, so if you mistype one, wait for the next rather than re-entering it. Run out of backup codes with no authenticator to hand and an admin has to reset your MFA for you.
Until you finish enrolling, the account can’t do anything else. That applies to the API as well as the web pages, so your initial password on its own isn’t enough to set anything up.
Then ZenPrint asks you to replace the initial password you were given, on your profile page. Until you do, every page leads back there. The same happens after an admin resets your password.
The sidebar on the left holds the main pages (Dashboard, Clients, Drivers) at the top, and Audit log, Settings and the docs at the bottom. Click your name under them for your profile and logging out. The top bar holds the search box and, at the far right, the button that switches between light and dark. On a narrow screen the sidebar folds away behind the menu button in the top bar.
2. Connect your RMM
The endpoint authenticates to ZenPrint with one piece of information: an API key. The server URL is already baked into the bootstrap script you download (the script is per-tenant).
- Go to Settings → API keys → Create API key. Give it a name (e.g. “Production”) and create it as a full-access key (leave “read-only” unticked, since the bootstrap needs to write). Copy the key now, because it’s only shown once.
- In your RMM, store the key as a secure custom field that the bootstrap script can read, set per organization.
See RMM Setup for the exact field names, screenshots, and the per-vendor walkthrough.
3. Deploy the bootstrap script
The bootstrap script authenticates with your API key, checks the endpoint in with ZenPrint, then fetches and runs the signed script for the mode you specify.
- Go to Settings → Scripts and download the bootstrap PS1 for your RMM.
- Save it as a new script in your RMM. You can run any mode ad-hoc from the RMM at any time, or schedule it on an interval (see Scripts for the per-mode cadence recommendations).
- Run it once manually on your test endpoint with
-Mode Reconcile. Every mode checks the endpoint in first, so this registers the endpoint. With nothing assigned in ZenPrint yet, reconcile finds no queues to apply, which is expected; that comes later.
An endpoint only exists in ZenPrint once its bootstrap has run and checked in at least once, so run the bootstrap (use -Mode Reconcile) on every endpoint you want ZenPrint to manage.
Within a minute or two, the endpoint should appear on the dashboard under Waiting for approval (or No location, if your RMM groups aren’t mapped yet). Approve it there or on its location’s Endpoints tab. Endpoints stay Pending until you approve them; ZenPrint never auto-activates one. A pending endpoint still checks in, scans, and polls, but it won’t reconcile any queues until you approve it.
Rolling out to a whole fleet rather than one test machine? Schedule the bootstrap on Reconcile across the endpoints you want managed and let them register on their own. Then use Approve all on each location’s row under Waiting for approval on the dashboard, or tick endpoints on a location’s Endpoints tab and approve them together (see the Endpoints tab).
4. Verify
You should see:
- The endpoint on its location’s Endpoints tab with status
Active - Its currently-installed printer queues in the endpoint’s drawer (click its row on that tab)
- An entry in the audit log (Audit log in the sidebar) showing the endpoint registered
5. Optional: user accounts on endpoints
A ticket usually names a person (“Jan can’t print”), not a machine. ZenPrint can show the Windows accounts that signed in to each endpoint in the last 30 days, so searching for jan or jan.peeters@contoso.com finds her PC. It’s off by default, because these are personal details of your customers’ staff: check with them before you turn it on.
- Go to Settings → Workspace → Endpoint user accounts.
- Tick Show user accounts active in the last 30 days on endpoints.
- Review the Don’t show list. It starts with
Administrator. Add your own admin and service accounts, one per line;*and?are wildcards, somsp-*hides every account that starts with msp-. A line matchesDOMAIN\user, the user name or the sign-in name. Accounts on this list are never stored. - Save.
From the next check-in, the endpoint row shows the account signed in (or used most recently), and the endpoint’s drawer lists them all. Only accounts used in the last 30 days leave the endpoint, which matters on shared laptops with a long list of people who have come and gone. Entra ID (Azure AD) accounts show with their sign-in name. ZenPrint keeps only what the latest check-in reported; turning the setting off deletes everything collected.
Next steps
- Capture an existing driver: turn an installed printer’s driver into something you can reuse across the fleet
- Assign queues at scale: target locations, groups, or individual endpoints
- Set up users and roles: invite your team and scope them per-client