How print jobs flow from IGEL OS endpoints
A print job from an IGEL OS endpoint takes one of three paths, depending on where the application that prints is running. If it's a local IGEL OS app, such as the browser on the device, the job goes through the ScrewDrivers Printers app on the device and the ScrewDrivers Gateway to a ScrewDrivers Print Server. If it's an app in a VDI or remote desktop session reached from the device, the ScrewDrivers printers in that Windows session handle it, most often by sending it to a ScrewDrivers Print Server. And if the user needs a printer that only the IGEL device knows about, the Endpoint Client redirects the device's own CUPS printers into the session over the ScrewDrivers virtual channel.
This page explains what runs where in each path, how each hop is secured, and what happens when part of the path is unavailable. The paths aren't mutually exclusive: the same IGEL endpoint can use all three at once.
What runs where
An IGEL deployment involves three places where software runs: the IGEL OS endpoint, the session host where remote applications run, and the ScrewDrivers infrastructure behind both.
On the IGEL OS endpoint, two separate ScrewDrivers components can run, and they do different jobs:
- ScrewDrivers Printers is an app from the IGEL App Portal, and it's the primary way ScrewDrivers supports IGEL devices. It finds the print server printers that an administrator assigned to the user or device in ScrewDrivers Administration and creates a CUPS queue on the device for each one. CUPS is part of IGEL OS; ScrewDrivers doesn't supply it, it just adds queues to it. Each queue uses a generic PPD that ships with the app, so the device doesn't need a manufacturer driver for any printer. ScrewDrivers Printers connects to the ScrewDrivers Gateway. The preferred way to give it the Gateway address is in the app's profile in IGEL Universal Management Suite (UMS); users can also enter it in the app when they launch it.
- The Endpoint Client reads the printers that already exist in CUPS on the device and redirects them into remote sessions (Citrix, or RDP and Azure Virtual Desktop through FreeRDP) over the ScrewDrivers virtual channel inside the RDP or ICA connection. It doesn't use the Gateway. This is redirected printing, also called client printing.
On IGEL OS 12, both apps come from the IGEL App Portal. On IGEL OS 11, the Endpoint Client was deployed as a custom partition through UMS. That's now the legacy method; ScrewDrivers on IGEL still documents it for OS 11 devices.
In the remote session, the ScrewDrivers session agent runs on the session host: the RDS host, Citrix VDA, or virtual desktop where the user's applications run. It builds the ScrewDrivers printers in the user's Windows session, including the redirected printers that the Endpoint Client reports.
Behind the endpoint and the session host sits the ScrewDrivers infrastructure that the first two paths depend on. The ScrewDrivers Gateway is how the ScrewDrivers Printers app on IGEL devices reaches the ScrewDrivers backend: it listens on TCP 4600 for non-Windows platforms, and ScrewDrivers 7.9.4 added a device authentication mode for them. The ScrewDrivers Print Server is the service on your Windows print servers that renders jobs with the manufacturer driver and sends them to the physical printer. ScrewDrivers Administration, the SQL Server database, and the Tricerat License Server hold the printer definitions and assignments. The port reference lists the ports between them.
Path 1: IGEL OS app to a ScrewDrivers Print Server
This is the primary path for printing from apps that run locally on the IGEL device. It needs ScrewDrivers Pro or Enterprise.
- Queue creation. The ScrewDrivers Printers app finds the print server printers assigned to the user or device in ScrewDrivers Administration and creates a CUPS queue on the device for each one, using the generic PPD that ships with the app.
- Printing. A local IGEL OS app prints to one of those queues, the same way it would print to any CUPS printer.
- To the Gateway. The job leaves the device and goes to the ScrewDrivers Gateway on port 4600.
- To the print server. The Gateway passes the job to the ScrewDrivers Print Server that hosts the printer.
- Rendering and delivery. The ScrewDrivers Print Server renders the job with the manufacturer driver installed on the print server and sends it to the physical printer.
Because rendering happens on the print server, the manufacturer driver lives only there. The IGEL device carries the generic PPD, and nothing else printer-specific.
Path 2: VDI session app to a ScrewDrivers printer in the session
When the user connects from the IGEL device to a Citrix, Azure Virtual Desktop, or RDP session, applications in that Windows session print to the ScrewDrivers printers the session agent built there. The IGEL device isn't involved in this path at all.
The main case is print server printing:
- Assignment. When the user signs in, the session agent gets the printers assigned to that user from the ScrewDrivers database and creates them in the session, using Tricerat's virtual driver.
- Printing. The application prints to one of those printers, and the virtual driver captures the job and the user's print settings.
- To the print server. The session agent sends the job to the ScrewDrivers Print Server on ports 5550–5553.
- Rendering and delivery. The ScrewDrivers Print Server renders the job with the manufacturer driver and sends it to the physical printer.
Pro: Print Server Printing Architecture covers this flow in depth. Because the session is Windows, any other ScrewDrivers printing method also works here. For example, Direct IP printing sends jobs straight from the session host to a network printer with no print server in the path.
Path 3: redirected CUPS printers through the Endpoint Client
This is redirected (client) printing, the secondary path. It's for printers that the IGEL device knows about through CUPS but that aren't assigned through ScrewDrivers Administration. It works with any v7 edition on the session host: Essentials, Pro, or Enterprise.
- Session start. When the user connects, the Endpoint Client on the IGEL device tells the session agent which printers exist in CUPS on the device.
- Printer creation. The session agent creates a matching printer in the user's session for each one, using Tricerat's virtual driver, so the session host doesn't need the manufacturer's driver.
- Capture. The user prints from an application in the session, and the virtual driver captures the job and the user's print settings.
- Over the virtual channel. The session agent compresses the job and sends it to the device over the ScrewDrivers virtual channel, the side channel inside the ICA or RDP connection that already carries the session. It doesn't need any additional firewall ports.
- Printing on the device. The Endpoint Client receives the job and hands it to the CUPS queue on the device, which delivers it to the printer.
For Citrix sessions, the Endpoint Client loads into Citrix Workspace app with no extra connection settings. For RDP and Azure Virtual Desktop connections, which IGEL OS makes through FreeRDP, the connection needs a FreeRDP --dvc argument that loads the ScrewDrivers plug-in (libsdigelrdp-client.so). Installing the ScrewDrivers Endpoint Client for Linux covers the client in general, and Essentials: Client Printing & Redirection Architecture describes the redirection pattern on every platform.
Where encryption applies
The rule is simple: wherever ScrewDrivers manages the network connection, it uses TLS 1.2. Over the virtual channel, ScrewDrivers relies on the security of the host protocol (ICA or RDP) rather than adding its own TLS. Two hops are never ScrewDrivers' to encrypt: the hand-off from an application to a print driver, and the hop from a print server or device to the physical printer, which happens after the manufacturer driver has rendered the job.
| Path | Hop | How it's secured |
|---|---|---|
| 1 | IGEL OS app → ScrewDrivers Printers CUPS queue | Local hand-off on the device; not a ScrewDrivers network connection |
| 1 | IGEL device → ScrewDrivers Gateway (port 4600) | TLS 1.2 |
| 1 | ScrewDrivers Gateway → ScrewDrivers Print Server | TLS 1.2 |
| 2 | Session app → ScrewDrivers printer in the session | Local hand-off on the session host; not a ScrewDrivers network connection |
| 2 | Session host → ScrewDrivers Print Server (ports 5550–5553) | TLS 1.2 |
| 1 and 2 | ScrewDrivers Print Server → physical printer | Happens after the manufacturer driver; depends on the printer's protocol and configuration, not on ScrewDrivers |
| 3 | Session host → Endpoint Client, over the virtual channel | The host protocol's security (ICA or RDP); ScrewDrivers doesn't add its own TLS |
| 3 | Endpoint Client → CUPS → physical printer | The device's own printing system; not ScrewDrivers' to encrypt |
So Path 1 is encrypted with TLS 1.2 end to end, from the device through the Gateway to the ScrewDrivers Print Server. For Path 3, how well the job is protected in transit depends on how the ICA or RDP session itself is secured. ScrewDrivers Client Security describes how the Endpoint plug-in works within the host protocol's security layers, and the Version 7 TLS 1.2 Support notes cover the TLS details by version.
When the Gateway or a print server is unavailable
Path 1 depends on the ScrewDrivers Gateway. If an IGEL device can't reach the Gateway, it can't send print jobs through the ScrewDrivers Printers queues until the Gateway is reachable again. If you've configured print server failover, it applies between the Gateway and the print servers: when the primary ScrewDrivers Print Server is unreachable, jobs go to the failover servers in order.
Path 2 doesn't involve the IGEL device after the user connects, and Path 3 rides inside the session connection, so both need an active remote session.
Related pages
- ScrewDrivers on IGEL: the legacy IGEL OS 11 custom-partition method for deploying the Endpoint Client
- Installing the ScrewDrivers Endpoint Client for Linux: how the Linux client redirects CUPS printers
- Installing the ScrewDrivers Gateway: set up the Gateway that IGEL devices connect to
- Pro: Print Server Printing Architecture: how the ScrewDrivers Print Server renders and routes jobs
- Essentials: Client Printing & Redirection Architecture: the redirection flow behind Path 3
- Ports and Firewall Rules: which components talk to which, and on what ports