Agents overview

Some work has to happen on a machine at your site: driving a card printer or reading a legacy database. Small programs, called agents, do that work and talk to CardOffice for you.

Agent	What it does	Runs on
Print agent	Claims print jobs, sends them to the card printer, and reports printer and ribbon state. Zebra ZXP Series 7 has the deepest integration	The print room PC
Sync agent	Bridges a legacy on-premises database in both directions. Ask us about this one: it is set up with you, not self-service	The machine hosting the legacy database

How agents connect

• Outbound HTTPS only. An agent opens connections to CardOffice. It never accepts an inbound connection, so nothing on your network has to listen for it.
• Enrolled once. Each machine enrols with an enrolment token and receives its own credential. You can see enrolled agents, and when each last checked in, in the portal.
• Leased work. The print agent claims a job under a lease and keeps renewing it. If the agent dies mid-run, the lease lapses and the job is requeued rather than stranded.
• Catch-up after an outage. An agent that loses its connection resumes from where it left off when it returns. It does not lose work.

Getting an agent

Download agents from Settings → Downloads in the portal. The download page shows the expected checksum so you can verify the file. If Windows blocks the file or warns when it runs, see Trusting the agent downloads on Windows.

Network requirements

The agent machine needs to reach your CardOffice host over HTTPS (port 443). If your network uses an outbound proxy or allow-list, add that host.