Lexmark Integrated controller settings
Lexmark Integrated controller settings
These are the settings for a shared device whose Controller Type is Lexmark Integrated: the Print Director embedded app on a Lexmark device. For the device’s other settings, see Shared device settings.
To open them, edit the shared device (Print Management > Shared Devices, double-click the device) and click Controller in the list on the left. Below Controller Type are the Remote panel link, which opens the device’s remote panel in a web browser, and a second list of settings pages: General, Printing, Authentication, Billing, Cards and Initialisation.
To change several Lexmark devices at once, open Print Management > Lexmark Integrated, select the devices and edit them. Each setting then has a change box: tick it to apply that setting to all the selected devices, and leave the others unticked to keep each device’s own value.
Most settings are stored in the embedded app on the device. After changing them, send them to the device with Set all settings or Initialise (see Initialisation).
General
Workflows & home screen
| Setting | Description |
|---|---|
| Workflow profile | The set of workflow tiles shown on this device’s panel. Click … to search. Choose <do not install> to send no workflow profile to the device. See Workflow Profiles. |
| Allocate advanced workflow licence | Gives the device one of your advanced workflow licences. The number still available is shown. |
| Place PD buttons on home screen page 1 | Moves the PD Workflow and Release Job buttons to the front of the home screen. Untick it to leave the device’s home screen layout as it is. |
| Show Release Job button on home screen | Untick it to remove the button. Release Job is also available as a workflow, which, unlike the button, can enforce settings such as single-sided printing. The button is hidden anyway when Secure Document Release is off. |
Screen timeouts (seconds)
| Setting | Description |
|---|---|
| User input | How long screens that wait for the user (for example the user ID or the job list) stay open. |
| Message | How long message screens (for example the number of jobs released, or the user welcome screen) stay open. |
Panel search control behaviour
The user, account and matter screens on the panel can be searched.
| Setting | Description |
|---|---|
| Method | Starts with, or Contains (searching son finds Johnson). |
| Field | Code (the Controller User ID, account code or matter code), Name, or Both. |
Auto change Shared Device IP address
Update using IP address received from embedded app: when the app connects to the PDServer, the shared device’s Host or IP is updated with the address the device reports, for example after a DHCP change. Untick it if the device connects through a router using NAT.
Welcome screens
| Setting | Description |
|---|---|
| Before login | Shows a screen with a Login button. Tapping it starts the login, for example the card swipe or user ID screen. Untick it to start with the first login screen. |
| User after login | After login, shows the user’s full name and balance. If you do not enforce credit limits, you can untick it. |
Printing
Secure release
Tick Enable Secure Document Release so that jobs wait (on the PDAgent or the PDServer) until the user logs in at the device and releases them.
| Setting | Description |
|---|---|
| Follow me printing | Enabled lets jobs sent to any queue matched to a follow-me device be released at any follow-me device in the same pull print group. Disabled means jobs can only be released at the device their queue is matched to. |
| Pull print group | Limits follow-me printing to a group of devices, for example devices with compatible drivers. Click … to add or delete groups. |
| Release method | Individual selected release shows the user a list to choose from. Release all after login prints all their jobs as soon as they log in. |
| Auto open job list | With individual release: shows the job list as soon as a user with waiting jobs logs in. Otherwise they tap Release Job on the panel. |
| Stay logged in | With Release all after login: keeps the user logged in after their jobs are released. |
| Show message after release | Shows a confirmation after jobs are released. |
| Release jobs in order of | The order of the job list: by submitted date, alphabetical, total pages, file size or total cost, each ascending or descending. |
| Show mono or colour | Show all jobs, Only show colour jobs or Only show mono (black & white) jobs. On a mono device, showing only mono jobs stops users releasing colour jobs there by mistake; on a colour device, showing only colour jobs keeps mono jobs for cheaper mono devices. |
Download-print and native formats
| Setting | Description |
|---|---|
| Use download-print when supported | Released jobs and cloud workflow print jobs are fetched by the device from the PDServer over a one-time link and printed by the device itself. Cloud printing then does not need Secure Document Release. Needs Lexmark Integration (post tracking) and a current Print Director app connected to the PDServer; otherwise jobs are delivered through the print port as usual. A workflow relay agent or Fiery destination chosen in a workflow still uses its own route. |
| Native formats | The file formats the device prints directly, separated by commas, for example pdf,gif,jpeg,jpg,bmp,png,tiff,tif,pcx,dcx. Resource Manager warns you about a format it does not recognise but still saves it, as newer Lexmark firmware adds formats. |
Print job tracking
Tracking method sets how printed jobs are recorded:
- Lexmark Integration (post tracking) (recommended): the embedded app reports what was actually printed, which is more accurate. It is needed for Prevent unauthorised printing and for download-print.
- Datastream interpretation: Print Director reads the print data as it passes through the matched queues.
Prevent unauthorised printing
Available with Lexmark Integration (post tracking) only. Confirm OK to print sets whether the device checks each job with the PDServer before printing it:
- Allow unauthorised: jobs from any source print. Jobs that did not come through the PDAgent are only recorded if Record as user is set on the Authentication tab.
- Only allow jobs from PDAgent (recommended): the device looks for the authorisation the PDAgent adds to each job and has the PDServer validate it. A job without it is deleted.
- Allow if username authenticated: for systems that send jobs straight to the device, such as an ERP system. The device reads the user name from the job and has the PDServer validate it; the job prints and is recorded under that user. If the system does not put the user name where the device can read it, use Allow unauthorised instead.
Denied message is the text shown on the panel when a job is refused (Print not authorised by default).
Authentication
Authentication method
| Setting | Options |
|---|---|
| Identification method | Keypad login only (no card swipe screen), Card or keypad login (card swipe screen with a manual login button) or Card only (manual login disabled). |
| Password requirement | Only with keypad login (a swiped card logs in without a password), Always required or Never required. |
User name input
| Setting | Description |
|---|---|
| User ID input | Type only keeps user names private. Type or select shows a list of users to pick from or search. The second drop-down sets the panel keyboard: Alpha keyboard, or Number keyboard when every user ID is numeric. |
| User ID label | The label shown for the field on the panel. With Type only, tick Hide chars (*) to show asterisks instead of the characters, for example when the user ID is used like a PIN. |
Authentication requirements
| Setting | Description |
|---|---|
| Show idle authentication screen | The device always shows the login screen. Once logged in, a user can print, copy and scan without logging in again until they log out or the session times out. Untick it to show the device’s normal home screen; the login screen then appears when the user opens a function that needs a login. |
| Allow copy without login, Allow scan without login, Allow fax without login | Lets anyone use that function without logging in. These transactions are recorded under the Record as user below, which must be set. |
Non-authenticated transactions
Jobs nobody logged in for, such as configuration pages printed from the device menus, scan or fax logs, and copies, scans or faxes allowed without login. Tick Record as user and choose the user to record them; otherwise they are not recorded.
Billing
Billing fields are used with the PD Pro licence, to bill print, copy, scan and fax transactions to accounts and matters.
Account Code
| Setting | Description |
|---|---|
| Account requirement | User setting (the default) follows each user’s popup setting: a user who must choose an account when printing must also enter one to copy, scan or fax. No Account Code entry and Account Code required ignore the user’s setting at the device; it then only affects printing. |
| Account Code input | Type only, Type or select, or User setting (search accounts), and the keyboard: Alpha keyboard, or Number keyboard when every account code is numeric. |
| Field label | The name shown on the panel, for example Project if your site bills to projects. |
Matter Code
The same settings as the account code: Matter requirement (No Matter Code entry, Matter Code required or User setting), Matter Code input (with User setting (search matters)) and Field label. They are available when an account code is entered.
Comment requirement
Transaction comment adds a comment screen when the user starts a function such as copying. The comment is recorded against the transaction and shown in detailed reports: No comment field, User setting or Require comment.
Cards
| Setting | Description |
|---|---|
| Self-register cards | What happens when someone swipes a card that is not yet assigned to a user: Not allowed, or the card is registered once they identify themselves with PIN & password (AD or internal), PIN only or AD username & password. |
| Byte conversion method | How the card reader’s data is turned into a card number: Detect byte conversion, Treat bytes as literal numbers, Bytes are ascii codes for hex characters, Keyboard wedge codes for hex characters, Keyboard wedge codes for decimal characters or Keyboard wedge codes for string. |
| Data ordering | Normal or Reverse bytes. |
| Start bit and Bit length | Which bits of the data form the card number. |
Card readers with a keyboard wedge mode are supported. To set one up, initialise the device, swipe a few cards, then click View swipes to see how the data is read. If you know what a card’s number should be (printed on the card, or from an access control system), adjust the conversion, ordering and bit settings until the same number is extracted.
Initialisation
App management
| Item | Description |
|---|---|
| Use app version | The version of the Print Director app to install. Keep Latest unless the device is an older model that needs an earlier version; see PD Lexmark Embedded Licence Structure. |
| Initialise | Installs the app and sends all the settings. The app is ready to use afterwards. |
| Install | Installs and starts the app without sending the settings. |
| Uninstall | Removes the app. |
| Start app and Stop app | Starts or stops the app on the device. |
| Upload FTP | Sends the app to the device by FTP. Only for older firmware that does not accept web service calls. |
Initialise and Install need HTTPS (see below).
Printer connection settings
How Resource Manager connects to the device’s web interface.
| Setting | Description |
|---|---|
| Username and Password | Needed when the device’s Public access does not include the Apps Configuration permission (see below). |
| Use HTTPS | Keep ticked unless HTTPS has been turned off on the device. |
| Always trust device certificate | New devices use a self-signed certificate, which cannot be verified. Untick it only if the device has a certificate from a trusted certificate authority. |
App settings on device
| Item | Description |
|---|---|
| PDServer address | The address the device uses to reach the PDServer: one of the server’s IP addresses or its host name. If you use the host name, check the device’s DNS settings. Set sends only this setting to the device. |
| Read settings | Reads the app’s current settings from the device and shows them in the output box. |
| Set all settings | Sends all the settings to the device without reinstalling the app. |
| All app settings | Opens the App settings window (below). |
To set up a device:
- Choose the settings on the other tabs, for example Enable Secure Document Release on Printing.
- On Initialisation, check that PDServer address shows an address the device can reach.
- Click Initialise and check the output box below the buttons for errors.
- Click OK + Refresh All, then test by logging in at the device panel.
If initialising fails
Unauthorised: the device’s Public access does not include Apps Configuration (in the device’s web interface, under Access Controls > Device Management). Enter, under Printer connection settings, the credentials of a local account that has it. Use the device’s Default Login Method for the browser (Settings > Security > Local Accounts): for User Name/Password enter both; for PIN or Password enter only the Password; for User Name enter only the Username.
InternalServerError: usually the device does not support the app version being installed. Choose another Use app version.
A Lexmark Log In screen appears instead of Print Director’s: the device has local accounts. In its web interface, go to Settings > Security, click Change beside Default Control Panel Login Method, choose Print Director Auth and click Save.
App settings window
Click All app settings on the Initialisation tab. Pull current settings from device replaces what the window shows with the settings currently on the device.
PDServer connection
These apply to app version 3 and later.
| Setting | Description |
|---|---|
| Device key | The key the app uses to identify itself to the PDServer. It is created automatically and is different for each device, so it cannot be changed for several devices at once. Generate creates a new one; send it to the device with Set all settings or Initialise. |
| Timeout | How many seconds the app waits for an answer from the PDServer (1 to 600, 30 by default). |
| Keep device CPU available for cloud requests | Ticked by default: the device’s processor stays awake while the panel sleeps, so releases, cloud workflows and remote device queries are answered straight away. Untick it to save power; those requests may then wait until the device wakes. App version 3.0.1 and later. See How to balance Lexmark power saving and cloud availability. |
Legacy prompt screens
Images and colours for the app’s older prompt screens, which app version 3 rarely shows. For each image, untick Use default and click Choose file (gif, jpg or png, at most 480 by 272 pixels).
| Setting | Description |
|---|---|
| Top left image | 70 pixels high and 70 to 350 pixels wide. |
| Bottom left image | 70 pixels high and 70 to 100 pixels wide. |
| Release job button up image and down image | The Release Job button when not touched and when touched, 80 by 80 pixels. |
| Colours (6 digit RGB hex) | Top bar and Bottom bar (9CCAEE) and Prompt text (29166F); set default restores one. |
The PDServer’s listening port for Lexmark devices is set in Resource Manager under Tools > System Configuration > Networking.
Related articles
- Shared device settings
- Workflow Profiles
- PD Lexmark Embedded Licence Structure
- How to balance Lexmark power saving and cloud availability
- How to set up IPPS on Lexmark printers
- How to harden the security of Lexmark printers
- Lexmark print permissions for delivered jobs
| Document revision date: 2026/10/23 Software version: 2.5.15.3 |