General

 Top  Previous  Next

Print Job Data Directory

This is the physical path on the disk that will hold the folder structure and that holds the spooled print jobs for use prior to their release to the output devices.

Options

These options include support for legacy devices and software along with LPR setup options.

The FollowMe server can be configured to accept incoming print jobs over LPR.  This makes FollowMe incredibly versatile when converging with non Windows systems.  The industry standard LPR commands can be accepted and processed by FollowMe.

In this section we can choose which LPR Command to take user data from and then choose to override any existing user data fro that specific job.

Field

Description

Enable old non-secure clients (prev 3.04.000)

When enabled the FollowMe Q-Server will accept pre-version 3.04.000 uploads where the authentication process was not encrypted

Accept RAW (9100) Print Jobs directly from clients

The FollowMe Q-Server natively support RAW 9100 printing, to enable this feature simply check this option

Accept LPR Print Jobs directly from clients

The FollowMe Q-Server natively support LPR printing, to enable this feature simply check this option

-- LPR Command to get Username from

When LPR is enabled the LPR datastream contains the Username by default in the P parameter however it maybe required to obtain this from another and therefore this option can be selected here

Print Job Username Override (LPR)

When LPR is enabled one can also parse the print job datastream for @PJL USER or @PJL USERNAME variables to extract the username from

Print Job Username Override (SPP)

When SPP is used one can also parse the print job datastream for @PJL USER or @PJL USERNAME variables to extract the username from

Enable Advanced Postscript Processing

The FollowMe Q-Server engine contains an advanced PostScript Processing engine within it (by default this option is enabled). If for any reason it is required for this to be disabled simply uncheck this option

Enable Advanced PCL Processing

The FollowMe Q-Server engine contains an advanced PCL Processing engine within it, the PCL Processing is more than PCL Processing as this engine also holds all other print language processing other than PostScript Processing (by default this option is enabled). If for any reason it is required for this to be disabled simply uncheck this option

FTP Job Receive

For legacy print systems or specialist systems that are only able to print via FTP then simply enable this option (Note: this option uses port 21, therefore if a FTP server already exists or if this port is in-use then either this option or the offending application needs to be disabled)

Enable Incoming Fax to Shared User

When the FollowMe Embedded for HP is used in conjunction with its Inbound Analogue Fax Re-direction feature the Enable Incoming Fax to Shred User option needs to be enabled

-- Shared User

When the Enable Incoming Fax to Shred User is enabled a Shared User must be selected. If a custom rule is used to re-direct print jobs it is still required that a Shared User is selected even if that Shared User will not have a Fax stored against it

Deduct from Credit Pools before user's default credits (rather than both simultaneously)

This option allows extended credits to be deducted before users standard credits

Encryption

A key part of FollowMe is security.  The level of security can be chosen here from a drop down of 5 options, these apply to the transmission of data to and from the FollowMe server.

For tighter security we can also choose to store print jobs as encrypted files.

We can also disable old (low security) uploads, this may be necessary in an upgrade environment for software from pre-2004).

LDAP Import Settings

Field

Description

Bind Timeout (secs)

Binding is the step where the LDAP server authenticates the client and, if the client is successfully authenticated, allows the client access to the LDAP server based on that client's privileges.

The timeout for the Bind is configured here.

Query Timeout (secs)

The maximum time in seconds that a LDAP server will spend on a single search. When this limit is reached, the LDAP server will return a timeout error.

The timeout for the Query is configured here.

Page Count

This Page Count controls the maximum number of LDAP objects that are returned in a single search result, independent of how large each returned object is. To perform a search where the result might exceed this number of objects.

The Page Count is configured here.