Requirements

Operating Systems

Dispatcher Phoenix is designed to work on the following platforms:

• Windows Server 2022
• Windows Server 2019
• Windows Server 2016
• Windows 11
• Windows 10

Supported Architectures

• x86 (32-bit)
• x64 (64-bit)

Notes:

• Support is not included for the home, small business, server core, or essentials editions of any Windows Operating Systems.
• Only the latest Service Packs are supported for each Operating System version.
• Domain Controllers are very important to all aspects of your environment; installing any software on them will take resources away from core functions (authentication, authorization, security, auditing, etc.) that can impact every user and computer in the entire domain.
• When using Dispatcher Phoenix Workflow Services on Intel’s Tiger Lake processers, workflows may stop unexpectedly moments after they are started. The Windows Event log will contain a “crypto.dll” error. If you experience this issue, please refer to Intel’s published fix.

Installed Dependencies

Dispatcher Phoenix installs the following dependencies:

• Microsoft Windows Imaging Component (WIC)
• Windows PowerShell 2.0
• Microsoft Visual C++ 2010 Redistributable x86
• Microsoft Visual C++ 2010 Redistributable x64
• Microsoft Visual C++ 2013 Redistributable x86
• Microsoft Visual C++ 2013 Redistributable x64
• Microsoft Visual C++ 2015-2019 Redistributable x86
• Microsoft Visual C++ 2015-2019 Redistributable x64
• Microsoft .NET 4.8 Redistributable

Hardware Requirements

It is important to note that since image content varies greatly between files, performance will depend on the images being processed and the workflows concurrently running. It is suggested that you use the recommended hardware configurations below:

Notes:

• Typical document specifications: 50 pages, 50% text/images, 75% black & white.
• Offload servers are recommended for any installation of 50+ MFPs.
• Performance is directly related to hardware specs.
• OCR workflows require a quad core processor.

Firewall Exceptions

When enabled, the Windows Firewall blocks all incoming network traffic to your computer except those applications and ports you allow. When installing Dispatcher Phoenix, please note that the following folders should be excluded from anti-virus software:

• C:\Program Files\Konica Minolta\
• C:\Program Files (x86)\Konica Minolta\
• C:\Program Data\Konica Minolta

In addition, the following Dispatcher Phoenix executables most often trigger an alert:

• C:\Program Files\Konica Minolta\blox\blox-xmpp-cluster.exe
• C:\Program Files\Konica Minolta\blox\blox-xmpp-worker.exe
• C:\Program Files\Konica Minolta\conopsd\erts-5.10.4\bin\erl.exe
• C:\Program Files\Konica Minolta\conopsd\erts-5.10.4\bin\erlsrv.exe

Note: The folder name for the erts-X.XX.X executables is subject to change.

Dispatcher Phoenix writes workflow, configuration and log files to the following locations:

• %appdata%\Konica Minolta\Dispatcher Pro Phoenix Edition
• %localappdata%\Konica Minolta\BarcodeGenerator
• %localappdata%\Konica Minolta\BubbleGrader
• %localappdata%\Konica Minolta\Dispatcher Phoenix MFP Simulator
• %localappdata%\Konica Minolta\Dispatcher Pro Phoenix Edition
• %localappdata%\Konica Minolta\Form Builder
• %commonappdata%\Konica Minolta\kmf
• %commonappdata%\Konica Minolta\MFP Explorer
• %commonappdata%\Konica Minolta\Moxie
• %commonappdata%\Konica Minolta\Patterns
• %commonappdata%\Konica Minolta\Workflow Services Manager

Note: Dispatcher Phoenix also writes configuration data to the Windows Registry.

Depending on what optional Add-Ins are installed, you may not have all of the above folders. You can exclude only the parent folder %appdata%\Konica Minolta\ and %localappdata%\Konica Minolta\ as long as the anti-virus includes the sub-folders. Remember that these are User specific folders so each logged in User has their own copy of these folders.

Ports & Executables

• KMBS bEST Server
  • EXE: C:\Program Files\Konica Minolta\Tuscon\Tuscon.exe
  • Inbound Ports: 50808 (HTTP), 50809 (HTTPS)
• KMBS LPR Service
  • EXE: C:\Program Files\Konica Minolta\blox\blox-lpd.exe
  • Inbound Port: 515 (LPD)
• KMBS SMTP Service
  • EXE: C:\Program Files\Konica Minolta\blox\blox-smtp.exe
  • Inbound Port: 25 (Default, but configurable within SMTP Manager)
• SEC Workflow Worker Process
  • EXE: C:\Program Files\Konica Minolta\conopsd\erts-7.3\bin\erl.exe
  • Output Port: Will try to bind to any Outbound Port required by the workflow (e.g., 53, 80, 443, 25, 445, 465, 587)
• Add-In Manager
  • EXE: C:\Program Files\Konica Minolta\AIM\2.6.0.0\AIM.exe
  • Outbound (HTTP) Port 80, (HTTPS) Port 443

Konica Minolta MFP Prerequisites

Dispatcher Phoenix workflows run on MFPs with either Graphical and Native User interfaces. Requirements are:

• For graphical user interfaces, the i-Option (LK-101 or LK-101 v2) and additional memory are required.

• For native user interfaces, the i-Option and additional memory are NOT required.

Device Requirements for MFP Panel Node Workflows

• To register Dispatcher Phoenix on bEST-enabled MFPs, the device must support OpenAPI 3.5 or higher. To verify the version of OpenAPI that is supported, we recommend checking the firmware’s release notes.

• To use Advanced Scan Settings (Blank Page Removal, Separate Scan, Document Sizes), the device must support OpenAPI 4.13 or higher. These devices are listed below:

  • bizhub C287, C227
  • bizhub 367, 287, 227
  • bizhub C368, C308, C258
  • bizhub 958, 808
  • bizhub C658, C558, C458
  • bizhub 558, 458, 368, 308
  • bizhub 658e, 558e, 458e, 368e, 308e
  • bizhub C759, C659
  • bizhub C3851FS, C3851, C3351
  • bizhub 4752, 4052

For more information on device requirements, click here.

Software Maintenance

Software Maintenance (offered in 1, 3, and 5 year increments) is required for the Dispatcher Phoenix main application and all add-in modules. This maintenance covers:

• Minor and major updates
• Maintenance releases
• Support of new operating systems
• Critical fixes

When maintenance expires, you can continue using the application. However, to receive updates or install new packages, software maintenance must be kept active.

Notes:

• Main Application - If software maintenance expires on the main application, you must buy and activate maintenance within 90 days of expiration; after this 90-day grace period, you must also purchase and activate a Maintenance Renewal Activation key that is associated with the main application.

• Add-In Modules - If software maintenance expires on an add-in module (such as Advanced OCR), you can buy and activate the maintenance at any time.

All supported device models are listed on the MFP Supported List. If End-of-Support (EOS) for Dispatcher Phoenix on an older device model series is announced, support will no longer be guaranteed on the impacted devices after the EOS date is reached.