Print queues on standby clients: which names you need so the group survives failover

01

The question the configuration starts from

The operational question is simple: which queues must be configured on standby clients? Nebulas cloud printing's answer is just as simple: the same queues, under the exact same name, used by the preferred client. An active/standby group keeps the same print destination available even when a workstation is unreachable, disabled, or loses authorization, because the Print Gateway assigns the group a single leader via a renewable lease; if the leader becomes unavailable, a standby automatically takes over leadership.

02

How to replicate queues on standby clients

Steps

1. List the exact local queue names the management system calls on the preferred client.
2. Install the client on standby workstations that can reach the same printers.
3. Replicate the same queue names on each standby workstation, without variations.
4. Complete login and MFA in the browser and authorize each PC separately.
5. In the Portal assign the clients to the same group and set different priorities, then check heartbeat, status, and active client before use in production.

03

Starting technical conditions

Prerequisites

• Same queue names on every member of the HA group.
• Supported systems: Windows x64, macOS Intel or Apple Silicon, Linux x64.
• Documents in PDF format and queues already installed and visible to the operating system.
• Outbound HTTPS access to Nebulas services.
• Nebulas user with the Cloud Printing module active.

04

Hypothetical example: reception with a shared backup client

Hypothetical example. Three workstations serve two print groups: 'Reception' with priority 1 on a dedicated workstation and priority 2 on a shared backup workstation, which exposes the local queue 'RECEPTION_PRINTER' under the exact same name as the dedicated workstation. If the dedicated workstation stops during download, the job returns to pending and is picked up by the backup. If instead it stops after delivery to the spooler, the job moves to DELIVERY_UNKNOWN and is not automatically reprinted, avoiding duplicate copies.

05

Checks on queue names

• Confirm that queue names are identical across all group members.
• Leave a job pending when an indicated queue is not found, without diverting it to another printer.
• Verify heartbeat, status, detected queues, and active client before use in production.
• Verify the physical outcome of a DELIVERY_UNKNOWN job before deciding how to proceed.
• An administrator can disable, remove, or deauthorize a client from the Portal at any time.

06

The priority and lease mechanism behind the queues

In the Nebulas Portal the administrator assigns two or more clients to the same print group and sets a numeric priority, with the lowest number indicating the preferred client. The Print Gateway assigns a single leader via a renewable lease; the operations that take on a job check both the active leader and the lease epoch, so a previous isolated leader cannot start new jobs after the handover to a standby.

07

Verification sequence for the IT team

Steps

1. Compare the queue names on the preferred client with those required by the management system.
2. Replicate the identical names on every candidate standby workstation.
3. Authorize each PC separately with a recent login and strong MFA.
4. Set priorities in the Portal, assigning the preferred one the lowest number.
5. Run a controlled failover test before releasing into production.

08

Next step

Before activating an active/standby group, compare the queue names on each candidate workstation line by line and confirm priorities in the Portal. A heartbeat and status check prevents a mismatched name from staying hidden until the first real failover.