Skip to Content Information Center
Print Release

Print Release

LFM 3.0 Announcement Information (July 2013)

Audience: Lexmark and Partner only (July 2013)

About Lexmark Fleet Manager (LFM)

  • Comprises several application components that manage and track job statistics, maintenance items, and consumable supplies
  • Works with any size printer fleet but is optimized for small to medium-sized businesses
  • Adapts to environments that utilize multi-branded devices
  • A partner channel product

New LFM 3.0 Announcement (LFT 3.0)

What's New

  • Improved GUI interface further elevates competitive stature in the market.
  • New capabilities
  • New reports

Upgrade / Rollout

  • General Announce is planned for 7/31/13.
  • Rollout is strategic, based on customer needs, and new contracts will be set up using LFT 3.0 in August 2013.
  • What happens to existing LFT 2.0 contracts? At no cost to contract partners, existing partners will be able to convert to LFT 3.0 and replace their current LFT-MSP (with the help of their Lexmark representative); however, this will be a gradual transition as the new product evloves and improves.
  • LFT 3.0 will be installed with a port mirror that will provide data to DBs for both their current LFT-MSP and their new LFT 3.0.
  • Data will be concurrent until LFT 3.0 is stable and has enough historical data to outweigh LFT 2.0.

TSC Support

The technical support center should be available for customers attempting to install collectors or experiencing issues.

Need to know...

  • Contract partner contacts the TSC seeking help with LFT 3.0.
  • Agent should know how to check for upgrades and licensing.
  • Agent should know how to access PartnerNet and utilize LFM documentation.
  • Upgrades to LFM 3.0 for troubleshooting purposes is not an option.
  • Licensing will be through Flexera going forward – apply a license file – no more online activations.
  • LFT 3.0 will be node locked – this protects Lexmark but could inhibit flexibility for a partner.
  • Location MAC address and Hostname must be known prior to license file creation.

Good to know...

  • Installation, setup, or upgrades to LFT 3.0
  • Integrated packaged db (PostrgreSQL)
  • Db flexibility (PG and Oracle now….MSSQL near term)
  • LFM 2.0 is now just LFM
  • Contract partners will not self upgrade to 3.0.
  • TSC should be equipped with locally installed collectors rolled up to an LFT 3.0; one of each collector on different subnets (LSM, eLSM, LLT and LPMA when available).
  • New LSM handles up to 1k devices (increased from 500).
  • LLT can roll up through an eLSM – allows hundreds of LLTs thus limiting traffic and pre-including groups – this eliminates the need for a local LFT to roll up only a few LLTs.
  • Grouping & Viewing flexibility
  • Reporting backend
  • Variable levels of LFT users
  • Managed vs Unmanaged devices
  • Text message alerts
  • LPMA Improvements over LLT
  • Eventual replacement to LLT
  • Enhanced local device and user detail support

LPMA (Lexmark Print Management Agent) (Birch)

  • New local attach collector for Windows and Mac.
  • Replaces LLT (Lexmark Local Tracker)
    • This collector can get USB connected device data and user data.
    • It can be used on local workstations and print servers.
  • LPMA will have the ability to roll up data directly to LFT 3.0.

How is LLT functionality different between Version 2 and Version 3?

Version 2 rolls data to another local collector before going to an MSP.

Key differences

  • Configured company and location codes for auto-grouping back at LFT
  • LLT device detail level PLUS toner levels and alerts
  • Now provides more granular and accurate job data

Version 3.0 Early Challenges

  • Various collector installation issues
  • Collector update methods
  • Roll Up configuration on a collector
  • Port access
  • Firewall access to the MSP or 3.0
  • Not getting e-mail alerts
  • Device support Issues
  • Integrated Apps not functioning (3rd Party- eAutomate)
  • Port Mirroring not functioning
  • Minute data integrity anomalies (LFT-MSP reports do not match LFT 3.0)

LEGACY ID: FA966

Audience: Lexmark Only


NOTE:
Some of the information below is subject to change without notification.

Product History

The Lexmark acquisition of 366 Software Inc. provided a full product offering for printer life cycle management software. This software has been

  • System administrators
  • Corporations
  • Dealers
  • Print service providers
  • Healthcare markets in the United States

Initial offerings

  • PrinterRx– print tracking software that tracks and monitors printers and printing activities necessary for onsite management of a corporation’s printer fleet
  • PrinterRx MSP– a solution that gives the print service provider a tool to centrally manage various customer sites and installations
  • rXpress– a solution used in small sites, quick audits, and collecting meter reads and quotes for printer assessment
  • pDesktop– an add-on module to printerRx that tracks desktop printers and user-printing statistics. It serves customers through dealers, distributors, and wholesalers. (http://www.pendlprint.com/uploads/printerRX_prod_overview.pdf)

Key Competitors

PrintFleet – http://printfleet.com/

PrintAudit – http://www.printaudit.com/office-equipment-dealers.asp

Growth and Other Information

  • 150 contracts in place by EOY13 with 113 current contracts and about 20 contracts are clamoring for an upgrade.
  • LA has two pending contracts for Mexico and Argentina.
  • There are some non-partner contracts where the customer uses LFM internally (Paychex).
  • PN for LFT 3.0 is 82S0528 (not saleable).
  • Non-Node locked demo license files will be available for periods from 60-90 days.
  • TSCs will get a five-year node locked license.
  • Each partner customizes their LFT-MSP to provide service.
  • Billing is based on the total number of devices managed in groups of 500.
  • Some contracts are managing 30-50k devices while others are doing 500-1k.
  • When a new contract is signed, a Lexmark representative will work directly with the partner to set up their LFT-MSP and then train them on how to install the appropriate collectors for their needs.

LFM Components

Component...Used by...Purpose...Good to know...
Lexmark Fleet Tracker Master Service Panel (LFT-MSP being replaced)Your contract partnerPrimary GUI application used for managing your devices
  • This interface utilizes a local database that receives data from collectors installed at each client site.
  • Will be replaced by LFT 2.0
Collectors LFTDevices generating or collecting use data in a business workflow environmentServe as data usage repositories before getting sent to LFT-MSP

LEGACY ID: FA966

Was this article helpful?
Top