Driverless printing lets users add an OptimiDoc printer on Windows, macOS, Linux or ChromeOS using nothing but the built-in IPP (Internet Printing Protocol) support in the operating system — no vendor driver required. Jobs sent to the printer are received by OptimiDoc, matched to the sending user, and held until the user releases them at a device. This guide explains how OptimiDoc's IPP server works and how to install a driverless printer on client workstations.
How Driverless IPP Works in OptimiDoc
OptimiDoc runs a built-in IPP server as part of the OptimiDoc service (and on every printing node). It is always available — there is no separate service to enable. Its characteristics:
-
One port, both schemes. The server listens on TCP 631 and accepts both plain
ipp://and encryptedipps://on that single port. IPPS requires the server's TLS certificate to be present; when it is, secure printing works with no extra configuration. -
The user is identified by the OS, not by a password. IPP does not prompt for a password. Instead, the operating system sends the logged-in account name with the job, and OptimiDoc matches that name to an OptimiDoc user. A
DOMAIN\prefix is stripped and retried, and an optional login-matching rule can be applied. If no matching user is found, the job is rejected and recorded under Diagnostics > Unauthorised Accesses. IPPS provides the transport encryption; user identity comes from the OS account. -
Multiple printers from one server. In addition to the default endpoint, you can publish named IPP Queue connectors, each with its own print defaults (paper, colour, duplex, finishing) and its own install URL. This lets one OptimiDoc server present several distinct "printers" to different groups of users.
Once a job is received it is held in the user's queue (visible in Reports > All Jobs / My Jobs) and released at any device the user authenticates to — exactly like any other OptimiDoc pull-print job.
The IPP Endpoint URLs
Driverless printers use one of these URLs (replace server with your OptimiDoc server or printing-node address):
|
Target |
Secure (IPPS) |
Plain (IPP) |
|---|---|---|
|
Default printer |
|
|
|
A named IPP Queue connector |
|
|
The {queueId} for a named queue is 1000000000 + the connector's id; the exact URL is shown for you on the connector — you do not need to calculate it by hand. Always prefer the ipps:// form where the server certificate allows it.
The Easy Way — the Dashboard Printer Installer (Windows)
For Windows clients, the quickest method is the built-in installer widget:
-
On the OptimiDoc Dashboard, add the Printer Installer widget (if it is not already shown) via the dashboard's widget settings.
-
Enter a name for the printer (default: OptimiDoc Printer) and click Download.
-
Run the downloaded
.cmdscript on the client. It self-elevates (prompting for administrator rights), then tries to add the printer via IPPS first and falls back to IPP, using the standard WindowsAdd-Printercommand against/ipp/printon port 631.
The script targets the OptimiDoc server you are currently browsing, so distribute it from the server address your clients should print to. For scripted or mass deployment, the same Add-Printer -IppURL command can be pushed via GPO or your management tool.
Adding the Printer Manually
Windows
-
Open Settings > Bluetooth & devices > Printers & scanners and choose Add device, then Add manually.
-
Select Add a printer using an IP address or hostname.
-
Choose device type IPP Device and enter the endpoint URL, e.g.
https://server:631/ipp/print(or the named-queue URL). Windows negotiates capabilities over IPP automatically.
macOS
-
Open System Settings > Printers & Scanners and click Add Printer, Scanner or Fax.
-
Select the IP tab.
-
Enter:
-
Address:
server -
Protocol: Internet Printing Protocol – IPP (or IPPS on newer releases)
-
Queue:
ipp/print(oripp/print/{queueId}for a named queue)
-
-
Leave Use on the automatic driverless option and click Add.
Linux (CUPS)
lpadmin -p OptimiDoc -E -v ipps://server:631/ipp/print -m everywhere
Use -m everywhere so CUPS uses IPP driverless capabilities. For a named queue, append the queue id to the path.
ChromeOS
-
Open Settings > Printing > Printers > Add printer.
-
Enter the endpoint URL
ipps://server:631/ipp/print. ChromeOS auto-detects capabilities.
Firewall
Open inbound TCP 631 on the OptimiDoc server (or printing node) for the client networks that will submit jobs. If a network firewall sits between clients and the server, open 631 there as well.
Security Notes
|
Consideration |
Detail |
|---|---|
|
Transport encryption |
Prefer |
|
User identity |
The job owner is the OS account name matched to an OptimiDoc user — there is no separate IPP password. Ensure users' workstation account names correspond to their OptimiDoc logins (a login-matching rule can normalise them). |
|
Rejected jobs |
Jobs from an unrecognised user are rejected and logged under Diagnostics > Unauthorised Accesses — a useful place to diagnose identity mismatches. |
|
Per-queue access |
Named IPP Queue connectors are access-controlled by group, so you can expose specific queues to specific users. |
Troubleshooting
|
Problem |
Solution |
|---|---|
|
Client cannot connect to the printer |
Confirm TCP 631 is open end-to-end; test with |
|
Job is rejected / user shows as unauthorised |
The OS account name did not match an OptimiDoc user. Check Diagnostics > Unauthorised Accesses; align the account name or configure a login-matching rule. |
|
|
The server TLS certificate is missing or untrusted. On a printing node, ensure |
|
Wrong defaults (paper/colour/duplex) |
Adjust the queue's defaults on the Driverless Print (IPP) page, or install the correct named IPP Queue URL. |
In Summary
OptimiDoc's IPP server is always on, listens on port 631 for both ipp:// and ipps://, and identifies users by their operating-system account rather than a password. Point a client at ipps://server:631/ipp/print for the default printer, or at a named IPP Queue URL for a printer with its own defaults. On Windows, the Dashboard Printer Installer widget generates a one-click install script; other platforms use their native driverless (IPP Everywhere) support.
Related articles