The eSF applications, card reader drivers, and UCF files required to use LPM are provided with the solution. Lexmark Management Console lets you configure and deploy the applications to the printers.
The required files can be found in the following folders:
Advancedprompt—<install-Dir>\Lexmark\Solutions\apps\wf-ldss\firmware
eSF applications and drivers—<install-Dir>\Lexmark\Solutions\apps\wf-ldss\solutions\PrintReleasev2-release version\firmware
UCF files—<install-Dir>\Lexmark\Solutions\Apache2\htdocs\apachewebdav\ucf\PrintReleasev2
Where <install-Dir> is the installation folder of LDD.
Component | Description | Compatible eSF framework | Purpose | |
---|---|---|---|---|
LDD application | advancedprompt | Provides basic prompts for the user at the printer control panel |
| Used for prompts |
Card reader drivers | keyboardreader | The driver for the RFID card reader |
| Used for RFID card readers |
omnikey5427ckdriver | The driver for the Omnikey card reader |
| Used for Omnikey card readers | |
omnikeydriver | The driver for the Omnikey card reader |
| Used for Omnikey card readers | |
For more information on the eSF application versions, see Release Notes. | ||||
eSF applications | Badge Authentication (badgeauth ) | Provides authentication using a badge swipe. |
| Used for badge or card authentication. |
Badge Authentication (badgeauth ) | Locks out the printer until a user authenticates with a badge or PIN |
| Used for badge or card authentication Note: After upgrading to LPM 2.5.2 or later, manually configure each Badge Authentication application to deploy to the target printer family. | |
Card Authentication (cardAuth ) | Locks out the printer until a user authenticates with a badge or PIN | e-Task 5 | Used for badge or card authentication | |
Device Usage (deviceusage ) | Provides all usage data on the printer |
| Used when Device Usage tracking is enabled Note: After upgrading to LPM 2.5.2 or later, manually configure each Device Usage application to deploy to the target printer family. | |
Device Usage (deviceusage ) | Provides all usage data on the printer |
| Used when Device Usage tracking is enabled Note: After upgrading to LPM 2.5.2 or later, manually configure each Device Usage application to deploy to the target printer family. | |
Guestlaunch | Provides authentication for the Guest Print feature |
| Used for PIN authentication when for Guest Print | |
PrintCryption (printcryption2 ) | Enables secure printing of encrypted jobs sent from the user's workstation |
| Used to decrypt the encrypted print jobs |
From Lexmark Management Console, click the Device Groups tab.
From the Device Groups section, click Print Release.
From the Tasks section, click eSF Configuration.
Do any of the following:
From the eSF Applications: (Solution) section, select an application, and then click the up or down arrow button.
We recommend the following order of deployment:
deviceusage
Card reader drivers: keyboardreader, omnikey5427ckdriver, ominikeydriver
advancedprompt
IdleScreen
badgeauth or cardAuth
mobileAuth
Notes:
From the eSF Applications: (Solution) section, select an application.
From the Settings section, in the Deploy to list, clear the settings.
From the eSF Applications: (Solution) section, select an application.
From the Settings section, configure the eSF application settings.
Click Save Settings.
From the Tasks section, click Policy Update > Update Policy.
Click Done.
You can deploy the following UCF files to the printers using Lexmark Management Console:
BadgeAuth—Creates an LDAP security building block that is compatible with e-Task 2 devices.
BadgeAuth2—Similar to BadgeAuth except that it is compatible with e-Task 2+, e-Task 3, and e-Task 4 devices.
CardAuth_e5—Secures access to e-Task 5 devices using a card reader. For LPM version 2.6, CardAuth_e5.ucf must be updated after installation.
The following settings must be removed from the configuration file:
<name>esf.IdleScreen.ChgBkgnd</name> <name>esf.IdleScreen.Idle</name> <name>esf.IdleScreen.showroomFAC</name>
The following setting must be added:
<name>use profiles</name>
MobileAuth_e5—Secures access to e-Task 5 devices using a mobile device.
The settings at the Solutions level serve as global values. During deployment, the system uses the global values unless local values defined at the Device Groups level are specified.
From Lexmark Management Console, click the Solutions tab.
From the Solutions section, click PrintReleasev2.
From the Tasks section, click Security Setup Files.
Exclude a UCF file from a policy update. In the Deploy to menu, clear the check boxes.
Click Apply.
The settings at the Device Groups level serve as local values.
From Lexmark Management Console, click the Device Groups tab.
From the Device Groups section, click Print Release.
From the Tasks section, click Security Setup Files.
Exclude a UCF file from a policy update. In the Deploy to menu, clear the check boxes.
To let the policy update use the UCF settings at the Device Groups level, clear Use Solution Configuration.
Click Apply.
From Lexmark Management Console, click the Device Groups tab.
From the Device Groups section, click Print Release.
From the Tasks section, click Security Setup Files.
Select a UCF file, and then configure the settings.
Set the values for your environment, such as Active Directory.
Set the values for the LDAP server settings:
, , andThe other settings can remain in their default values.
Set the values for your environment, such as Active Directory.
Set the values for the LDAP server settings:
, , andIf your environment does not allow anonymous binding, then sent
to . Set the values for and .The other settings can remain in their default values.
Set the values for your environment, such as Active Directory.
If your environment allows anonymous binding, then set the values for
, , and .If your environment does not allow anonymous binding, then set
to 0. Set the values for and .The other settings can remain in their default values.
Click Apply.