Deploying Lexmark Print Management

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:

Where <install-Dir> is the installation folder of LDD.

Supported components

Note: For more information on e-Task printers, see Supported printers.

Component

Description

Compatible eSF framework

Purpose

eSF applications

Badge Authentication (badgeauth v1.22)

Provides authentication using a badge swipe.

e-Task 2

Used for badge or card authentication.

Badge Authentication (badgeauth v2.14.6)

Locks out the printer until a user authenticates with a badge or PIN.

  • e-Task 4

  • e-Task 3

  • e-Task 2+

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 v5.6.5)

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 v1.6)

Provides all usage data on the printer.

e-Task 2

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 v1.10.8)

Provides all usage data on the printer.

  • e-Task 5

  • e-Task 4

  • e-Task 3

  • e-Task 2+

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.

Card reader drivers

keyboardreader v2.4.11

The driver for the RFID card reader.

  • e-Task 5

  • e-Task 4

  • e-Task 3

  • e-Task 2+

  • e-Task 2

Used for RFID card readers.

omnikey5427ckdriver v1.2.11

The driver for the Omnikey card reader.

  • e-Task 5

  • e-Task 4

Used for Omnikey card readers.

omnikeydriver v2.4.4

The driver for the Omnikey card reader.

  • e-Task 3

  • e-Task 2+

  • e-Task 2

Used for Omnikey card readers.

LDD application

advancedprompt v5.2

Provides basic prompts for the user at the printer control panel.

  • e-Task 5

  • e-Task 4

  • e-Task 3

  • e-Task 2+

  • e-Task 2

Used for prompts.


Managing eSF configurations

  1. From Lexmark Management Console, click the Device Groups tab.

  2. From the Device Groups section, click Print Release.

  3. From the Tasks section, click eSF Configuration.

  4. Do any of the following:

    Change the deployment order

    From the eSF Applications: (Solution) section, select an application, and then click the up or down arrow button.

    The following order of deployment is recommended:

    • deviceusage

    • Card reader drivers: keyboardreader, omnikey5427ckdriver, ominikeydriver

    • advancedprompt

    • IdleScreen

    • badgeauth or cardAuth

    • mobileAuth

    Notes:

    • IdleScreen is available only in LPM On-Premises version 2.5 or earlier.
    • mobileAuth is available only in LPM On-Premises version 2.6 or earlier.
    • By default, the compatible eSF level and the recommended deployment order are installed.

    Exclude an eSF application from a policy update

    1. From the eSF Applications: (Solution) section, select an application.

    2. From the Settings section, in the Deploy to list, clear the settings.

    3. Note: When Card Authentication for e-Task5 is excluded from application deployment or policy update, exclude the corresponding security setup files (CardAuth_e5.ucf) as well. For more information on how to exclude UCF file, see Managing UCF settings.

    Configure the eSF application settings.

    1. From the eSF Applications: (Solution) section, select an application.

    2. From the Settings section, configure the eSF application settings.

      Note: To select an e-Task printer, make sure that Deploy to is selected.
  5. Click Save Settings.

    Note: To deploy multiple applications, make sure that you save the settings after configuring each application.
  6. From the Tasks section, click Policy Update > Update Policy.

    Note: The deployment can take from one to two minutes. For more information on how to improve the policy update performance, see Improving device discovery and policy update speed.
  7. Click Done.

Understanding UCF files

You can deploy the following UCF files to the printers using Lexmark Management Console:

Managing UCF settings

Solutions level

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.

  1. From Lexmark Management Console, click the Solutions tab.

  2. From the Solutions section, click PrintReleasev2.

  3. From the Tasks section, click Security Setup Files.

  4. Exclude a UCF file from a policy update. In the Deploy to menu, clear the check boxes.

  5. Click Apply.

Device Groups level

The settings at the Device Groups level serve as local values.

  1. From Lexmark Management Console, click the Device Groups tab.

  2. From the Device Groups section, click Print Release.

  3. From the Tasks section, click Security Setup Files.

  4. Exclude a UCF file from a policy update. In the Deploy to menu, clear the check boxes.

  5. To let the policy update use the UCF settings at the Device Groups level, clear Use Solution Configuration.

  6. Click Apply.

Note: If all devices will be configured with the same Security Setup File configuration, then we recommend managing the Security Setup Files on the Solutions tab.

Configuring UCF settings

  1. From Lexmark Management Console, click the Device Groups tab.

  2. From the Device Groups section, click Print Release.

  3. From the Tasks section, click Security Setup Files.

  4. Select a UCF file, and then configure the settings.

    BadgeAuth.ucf

    Set the values for your environment, such as Active Directory.

    Set the values for the LDAP server settings: mfp.ldap.searchBase, mfp.ldap.serverAddress, and mfp.ldap.userIdAttribute

    The other settings can remain in their default values.

    BadgeAuth2.ucf

    Set the values for your environment, such as Active Directory.

    Set the values for the LDAP server settings: searchBase, serverAddress, and useridAttribute

    If your environment does not allow anonymous binding, then sent anonBind to 0. Set the values for mfpDN and mfpPassword.

    The other settings can remain in their default values.

    CardAuth_e5.ucf

    Set the values for your environment, such as Active Directory.

    If your environment allows anonymous binding, then set the values for address, search_base, and userid_attr.

    If your environment does not allow anonymous binding, then set anon_bind to 0. Set the values for machine_dn and machine_password.

    The other settings can remain in their default values.

  5. Click Apply.