Page 1
Printer Driver User Guide Version: 2.1.2 Connect Version: 2022.2 Last Revision: 2022-11-30 Upland Software - Objectif Lune 2030 Pie-IX, Suite 500 Montréal, QC, Canada, H1V 2C8 +1 (514) 875-5863 sales@ca.objectiflune.com www.objectiflune.com All trademarks displayed are the property of their respective owners. © Upland Software - Objectif Lune. 1994-2022. All rights reserved.
Table of Contents Table of Contents 3 What is Connect Send? 7 Features List Main steps in OL Connect Send Installation Printer driver Workflow Plugins Connect Send database cleanup service Moving Workflow to another machine Prerequisites System Requirements Plugin Printer Driver HTTP Browser Installing OL Connect Send Printer Driver Before you start Setup process – new installation Adding, modifying or deleting a printer Shared Printers Managing multiple OLCS printers Printer driver properties and advan
Changing the UDP communication Port 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 39 39 39 39 40 40 40 41 41 42 Basic mode User mode Click Charge mode Incoming print jobs and the license Scenario 1 Scenario 2 OL C
Troubleshooting 72 OL Connect Send 2.1.2 Printer Driver Release Notes 74 Overview Important Notes OL Connect Send 2.1.2 Printer Driver Operating system support Installer Improvements OL Connect Send 2.1.1 Printer Driver OL Connect Send 1.8.0 Printer Driver Citrix and Microsoft Terminal Services (Remote Desktop Services) support General improvements OL Connect Send 1.7.0 Printer Driver Improved licensing Improved Printer Driver installation General improvements OL Connect Send 1.6.
What is Connect Send? Connect Send is an application with two components. The first is a Windows printer driver (2.1) and the second includes a set of Workflow plugins (2022.2). These two components work together – they cannot be used on their own. Connect Send allows for PostScript files to be received over the internet from any Windows Desktop application. It can be used in unlicensed mode and licensed mode. The Unlicensed mode (default) allows users to push documents to Connect Send.
l l l General l Compresses PostScript files during transmission to minimize bandwidth. l Allows the printer driver to include an API key in its HTTP headers to authorize itself for printing. Unlicensed mode l Non-interactive job submission. l Free to use. l Confirms job transmission with a message in the Notification Area. Licensed mode l Interactive job submission possible. l Launches the user’s default browser to display web content produced by a Connect server.
. The plugin returns a status message to the client, indicating a successful or failed job transfer. 10. The plugin sends the license status to the Printer Driver. 11. The Printer Driver (if licensed and interactive) will launch a browser window and send an HTTP request to Workflow. The result of the receiving interactive process (see "Get Job Data plugin" on page 53) will be displayed in the browser.
Installation Printer driver The OL Connect Send Printer Driver must be installed on a dedicated machine and a Windows printer must be set up using this driver. Additionally several settings regarding the host for sending print jobs have to be set. All this is done with the Printer Driver installer; see "Installing OL Connect Send Printer Driver" on page 13. Any OL Connect Send Printer Driver with a version number less than 1.0.5 should be uninstalled before installing the newest Printer Driver. 1.
Connect Send database cleanup service A cleanup mechanism in the OLCSService service and in the Job Processor plugin prevent excessive growth of the Connect Send database. There are no settings to make for these mechanisms, except that you could change the default number of days to keep history of transactions. This influences the output of the Get Data plugin (see "Get Data plugin" on page 58). By default, the minimal number of days to keep history of transactions is 60. To change this: 1. Create a olcs.
l l OL Connect Send: l OL Connect Send Printer Driver l OL Connect Remote Print plugins. These are built into Workflow as of version 8.6.1. An OL Connect Send license (required for interaction to take place) System Requirements Plugin The Job Processor plugin is designed to work with the Workflow module (Workflow) of PlanetPress Connect and PReS Connect (Connect) which means it will run on any operating system by those products.
Citrix and Microsoft Terminal Services (Remote Desktop Services) support As of OLCS Printer Driver version 1.8, both Citrix and Microsoft Terminal Services (Remote Desktop Services) environments are supported. HTTP Communications between the Printer Driver and the plugin is achieved using HTTP. It is therefore necessary to ensure that HTTP interaction between all Printer Driver and server machines is enabled.
Setup process – new installation The following section describes the installation process for the OL Connect Send Printer Driver. Starting the installation Click the OLCS_Printer_Driver_Setup_2.1.1.msi file to start the OL Connect Send Printer Driver Setup. If an OLCSClient.ini file is found in the folder from which the installer runs, the fields in the installer will be pre-populated using the settings contained in that file. For information on how to prepare the OLCSClient.
Please read the legal notices and acknowledgments. Click Next to proceed. EULA The next screen shows the EULA. Please read and accept it to proceed further by clicking Next. Installation Type The OL Connect Send Printer Driver setup can be tailored for individual installations. On this page, select whether to install using download customized settings (via a URL that will need to be specified), or whether to use local or default settings.
If your print service provider has provided an option to download customized settings for the Printer Driver, then select the Download settings from a server, using a URL option. Otherwise select the Configure manually, or use a local settings file option. Click Next to proceed. Download Settings This Wizard page only appears if the choice on the previous Installation Type page was to download the installer settings from a URL. Enter the URL from which to download the customized settings.
If no Authentication is required, leave the Authentication required check box unchecked and ignore the Username and Password entries. Once all the required details have been entered, click the Download button to download the customized settings. If there are errors in the download, these will be reported in the lower portion of this page. Only when the download has completed successfully will the Next button become active. Click the Next button to proceed.
Otherwise select the My provider does not require an API key option. Click Next to proceed. Communication URL settings This Wizard page might not appear, if the installation is being run in conjunction with a provided (or downloaded) OLCSClient.ini settings file. The URL for the print job submission is required for the HTTP connection with the receiving OL Connect Workflow server (e.g. http://192.168.159.100:9090/olcs_transfer). This would be the Workflow process which accepts the relevant data.
If a license is valid for the local system and the interactive mode is activated, the action name has to be given for this (default: “olcs_interaction”). This would be the Workflow process that starts/executes the interaction. URL for print job submission The URL for print job submission allows the URL for Workflow to be entered. This is the server that will capture and process print jobs. It needs to be entered as a full URL, for example: http://demo.objectiflune.
automatically run in protected mode (SSL). For additional information about secure file transfer, HTTPS certificates and how to request a countersigned certificate, please see this page: SSL HowTo. l : The host name or IP address of the target machine. This is either the computer where the related Connect Workflow is running or a gateway machine. l : The port entry is mandatory, even if the port should be one of the standard ones (80 for HTTP or 443 for HTTPS).
This URL may be entirely different from the URL for job submission. If the protocol, host and port of the URL are the same as in the URL for print job submission, it suffices to give the action and any path components. For example: The URL for job submission is given as http://demo.myhost.com:80/path/to/target/olcs_ transfer. If the protocol, host and port of the URL for interaction are the same, the URL for interaction can be entered as: path/to/target/olcs_interaction. When done, click Next to continue.
Printer name By default the printer name is OL Connect Send Printer. If a printer with the same name already exists, a number is added and increased until no matching printer name is detected. This then becomes the proposed printer name in this dialog. The printer name must consist of valid characters. Invalid, forbidden characters are: l / = forward slash, 0x2F l " = quote, 0x22 l \ = backslash, 0x5C l * = asterisk, 0x2A l : = colon, 0x3A l ? = question mark, 0x3F l < = less than sign, 0x3C l
As opposed to the other settings, the printer name cannot be changed after installation. Logging The OL Connect Send Printer Driver creates one log file per printer per day. (For information about all log files, see "Log files" on page 69.) The number of log messages can be set by choosing the log level. Available log levels are: l DEBUG: Logs all messages and is intended to be used only for bug research.
To finalize the installation, click the Install button. A progress bar will then be shown, displaying the progress of the installation process. After a successful installation, the Finish dialog is shown. Note Reboot requirement Depending on what applications and Visual C++ runtimes already installed, a reboot may be required after the successful installation of the OL Connect Send Printer Driver.
The OLCS Notifier Once a OL Connect Send Printer Driver is installed, an application called OLCS Notifier is also installed. It displays and logs information relating to the preparation and transfer of each print job. For more information see "OLCS Notifier" on page 37. Adding, modifying or deleting a printer To install an additional printer, modify a printer or delete a printer, run the installer again.
Clicking the Next button will bring you to the selection page where you can decide to: l Add a printer. l Modify the settings of an existing printer. l Delete one or all existing printers.
Adding a printer The wizard pages that follow when clicking the Add printer button are the same as for a new installation. Each printer can have its own settings. Modifying the printer settings Depending on the number of printers already installed, you will either see the Wizard window or a dialog box from which you must select the printer you wish to modify.
The wizard pages are the same again, so you can modify any of the values (e.g. if the host name has changed), except for the printer name which is grayed out and locked. Removing a printer Depending on the number of OLCS printers installed, you will either get a selection box to identify which printer to remove, or you can just delete the only one.
Shared Printers The OL Connect Send Printer Driver is not a shareable driver. This is because the browser interaction cannot be routed through the print server to the end user's desktop. Also a shared printer would transfer the print server's machine name, user name, domain etc., thus invalidating the intended behavior. So, OL Connect Send Printer Driver must be installed on each dedicated machine.
Printer driver properties and advanced settings It is not normally necessary to change the OL Connect Send printer driver's properties or advanced settings. Most of these settings (e.g. Output Destination, Stapling, Jogging) will not have an effect, unless the print service supports them. Ask your print service provider which features can be used when printing a document. Nevertheless, a few settings are important to the proper functioning of OL Connect Send.
Mass deployment of the OL Connect Send Printer Driver The OL Connect Send Printer Driver is intended to be installed on computers from which print jobs shall be sent to the respective Workflow server. Often such computers are part of specific domains on which end users are not allowed to install software on their own. Such users may not have the knowledge to install printers, and often dedicated restrictions and policies have to be taken into account.
The command to run the tool manually is: msiexec.exe /i OLCS_Printer_Driver_Setup_2.1.1.msi /qn The user account used to run the Silent Setup tool needs to have administrator rights for the installation of a printer, a printer port, a printer driver etc. Otherwise the installation will fail silently, but the respective log entries will be created (see "Installation errors" on page 35). Configuration file content The silent installation mode will only work with a valid configuration file.
Section Description Default The port for communications with Workflow can be changed in the Workflow preferences under Plugin > HTTP Server Input 1 > Protocol options > Port. Default value changed in OLCS version 1.7.0 PrinterName Name for the printer to create and configure. If a printer with that name already exists, the installer will add an additional numbered printer of that name.
Section JobInteraction Description Name of the HTTP action in Workflow for the browser interaction process. Default olcs_ interaction Defines if the Windows Taskbar notifier (OLCS Notifier) is started during the setup process (1) or not (0). When set to 0, the OLCS Notifier will not be started until the user logs in. Note StartTBN Set StartTBN to 0 for mass deployment of the Printer Driver. Starting the OLCS Notifier during setup in a silent installation will lead to issues when the user logs in.
Section Description l Default A Summary page with a Test connection button will be displayed. If the preset file contains the flag LockSettings=1, but doesn't contain all the settings required for the Communication page, any absent settings will be set to their defaults. LockSettings option added in OLCS version 1.7.
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 page 30. 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.
driver, or a presets file that includes the API key, which the Setup tool will use if the two are located in the same folder, or if it is downloaded as part of the Installation (see "Installing OL Connect Send Printer Driver" on page 13). The same presets file is used by the Silent Setup tool (see "Mass deployment of the OL Connect Send Printer Driver" on page 31).
Logged messages To view the messages logged by the OLCS Notifier, right-click the OLCS Notifier icon in the notification area and select Show. This brings up the OL Connect Send Messages window with all the notifications arrived at the OLCS Notifier since installation or since the list was last cleared (using the Clear List button).
%programfiles(x86)%\Objectif Lune\CPD\App Changing the UDP communication Port Each OL Connect Send Printer Driver sends its messages to the OLCS Notifier via UDP. By default port 8090 is used, but it can be modified by setting a different port number in the registry under: l HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Objectif Lune\ConnectSend\TaskbarNotify on 64bit Windows l HKEY_LOCAL_MACHINE\SOFTWARE\Objectif Lune\ConnectSend\TaskbarNotify on 32bit Windows The key must be named UDPPort and must be of ty
l Start: Command Prompt (Admin) l Copy/paste the path to the OLCS Printer Driver Setup MSI file into the Command Prompt l Press Enter The installer should then run without further administrative rights issues.
One known issue is that if the PDF contains a PostScript font (Type 1 in Adobe Acrobat Reader), an "error retrieving character data” may occur in Workflow's Execute Data Mapping task during the data mapping of the received file. In that case the data will be corrupted and no preview will be shown in the web template. Paper Size vs Printer Page Size It is important to ensure that paper size settings match the printer driver settings.
License modes OLCS can operate in three different modes but they cannot be mixed on a single Connect system. The three modes are: Basic, User and Click Charge. The Basic, unlicensed mode: l allows non-interactive job submission. l is free to use. l confirms job transmission with a message in the Notification Area (also called the "system tray"). The User and Click Charge modes are licensed modes in which: l interactive job submission is possible.
User mode User mode requires either a license limiting jobs submissions to specific domains (or subdomains) or a license that allows job submission from any domain, but from a limited amount of users (Enterprise). The restricted (sub)domain licenses can be restricted to a specific number of users (10, 25, 50, 100, 200 or similar) or they can be unlimited. The non restricted (sub)domain licenses are limited to 1000 users (Enterprise).
Click Charge mode Where the domain and the number of users is unknown at the point of sales – for example a public service driven by users creating their own accounts via the web for onboarding documents -, the Click Charge license can be used. It allows any number of domains and users to submit jobs into the Connect system, providing credits are available. 1. This mode enables the Printer Driver to request a web page (which could include a preview of the document) from Connect.
Scenario 1 OLCS is licensed in Click Charge mode with 10,000 pages. They have already used 9,870 credits, so 130 are left. l Case 1: A job comes in with 40 pages. This job can be handled in LICENSED mode, so this is a "licensed job". l Case 2: A job comes in with 243 pages. This is more than 130. This job is handled in UNLICENSED mode (reduced metadata and no database entries). This is an "unlicensed job". Scenario 2 Perpetual license with domain = "some.phantasy.com" and number of licensed users = 100.
OL Connect Send in Workflow Just as the Printer Driver is an indispensable part of OL Connect Send, OL Connect Send cannot function without its Workflow plugins, embedded in special Workflow processes. These processes take care of the communication with the Printer Driver and they handle the interaction with the user who sends a print job using the Printer Driver. The following topics explain how to configure these processes.
printer driver, you don't have to do that again.) Add a Connect Send printer with the given settings and print the provided Word file to that printer. The printer will trigger an interactive process on demo.objectiflune.com. l Download the sample files from OL's Resource Center: http://help.objectiflune.com/en/#csend. Job transfer process The Workflow process that handles the job transfer is small and straightforward. It starts with an HTTP Input task.
l Creating interactive processes for incoming print jobs using OL Connect Send requires that the relevant information about the respective job is available and can be used in Workflow. This is what the OL Connect Send Get Job Data plugin is made for. For more information, see "Get Job Data plugin" on page 53. l Each web page served by an interaction process is generated by the Create Web Content plugin. It creates HTML output from a specified web template.
Plugins Job Processor plugin The Job Processor plugin is an output plugin that appears in the Plug-in Bar of Workflow under OL Connect Send. The Job Processor plugin must be added to a Workflow job transfer process that starts with an HTTP Server Input. The Job Processor plugin can be the only other task in that process (except when API keys are used; see "Verifying an API Key" on page 63).
Configuring the plugin To configure the Job Processor plugin, right-click it after adding it to the Workflow process, and click Properties. The color of the property names in the Job Processor Properties dialog indicates that these fields can contain variables. Workflow variables To facilitate using job related information for the creation of the target folder and file name/s, the Job Processor plugin maps job relevant information to the standard Workflow variables (%1 to %8).
Information Workflow Variable When licensed When unlicensed No. of Pages 1 %5 Number of pages of the job Number of pages of the job No. of Copies 1 %6 Number of copies set by the user Number of copies set by the user Domain Name 1 %7 The Domain Name "na" Machine Name 1 %8 The Machine Name "na" 1) These values originate from the Printer Driver machine. The variables can and should be used to create dynamic file and folder names for each print job.
HTTPS Communication The Printer Driver can be set to use HTTPS for any job transfer. To do this Workflow must also be set to use HTTPS. This topic is covered briefly in the “Server URL Setting” section in this document (new Printer Driver installation), but full details can be found in the Workflow documentation. Job Origin OL Connect Send allows to use API keys to enhance security (see "Using API Keys" on page 36). Each print job will include unique information about the machine it has been sent from.
Timeout During a job transfer from the Printer Driver to Workflow, a timeout could occur (indicated by a log entry like “ERROR: sendBinaryContents: Could not open request. Reason: 12002”). In this case, the timeout for the HTTP service in Workflow needs to be increased. It is recommended to use a value of more than 10 minutes (>600 seconds). Additionally, the timeout in the browser on the client side should be enhanced. Please see the help pages for your browser about how to do this.
Typically, it is used in the interaction process just after the initial HTTP Server Input plugin. The Get Job Data plugin gets all relevant information for the dedicated print job using the Unique Job ID. Whenever an OLCS Printer Driver is sending a print job to the Job Processor plugin, it creates a unique ID string composed of 10 upper- and lowercase letters and digits e.g. “ri0zZdluLp”.
General Tab Three different settings affect the general behavior of the plugin: l Where to get the Print Job ID. l When to continue with the next step. l Where to store the job information details. Select Job ID Source The plugin can be used in a generic way. Whenever information about a specific print job is required, it can be retrieved as long as the related job ID is known. However, the plugin has been implemented in a way that it can also be used very easily in the OLCS interaction process.
Select Returning Type Depending on this setting the plugin gets status information about the job before it has arrived or it gets information after the job has been completely received. l Immediately. By choosing this option, the Get Job Data plugin will return as quickly as it can, providing it can find a matching Job ID in the database. It is important to know that it will wait until any information about the job is available.
l Date/Time stamp: This is the time when the matching job was initially created in the database. It is stored in UTC format plus time zone indicator inside the database. It will differ from the time stamp logged by the Printer Driver as well as by the OLCS Job Processor plugin. The Printer Driver machine time stamp in the Printer Driver log may significantly differ from this value.
l Machine GUID: The unique machine ID (see "Job Origin" on page 52) of the machine on which the job was produced. It can be used as an additional identification mark to validate the origin of the job. On Error Tab Please refer to the Using the On Error tab in the Workflow documentation. Miscellaneous Tab Please refer to the Miscellaneous tab in the Workflow documentation. Get Data plugin The Get Data plugin allows OL Connect Send (OLCS) users (admins, accounting personnel, print masters ...
A cleanup mechanism in the OLCSService service and in the Job Processor plugin prevent excessive growth of the Connect Send database. There are no settings to make for these mechanisms, except that you could change the default number of days to keep history of transactions. This influences the output of the Get Data plugin. By default, the Connect Send database keeps history of transactions for 60 days. This is adjustable; see "Connect Send database cleanup service" on page 11.
Example 1 A valid user name search string, entered in the Filter Users field, would be: %\{global.User};helen;%1;george napier This would look for all entries, where the user name is: l as currently stored in the global Workflow variable User l "helen" l as stored in the job variable number 1 l equals "george napier" (case insensitive). The search criteria are in this case combined with OR. Example 2 The domain name entered in the Filter Domains field is objmtl.objectiflune.
It is possible to define the same date for From Date/Time as for To Date/Time. However, entering the same info (without time information) would lead to getting no entries.
l Job UID: This is the 10 (ten) character long Unique Job Identifier string. l Status ID: The status ID shows in which stage the job currently is: 0 = undefined; 1 = idle; 2 = transfer; 3 = chunk; 4 = concatenate; 5 = unzip; 6 = done. A value of 6 indicates a fully processed job. Any value between 2 and 5 (inclusive) means that the job is still in progress. For a small job, some statuses may be skipped. l Date/Time stamp: This is the time when the matching job was initially created in the database.
l Domain / Workgroup Indicator: This domain name is the real domain name or only a workgroup name. For explanations about domains, domain names, users, user names, user domains, logged on users vs. application running users, machine names etc. please refer to the respective Windows help pages or ask your system administrator. l Machine name: The name of the machine the Printer Driver is running on as retrieved by the respective Windows API.
In order to tell the printer driver if an API key is missing or incorrect, the Input task of the process must be set to return a custom HTTP server response code, which is stored in a variable (in this example: %{http_response}). Retrieving the API key from the HTTP headers can be done with a Run Script task. For example: // Get Bearer Key from raw header var rawHeaders = Watch.
Another Text Condition task checks if the API key is actually valid (here: comparing the value found in the %{bearer_key} variable to a string value). If it is valid, the job may be processed by the Job Processor task. If the API key wasn't valid, use the Set Job Infos and Variables task to assign the value of the respective response code, 401, to the variable that was selected in the Input task. If the API key is missing, the code should be 400 (bad request).
Using the Printer Driver The OL Connect Printer Driver can be used like any physical printer. Just go through the usual steps: 1. Click the Print button (or use the menu from the software used). The Print dialog appears. 2. In the Print dialog, select a printer that works with the OL Connect Send printer driver and click OK.
The OL Connect Send Printer (2.1) generates a local PostScript file. This data is zipped and sent in one or multiple chunks to the Workflow server (2022.2). Depending how the environment has been setup, information is sent using the HTTP or HTTPS protocol.
the customer’s machine is launched showing the interactive web page defined in the installation process. It is recommended not to use Adobe Acrobat Reader to print PDF files with OL Connect Send. Print the source file (e.g. the Word file) whenever available. If PDF files are to be printed with OL Connect Send, use a different PDF viewer instead. Adobe Acrobat Reader produces its own PostScript file, rather than passing the PDF to the OLCS Printer Driver to generate the PostScript file.
Log files Workflow log files The OL Connect Send Workflow plugins write to the Workflow log file. Its location can be found in the Workflow Help (see help.objectiflune.com). Printer log files Each OL Connect Send printer logs its messages in a daily log file. The log files are located under %ProgramData%\Objectif Lune\CPD\Log\ on the machine/s on which the Printer Driver has been installed.
No;Status;Mode;User;Target}} The separator character is the semicolon (0x3B). Each following line is one log entry. The file can be loaded with e.g. Excel and filtered, ordered, sorted and modified as desired. When the history log file is open in another application (such as Excel), it is locked for write access, which means that OL Connect Send printers cannot add entries to it. The printer's normal log entries will be written but the related history log entries will be lost.
l Document name as can be retrieved from the spooler information. Please be aware that some applications modify, mix up, enhance or truncate this information. l Number of pages l Number of chunks l Chunk number = number of the currently transferred chunk l Job transfer status.
Troubleshooting There are some known issues that can be encountered when using Connect Send, depending on the way OL Connect Send is installed, configured or used; see "Known Issues" on page 39. If another issue occurs and you find that you cannot solve the issue, there are a few things to check. 1. Switch the OL Connect Send Printer Driver logging to DEBUG. This can be done by modifying the OL Connect Send Printer Driver; see "Installing OL Connect Send Printer Driver" on page 13.
c. Remove the existing OLConnect1.OLConnectLicense from %ProgramData%\Objectif Lune\OL Connect\licenses. d. Put the new license at that location. e. Restart any Connect services you stopped. You may notice that removing the existing license may be forbidden and you need to allow it explicitly. It may even be that you need to log on as an administrator to delete the file. This is not an issue with OLCS, but with the Connect and/or Workflow version and under which user it has been installed.
OL Connect Send 2.1.2 Printer Driver Release Notes Overview This document provides an overview of the new features and enhancements in the OL Connect Send Printer Driver. Important Notes l Passthrough printing through the OL Connect Send Printer Driver is not supported. This includes printing from Connect (Designer) or any other software that relies on passthrough printing. It might partially work, but it cannot be relied upon.
OL Connect Send 2.1.2 Printer Driver Operating system support As of version 2.1.2, OL Connect Send Printer Driver is officially supported under Windows 11 and Windows Server 2022. Installer Improvements Updated the third party library used to compile our installers to fix a security vulnerability. (OLCS1014) OL Connect Send 2.1.1 Printer Driver l Licensing improvements. (OLCS-607/610) l Fixed issues with OLCS Printer Driver installation Connection Test failing for HTTPS addresses.
OL Connect Send 1.8.0 Printer Driver Citrix and Microsoft Terminal Services (Remote Desktop Services) support OLCS now runs under both Citrix and Microsoft’s Remote Desktop Services environments. (SHARED-71164/71167) Some of the changes made to allow this include: l The license check for user based licenses has been changed to distinguish between different users on the same machine/system. These are now separately counted.
OL Connect Send 1.7.0 Printer Driver Improved licensing OLCS User Mode License changes For previous releases the only way to allow access to any domain, was to use a credit-based license. As of 1.7.0, user-based licenses will allow jobs to be received from either specific domains/subdomains, or from all domains. Improvements include: l A license can now include domains and sub-domains, so users will be able to print regardless of domain structure.
General improvements l Changed OLCS compression method, resulting in increased performance when submitting some large files. (SHARED-75205) l Printer Driver port monitoring improved. (SHARED-79280) OL Connect Send 1.6.6 Printer Driver Installer Improvements l Interactive installation with presets is now supported. The installer will read a presets file of the same format as would be supplied for a silent installation. The presets file must be located in the same folder as the msi.
OL Connect Send 1.4.5 Printer Driver Operating system support As of version 1.4.5, OL Connect Send Printer Driver is officially supported under Windows Server 2016. OL Connect Send 1.3.5 Printer Driver Installer Improvements l Improved feedback from the Installer. (SHARED-54046) l The URL for print job submission entered as part of the installation process are now stored case sensitive. (SHARED-55193) These entries must match the requirements of the target host’s case-sensitiveness.
Improved connections to Connect Workflow An issue was encountered with HTTPS communication between the OL Connect Send Printer Driver and Connect Workflow. When the OL Connect Send Printer Driver was working with Secure HTTP (HTTPS), then the Secure Socket Layer (SSL) would check the "Certificate Revocation List" (CRL) via a Revocation Server.
