Skip to Content Information Center
Lexmark XM5163

Lexmark XM5163

Not your product?

Adding a missing password to an exported UCF for scan to network

Issue description

This article provides the procedure for adding a missing password parameter ("") value to an exported Scan-to-Network universal configuration file. This will require a PC equipped with Notepad and a base64 encoder.

*UCF - Universal Configuration File

Additional identifiers that this article is for you...

  • You utilize static passwords for an individual or set of users...
  • You need to transfer this password to a new device or fleet of devices utilizing the Import and Export Embedded Solutions Settings File feature.

Step 1: Export Settings

  1. Open the MFP's embedded Web server (EWS).

  2. Click on Settings.

  3. Click on Import/Export.

  4. Click on Export Embedded Solutions Settings File, i.e., scanToNet.ucf

  5. Open file with Notepad.

  6. Locate the pwd key esf.cifs.inst.1.cifs.pwd ""

  • esf.cifs.inst.1.appId "scanToNet"
  • esf.cifs.inst.1.instanceId "1"
  • esf.cifs.inst.1.cifs.address "\\157.184.20.42\temp"
  • esf.cifs.inst.1.cifs.ldapPathAttribute ""
  • esf.cifs.inst.1.cifs.ldapUseridAttribute ""
  • esf.cifs.inst.1.cifs.ldapPathSuffix ""
  • esf.cifs.inst.1.cifs.domain "BRLENDA"
  • esf.cifs.inst.1.cifs.winsServer ""
  • esf.cifs.inst.1.cifs.brdAddr ""
  • esf.cifs.inst.1.cifs.isKerberos "false"
  • esf.cifs.inst.1.cifs.authOptions "3"
  • esf.cifs.inst.1.cifs.uName "user"
  • esf.cifs.inst.1.cifs.pwd ""
  • esf.cifs.inst.1.address ""
  • esf.cifs.inst.1.ldapPathAttribute ""
  • esf.cifs.inst.1.ldapUseridAttribute ""
  • esf.cifs.inst.1.ldapPathSuffix ""
  • esf.cifs.inst.1.domain ""
  • esf.cifs.inst.1.winsServer ""
  • esf.cifs.inst.1.brdAddr ""
  • esf.cifs.inst.1.authOptions "0"
  • esf.cifs.inst.1.uName ""
  • esf.cifs.inst.1.pwd ""
  • esf.cifs.inst.1.parentCode ""

Step 2: Generate a Password

The password must be base64 encoded. Encoders can be obtained on the web; i.e., www.base64encode.org/.

Example: Password123

Choose UTF-8

Step 3: Modify the UCF file and resend the file

Enter the newly generated password to the inside of the empty quotes. Each file share (shared folder) will have an entry for its own password.

  1. Enter the values from Step 2 above into the empty quotes as displayed.

    • esf.cifs.inst.1.cifs.pwd “UGFzc3dvcmQxMjM=”
    • esf.cifs.inst.1.pwd “UGFzc3dvcmQxMjM=”

  2. Save the file. Make sure you select UTF-8 encoding.

  3. Use the Import Solutions Settings File via EWS > Settings > Import/Export to configure the device with a password.

Additional information

Universal Configuration Files provide the ability to transfer settings to large fleets in a short period of time. This ASCII file is created via human interaction with an editor or automatic generation of the file via a program of some sort.

Key and Line structure

First element on a line comprises...Subsequent elements comprise..

UCF key

Parameters (directly associated with first element)

Acceptable values:

  • Upper or lower case
  • Two usable parameter limit.*

*Determined by the Key.

Not acceptable:

  • Double quotes around keys

Acceptable values:

  • A case sensitive ASCII string
  • A signed integer that can fit in 32 bits
  • An IP address of the form a.b.c.d...
  • A case-insensitive boolean in the set of {true, false, on, off}.
  • Should a parameter need to be separated by spaces, tabs, or special delimiters (%), the parameter may be enclosed in double quotes.

Not acceptable:

  • Any key with more than two parameters is ignored.

Example: IPADDRESS (Key)

9.51.8.43 (Parameter)

  • Comments are delineated by the % character remain for full length of the line.
  • Blank lines and lines that are only comments are valid.
  • For backwards compatibility reasons, any unknown keys/parameters processed by the device are ignored and should not generate errors.
  • A key with too many parameters, or if the file does not contain good data, likely results in the desired outcome not being achieved (i.e., garbage in, garbage out).
  • No check is made to determine whether a particular key has already been processed before it is processed again. In all likelihood, the last-encountered key would be the one that wins, though that is up to the code associated with processing that key.
  • Maximum .ucf file size is 10,000 bytes.
  • It should be noted that the size of the file as stored on a system might be different from the size of the file the print server receives if it has any required conversions (as with TFTP from Unix where it would be converted from Unix format to NETASCII format).
  • Example:
    • %
    • % created 24 April 1997
    • %
    • IPADDRESS 9.51.8.43
    • IPNETMASK 255.255.255.128
    • IPGATEWAY 9.51.8.1
    • SNMPCOMMUNITY cilbup
    • RESTRICT 1 9.51.8.0
    • RESTRICT 2 10.1.0.0 % allow accounting
    • LLNICKNAME "I'm a little teapot"
    • LLACTIVE true
    • NWACTIVE false
    • ATACTIVE true
    • ATTNAME "I Love PostScript"
    • GENCONTACT "Arnold Schwarzenegger"
    • GENLOCATION "Near Maria Schriver"

LEGACY ID: HO3923
Was this article helpful?


Related content

Top