FAQ

Frequently asked questions.

For architecture, requirements, and the security model, see the documentation.

Does HiFi Print require cloud or internet access?
No. The appliance, the agents, and subscription key validation all work offline. Updates are applied out of band as signed bundles.
Do I need Active Directory?
No. HiFi Print works on workgroup and domain machines alike. AD/LDAP integration is optional and used for sign-in and group-to-role mapping.
How does it compare to a Windows print server?
No print server is required. Printer queues are created on the endpoint and print jobs go direct to the printer over IP, so a spooler problem is limited to one machine.
What about VDI and non-persistent desktops?
Clones receive their own certificates, drivers can be pre-staged into the image, and rules can match the hostname or the connected thin-client name so printers follow the user across a pool.
How are drivers managed?
Driver packages are uploaded to a central library where every INF is parsed and scored and the model list is extracted, so the correct spooler driver name is selected. Printer profiles (name, IP, driver, port, duplex, SNMP, comment) are then assigned to groups, endpoints, or hostname rules.
What logging and reporting is included?
Push jobs, driver installs, and admin actions are logged with timestamp and user. Print history, cost reporting, and scheduled reports are available from the console.

Still stuck? Contact support.