Overview

This feature allows SafeQ Client to deliver print jobs to different SafeQ servers, choosing the destination server automatically.
Whole behavior is based on rules described in server_subnet.csv file.
SafeQ Client then delivers print jobs to a SafeQ server based on the IP subnet of the user or the Client.
Behavior modes are described in installation step 3 below and also in SafeQ.ini file in the SafeQ Client installation package.

Limitations

Each user can only be connected to the terminal server once at a time. When there are more sessions of a print job owner, the user's print jobs will be sent to the default IP address.
Only IPv4 protocol is supported.
In ServerDeliveryMode=2, when the computer has multiple IP addresses, the first one will be used (there is no way to choose the network interface).
It is not possible to combine load balancing and fail over at the same time (for example to achieve loadbalancing within one datacenter and failover to another datacenter), but load balancing can be set to all addresses mentioned in the CSV file by option LoadBalancing.

Installation

1. Create and configure server_subnet.csv file

Create CSV file (in any text editor) named server_subnet.csv and put it in the SafeQ Client installation package (where SafeQ.ini is located)
There should be a line for each IP subnet from which clients will be printing, and for each SafeQ CML/ORS server that will be used for print job delivery
Default IP address is used in case connection comes from subnet undescribed in server_subnet.csv
Description must be in form subnet / mask ; server_IP_address
The subnet size can be described in two ways: using a subnet mask (e.g. 10.0.11.80/255.255.255.0) or in CIDR notation (e.g. 10.0.11.80/24)
Target allows multiple IP addresses or FQDN names (these values must be delimited by comma)
If there are multiple matching subnets, the first one is applied
For example:

server_subnet.csv example

0.5.0/24;10.0.11.80,10.0.11.81
0.6.0/24;10.0.11.82
0.7.0/255.255.255.0;10.0.11.83

In this case, if user is connected from 10.0.5.* subnet and performs a job, the job will be delivered to 10.0.11.80 (or to 10.0.11.81 if the first one fails).

2. Configure all known properties in SafeQ.ini as usual

Don't forget to configure default ServerIP property
We recommend to set property AuthType = 1 or AuthType = 3 so Identification is set to Job owner or Text when using shared printer

3. Configure server autodiscovery mode

In SafeQ.ini configure the property ServerDeliveryMode
These modes can also be changed later in SafeQ Client Options in Mode selection (see image below)

Value in ServerDeliveryMode	Mode name in SafeQ Client Options	Description
0	Static addresses	Jobs are delivered to statically defined IP address (or addresses). This is the default (and backwards-compatible) option.
1	Remote connection subnet	SafeQ Client on a terminal server uses the IP address of the workstation from which the user is connected via a remote desktop connection to the server and then the job is delivered to a SafeQ server selected according to the server_subnet.csv file (on the server)
2	Local server subnet	SafeQ Client uses the IP address of the workstation/server where the Client is running and delivers print jobs to a SafeQ server selected according to the server_subnet.csv file
3	Print job subnet	SafeQ Client uses the IP address of the workstation where the print job has been created and delivers print jobs to a SafeQ server selected according to the server_subnet.csv file (used when the print queue is shared)
5	Environment variable subnet	SafeQ Client uses IP address taken from user's environment variable and delivers print jobs to a SafeQ server selected according to the server_subnet.csv file. The variable "EnvironmentVariableIP" contains the name of environment variable cointaining IP address. The variable is searched in the Registry under key "HKEY_CURRENT_USER\Volatile Environment".

4. Run install.exe

Check that there is server_subnet.csv present also in Y Soft Client instalation folder

5. The printer port(s) will be created

SafeQ Client configuration dialog with selected "Remote connection subnet" mode