The first step in enrolling printers is to decide which agent or agents to use. You may choose from the Native Agent, Fleet Agent, Printer Agent, or Local Agent.
Note: Collectively, the agents are referred to as Cloud Bridge.
Native Agent
The Native Agent is built into the printer firmware. It is available on all current‑generation Lexmark printers. The control panel on current‑generation Lexmark printers has a dark background.
Sample of the control panel from a current‑generation printer that supports the Native Agent.
- Requires firmware 081.215 or later is required. For more information, see Viewing the printer firmware version.
- Supports data collection and configuration on all current generation printers.
- Supports the deployment of eSF applications on current generation, touch-screen printers. For more information, see Supported printer models.
- Native Agent–capable printers can be enrolled using the following methods:
- Cloud-based pre-enrollment
- Printer-based enrollment
- Printer Enrollment Tool (PET)
- Requires the printers to have a constant Internet connection.
- Uses Internet of Things (IoT) technology to reports printer data to the cloud.
Fleet Agent
The Fleet Agent is an application that is configured and installed on an on‑site server or host computer. It enrolls Lexmark and third-party printers to the Lexmark Cloud Services.
- Uses Internet of Things (IoT) technology to report printer data to the cloud.
- Requires a stable, high-availability server or host computer with a constant Internet connection and with the following minimum specifications:
Operating system | x86, x64-bit or Linux 64-bit |
Processor | 1Ghz dual‑core |
RAM | 2GB |
Storage | 32GB (Fleet Agent requires 12GB of storage) |
- Supports printer configuration and data collection with Lexmark printers. For more information, see Supported printer models. Data collected and printer configuration capabilities may vary by model.
- Data is collected over Simple Network Management Protocol (SNMP) from the public and private printer MIBs available on the enrolled printers.
- Supports data collection for some third-party printers. Data collected varies by manufacturer and model.
Printer Agent
Printer Agent
The Printer Agent, also referred to as embedded agent, uses an embedded application, the Printer Configuration Agent (PCA), installed on each Lexmark printer. The Printer Configuration Agent collects and sends the printer information to Lexmark Cloud Services.
- Requires running the Printer Enrollment Tool on a network connected computer to discover and enroll printers.
- Supports data collection and configuration on Lexmark touch-screen printers with eSF version 3.0 or later. For more information, see Supported printer models.
- Requires the printers to have a constant Internet connection.
- Uses Internet of Things (IoT) technology to report asset inventory (meters, counters, and supplies) data. If the IoT hosts are blocked during enrollment, then this agent reverts to the https path.
Local Agent
Local Agent
The Local Agent is an application configured and installed on a Windows computer system that has USB-attached printers. It enrolls locally attached Lexmark printers into Lexmark Cloud Services. It uses an Internet of Things (IoT) connection to communicate with Lexmark Cloud Services.
- Automatically discovers and enrolls USB-connected, Lexmark printers.
- Uses Internet of Things (IoT) technology to report asset inventory (meters, counters, and supplies) data.
- Supports Windows 64‑bit and 32-bit operating systems.
Comparing agents
To make sure that you have an optimal experience in enrolling and managing your print fleet, select the correct agent for your specific needs.
- If managing a current‑generation Lexmark touch‑screen printer with eSF version 5.0 or later, then use the Native Agent, Fleet Agent, or Printer Agent.
- If managing Lexmark touch‑screen printers with eSF version 3.0 or later, then use either the Printer Agent or the Fleet Agent.
- If managing a group of touch‑screen and non-touch‑screen Lexmark printers, then use the Fleet Agent.
- If managing a group of Lexmark and third-party printers, then use the Fleet Agent.
- If managing USB-connected Lexmark printers, then use the Local Agent.
- If eSF applications cannot be installed on the printers to be managed, then use the Fleet Agent.
- If an on‑site server or host computer cannot be used, then use either the Printer Agent or the Native Agent.
- All agents may be used in the same organization at the same time.
- A printer can only be managed by one agent.
| Scenario | Native Agent | Fleet Agent | Printer Agent | Local Agent |
|---|
1 All printer-cloud communications use IoT. IoT support is resident in the printer firmware. 2 IoT default communications path for asset inventory (meters and counters) data. If IoT connection cannot be established, then an https path is supported. 3 All cloud communications use IoT. 4 For more information, see Supported printer models. 5 When the printer is connected to a workstation through USB. |
Uses an agent native to printer firmware | ✔ | X | X | X |
Uses an application running on an Internet‑connected, on‑site server or host computer | X | ✔ | x | X |
Uses an embedded application running on enrolled printers | X | X | ✔ | X |
Supports USB-connected printers | X | X | X | ✔ |
Internet connection required for printers | ✔ | ✔ | ✔ | X |
Uses Internet of Things (IoT) technology | ✔1 | ✔3 | ✔2 | ✔2 |
Supports data collection and configuration in Lexmark printers with eSF version 5.0 or later (touch‑screen models) | ✔4 | ✔4 | ✔4 | X |
Supports data collection and configuration in Lexmark printers with eSF version 3.0 (touch‑screen models) | X | ✔4 | ✔4 | X |
Supports data collection and configuration for Lexmark printers with eSF version 2.0 | X | ✔4 | X | X |
Supports data collection for non-eSF Lexmark printers | ✔4 | ✔4 | X | ✔5 |
Supports data collection from third‑party printers | X | ✔ | X | X |
Requires a user account on the printer with administrative access | X | X | ✔ | X |
Performs data collection over SNMP | X | ✔ | X | X |
Before enrolling
To make sure that the enrollment of printers is successful, do the following::
- Make sure that the printer to be enrolled supports the agent to be used. For more information, see Supported printer models.
- If a firewall or proxy is used, then add the proper host names to the Allow List.
- If the printer was previously used at another customer site, then unenroll the printer from its current organization in the Cloud Fleet Management portal. If necessary, also erase the printer memory.
When erasing printer memory, note the following:
- Unenrolling must be performed the first time a printer is enrolled with a customer.
- Any configuration settings or customer data related to a prior installation is deleted. For more information, see Erasing printer memory..
- Make sure that all printers are online and in the Ready state with no unresolved errors, such as paper jams or incorrect email configurations.
- The printer firmware is updated to the latest recommended version.
- Printer permissions are set correctly.
- Printer login credentials for secure printers are available.
- Printer SNMP configurations are available.
- When using the Fleet Agent, SNMP v3 must be enabled on eTask version 5.0 and higher printers.
- By default, SNMP v3 must be enabled on these models.
- SNMP v3 does not have to be configured. It must be enabled.
- Make sure that Firewall, DHCP, and DNS settings are correct.
- The date and time are configured correctly, preferably using a network time protocol server.
- If possible, enroll printers during off hours when the printers are not being used.
- Firmware and configuration deployments from Cloud Fleet Management following enrollment may briefly take the printer offline.