2022.2
Table Of Contents
- Table of Contents
- What is Connect Send?
- Installation
- Printer driver
- Workflow Plugins
- Connect Send database cleanup service
- Moving Workflow to another machine
- Prerequisites
- System Requirements
- Installing OL Connect Send Printer Driver
- Printer driver properties and advanced settings
- Mass deployment of the OL Connect Send Printer Driver
- Using API Keys
- OLCS Notifier
- Known Issues
- Existing OL Connect Send Upgrade Issue
- Installing OL Connect Send on Windows Server 2016
- Installing OL Connect Send on a machine with Connect installed
- OL Connect Send issues under Microsoft Edge browser
- Printing PDF files with Adobe Acrobat Reader
- Paper Size vs Printer Page Size
- Passthrough Printing not supported
- License modes
- OL Connect Send in Workflow
- Using the Printer Driver
- Log files
- Troubleshooting
- OL Connect Send 2.1.2 Printer Driver Release Notes
- Overview
- Important Notes
- OL Connect Send 2.1.2 Printer Driver
- OL Connect Send 2.1.1 Printer Driver
- OL Connect Send 1.8.0 Printer Driver
- OL Connect Send 1.7.0 Printer Driver
- OL Connect Send 1.6.6 Printer Driver
- OL Connect Send 1.4.5 Printer Driver
- OL Connect Send 1.3.5 Printer Driver
- OL Connect Send 1.2.5 Printer Driver
msiexec.exe /i OLCS_Printer_Driver_Setup_2.1.1.msi /qn
Some driver settings may need to be updated in order for existing printers to be compatible with
the new driver; see "Printer driver properties and advanced settings" on page30.
The installer will fail when trying to install an older version than the one that is already installed.
Silent uninstall
The following command will silently uninstall the printer driver:
msiexec.exe /x OLCS_Printer_Driver_Setup_2.1.1.msi /qn
This is standard functionality of the msiexec tool, as documented by Microsoft on this webpage:
https://go.microsoft.com/fwlink/?LinkId=94329.
Using API Keys
OL Connect Send allows to use API keys to enhance security. Using API keys is optional, but
strongly recommended.
This is how it works.
l
The print service provider provides an API key to the Printer Driver user (see "Providing an
API key to a user" below).
l
When a job is printed by the OL Connect Send Printer Driver, it will include the API key in
its HTTP headers to authorize itself for printing (see "The API key in the HTTP headers" on
page63).
l
The Workflow process that receives print jobs needs to verify the API key (see "Verifying
an API Key" on page63).
l
If the API key is not accepted, the server should respond with HTTP status 401.
l
If the OLCS client receives a response with status code 401, it will stop trying to submit the
print job, and the print job will go into an error status with an appropriate error message.
Providing an API key to a user
It is up to the print service provider to manage API keys and provide them to subscribers.
The subscriber will either need the API key itself and enter it during installation of the printer
Page 36