This information is also applicable for Develop, Olivetti, and Aurora devices.

Requirements

  • A licensed and configured Konica Minolta OpenAPI platform at the device (OpenAPI version 3.6 or higher) is required.
  • Konica Minolta OpenAPI3 Account Map is the recommended option for accounting.
  • The Konica Minolta MyPanel application or web browser support requires OpenAPI version 3.6 or higher and an iOption license.

  • Most of printers require extended memory and a hard drive for full functionality (more details in Hardware Compatibility List).

  • For the precise accounting of billing codes for copy and scan jobs, the devices must be able to correctly provide the Track ID information. Support for Track ID can vary per device model and firmware version. If Track ID is provided, the job is accounted with the billing code from Track ID, otherwise, the job is accounted to the billing code that is currently selected. Print jobs are accounted to the billing code that is currently selected.
  • Failover with etcd enabled or with a shared DeviceConfigurationData folder is needed if you use localized keyboards or if you are experiencing issues with user IDs. Usage of etcd is preferred for all failover solutions on Konica Minolta. More information can be found in the article Configuring Terminal Failover. 
  • Setting OpenAPI to version 4.2 is required in order to successfully establish a secure connection for downloading the device description to the Terminal Server.

Known Limitations

  • The terminal inactivity timeout setting in the user's additional configuration is supported only for Dispatcher Paragon Embedded Terminal for Konica Minolta - 2nd Gen.. The timeout can be also set directly on the machine. For more information, see Konica Minolta - Configure inactivity timeout.
    • Timeout priorities are following: Dispatcher Print - both timeouts are applied, Dispatcher Scan - only SafeQ timeout is applied, other screens - only device timeout is applied.
  • For limitations related to printing from USB, see the article printing from USB on Dispatcher Paragon Embedded Terminal for Konica Minolta.
  • By default, the scan jobs performed by a user with insufficient credit are accounted. This may cause a discrepancy between Dispatcher Paragon reports and the information in Payment System. This behavior can be altered when the configuration "accountingCanceledScanWithZeroPages" is set to "Enabled". The canceled scan job is accounted with 0 pages, so accounting information from the MFD is ignored.
  • Jobs performed by a public user and jobs sent directly to the printer are not accounted.
  • Users with the username "admin", "ce", "public", "logadmin", "boxadmin" or "other" are not supported.
  • OpenAPI 4.0 or higher:
    • The scan workflow's description cannot be longer than 60 characters.
    • In the scan workflow settings, the value attribute of an administrator parameter (or the default value of a user parameter) must not be longer than 64 characters.
  • Native interface:
    • A simplex/duplex option for the scan is not propagated from the scan workflow template on IT4 generation devices and older ones. Therefore, these settings have to be set manually on the device's panel.
    • It is not possible to mark jobs as favorite.
    • When device doesn't recognize paper size of scanned document, native interface will shown, on IT4 devices the selected paper size has to be confirmed by HW button to start scanning.
  • There can be only five jobs in the device scan job queue, the sixth job will fail with the error code 21 in the OpenAPI log. It is caused by the device having finite resources.
  • For the 367 series onward, MFPs not implemented with enhanced memory fail on scans with a compact PDF and high resolutions.
  • A black and white scan with a JPEG and Compact PDF file format is not supported by all devices, and on some, scans may fail without any appropriate message.
  • The terminal might not work properly if the MFD certificate validation is enabled (configuration option enableMfdServerCertificateValidation).
  • Authentication in offline mode is not supported with the Dispatcher Paragon Terminal Application - 2nd Gen.
  • Authentication methods requiring authentication by card are not supported with Serverless Pull Printing. The affected authentication methods are Card, Card and username/password, Card and PIN, Card and PIN (if PIN exists). This is caused by the inability of the printer driver to get a card number for the job authentication and thus the job sent to the device can not be assigned to a user.
  • Native "Blank Page Removal" scan feature is not available with Dispatcher Paragon scan workflows. It is available only if native scanning is used.
  • A secure connection for downloading the device description to the Terminal Server is not supported for OpenAPI version 4.13.

  • Device settings became inaccessible (greyed out) when the HW home button is used to exit.
    Dispatcher Paragon application.

  • When a printer's input field and the virtual keyboard are displayed on the terminal then a card swipe is redirected into the input field. As a result, the card swipe cannot be processed as a login attempt. As a side effect, the card number is displayed in plain text in the input field. 

  • Konica Minolta OpenAPI supports about 30 panel languages. Dispatcher Paragon Embedded Terminal for Konica Minolta supports more than that. When you select an unsupported panel language either in MFD settings or in Dispatcher Paragon Terminal Application - 2nd Gen., e.g. Estonian, Welsh, Bulgarian, Basque, an error "Application startup failed." might be displayed after logging in. After closing the error window, Dispatcher Paragon Embedded Terminal for Konica Minolta is translated into the selected language. Switching to an unsupported panel language in Dispatcher Paragon Terminal Application - 2nd Gen. causes the MFD panel isn't translated into the unsupported language but Dispatcher Paragon Terminal Application - 2nd Gen. is.

Finishing options

  • The proper functionality of Advanced Finishing options is only guaranteed only when using one of Dispatcher Paragon Universal Print Drivers.

  • Not all Finishing options are supported on every device, for detailed information, please see the Hardware Compatibility List.

Quotas

  • Summary
    • Stop-on-zero works only with a single quota defined for the user.
    • The terminal eventually detects if a user exceeded a quota. The amount by which a user can exceed a quota depends on other quotas applicable to the user.
    • If the terminal detects that a quota has been exceeded, a warning screen is displayed with a "Start" button on it. The user must log out. This applies both for native and browser-based terminals.
    • For combinations of color and black and white quotas for given operation, if black and white quota has been depleted then color is also inaccessible.
  • Details
    • Page quotas are simulated using credit, prices, and restricting device functions.
    • Prices and device function restrictions are set at the beginning of a user session and cannot be changed during the session.
      • Operations limited by a quota with a zero or negative remaining balance are blocked. For example, COLOR 0 blocks all color jobs.
      • Operations limited by a quota with a positive remaining balance are limited by the total number of operations. For example, PRINT 1 and COPY 1 mean two possible operations. See below for full details.
      • Operations for which no quotas apply remain unlimited. For example, if page quotas are set for PRINT COLOR and PRINT BW, the number of copies is not limited at all.
    • The total number of operations allowed by a particular combination of quotas is the maximum of the following sums of remaining balances (undefined quotas and quotas with a negative balance are counted as zero):
      • PRINT + COPY
      • COLOR + BW
      • PRINT BW + PRINT COLOR + COPY BW + COPY COLOR
      • COPY + PRINT BW + PRINT COLOR
      • PRINT + COPY BW + COPY COLOR
    • If a user reaches the limit of the total number of operations, a warning screen is displayed with a "Start" button on it. The user must log out. This applies both for native and browser-based terminals. 
  • Example: A user has COPY 1, PRINT 1, BW 1. Other quotas are not defined. Upon login, no function is disabled and the user gets two operations. The user can now perform any two operations in one session.
    • Scenario 1: The user performs two BW prints. The resulting quotas are COPY 1, PRINT -1, BW -1. Upon the next login, the user is restricted to performing any BW jobs and any print jobs with one action left. Therefore, the user can perform only one color copy.
    • Scenario 2: The user performs one BW print and one color copy. The resulting quotas are COPY 0, PRINT 0, BW 0. The user can now not perform any further operations.
    • Scenario 3: The user performs one BW print and one BW copy. The resulting quotas are COPY 0, PRINT 0, BW -1. The user can now not perform any further operations.
    • Scenario 4: The user performs two color prints. The resulting quotas are COPY 1, PRINT -1, BW 1. Upon the next login, the user is restricted to perform any print jobs with one action left. Therefore, the user can perform only one copy.