OptimiDoc Server Help Center

Shared Queue

The Shared Queue connector holds print jobs in a common, shared pool rather than a single user's personal queue. Any user with access to the connector can browse the queue at a device and release any job in it, and the cost is charged to whoever releases it. It is designed for shared or public printing scenarios -- reception desks, communal printers, and shared cost centres.


https://optimidoc.atlassian.net/wiki/download/attachments/43253761/connector-shared-queue.png?api=v2

Screenshot: Shared Queue connector configuration

Overview

A normal pull print job is owned by one user and can be released only by that user. A Shared Queue works differently: its jobs are held in the Shared state, not tied to an owner. Anyone whose groups grant access to the connector sees the queue on the device panel and can release any waiting job. Because the job has no fixed owner, the pages and cost are attributed to the user who releases it.

The connector points at a shared Windows print queue. Jobs sent to that queue are captured by OptimiDoc and held as shared jobs until someone releases or they expire.

Typical uses:

  • A public or reception printer where any staff member may collect a job

  • Shared departmental output that should be billed to whoever prints it

  • Communal queues for temporary or guest use


How It Works

  1. An administrator shares a print queue on a Windows print server and points the connector at it.

  2. A job sent to that queue is captured by OptimiDoc and stored in the Shared state.

  3. The Shared Queue appears on the device panel only when it holds shared jobs, with a count of waiting jobs beside its name.

  4. Any user with access authenticates, opens the queue, and selects jobs to release.

  5. Released jobs pass through the rules engine and quota checks, and the cost is recorded against the releasing user.


Configuration

  1. Navigate to Printing > Print Connectors and click Add Connector.

  2. Enter a Name (e.g. "Reception") and select Shared Queue from the Type dropdown.

  3. On the Configuration tab, set the queue.

Configuration Settings

Setting

Description

Print Queue

The UNC path to the shared Windows print queue (e.g. \\server\printer).

  1. On the Access Rights tab, assign the Groups whose members may release jobs from this queue.

  2. Click Save.


Setting Up the Windows Print Queue

  1. On the Windows print server, add a printer and share it with a clear name.

  2. Configure it so jobs are captured by OptimiDoc rather than sent straight to hardware (a local or NULL port).

  3. Deploy the shared printer to workstations via Group Policy, a login script, or manual installation.

  4. Point the connector's Print Queue at the share's UNC path.


Shared Queue vs Personal Pull Print

Aspect

Personal pull print

Shared Queue

Job state

Waiting

Shared

Who can release

The owner only

Any user with connector access

Cost attributed to

The job owner

The releasing user


Troubleshooting

Issue

Resolution

Queue not visible on the device

The Shared Queue appears only when it holds shared jobs, and only to users whose groups have access. Confirm both.

Jobs not captured

Verify the Print Queue UNC path and that OptimiDoc has permission to read from the shared queue.

Jobs print immediately

Ensure the Windows printer port does not point at a physical device, so OptimiDoc can intercept the jobs.


Related articles