Summary

The architecture of YSoft SafeQ 5 and Dispatcher Paragon is completely different and may require changing the architecture of the current solution, so please consider whether is not necessary to customer support, e.g., if there are more application servers in a cluster or a database cluster with fail over.

This document describes how to upgrade a non-trivial environment with YSoft SafeQ 5 with more servers in a cluster, ORS servers, etc., through Dispatcher Paragon server installer (for manual upgrading, see this article).

See general summary of the upgrade to get more information.

Prerequisites

See General prerequisites.

If the SQL Server Express edition is used on a cluster node and a highly-available MSSQL server will be used, then the database from one cluster node must be restored on the highly-available server.

Upgrading the First Server in a Cluster

1. Check that all prerequisites are fulfilled.

2. Install the Dispatcher Paragon last build with the server installer on the same server where older the YSoft SafeQ 5 CML is installed.

   1. The installer detects the old installed version and asks if it should be upgraded.

   2. The installer will stop and set these old services for manual starting.

   3. YSoft SafeQ 5 Terminal Server service is renamed to YSoft SafeQ Terminal Server 5.

   4. The installer will install the new Dispatcher Paragon Management Service and Spooler Controller into the new directory. Local Spooler Controller must be installed (it is part of the server installer) if the original YSoft SafeQ 5 installation does not have any ORS group set up.

   5. The installer runs the Upgrade Tool automatically.

      1. If there is an error in the upgrade, the installer displays an error message with detailed information about the error.

      2. If there is a warning in the upgrade, the installer displays a warning message with information that it is strongly recommended to review the changes to adjust them to match business requirements.

   6. The installer starts the newly registered services, and Dispatcher Paragon is up and running.

3. See Upgrade Tool logs and report if all steps were successful.

   1. If the Upgrade Tool succeeds, ensure that all Common after successful upgrade steps are performed.

   2. Otherwise, the errors must be investigated according to The YSoft SafeQ 5 to Dispatcher Paragon Upgrade Tool documentation.

4. After the upgrade, the previous version of the YSoft SafeQ 5 is still in the system. It is possible to uninstall it manually (later) by running the YSoft SafeQ 5 uninstaller.

Upgrading the Second or Next Server in the Cluster

1. Install Site Server with the Dispatcher Paragon server installer

   1. The installer detects the old node of the YSoft SafeQ 5 installation and offers the installation of the new cluster node of Dispatcher Paragon.

   2. If the new node is not installed, there is no need to perform any manual steps, or it is possible to install the new cluster node later (if the node is not crucial).

2. After the upgrade, the previous version of YSoft SafeQ 5 is still in the system. It is possible to uninstall it manually (later) by running the appropriate YSoft SafeQ 5 uninstaller.

3. Ensure that all Common after successful upgrade steps are performed (mainly, the re-installation of device terminals).

Upgrading the ORS Servers

1. Install Site Server with the Dispatcher Paragon server installer.

   1. The installer detects the old installed version of the ORS server and offers to upgrade the Site Server.

   2. If the upgrade is selected, the Site Server with the same GUID is installed, and there is no need to perform any manual upgrade steps.

   3. If the ORS server is not upgraded, it is necessary to resolve the devices connected with this Site Server:

      1. Log into Management Service > Devices > Filter devices according to the Spooler Controller group with the same GUID as the not-upgraded ORS > Check all these devices > Click Actions > Edit.

      2. Change the Spooler Controller group (to a migrated one), and save the form.

      3. It is possible to remove the unused Spooler Controller group in the Spooler Controller groups submenu.

2. Ensure that all Common after successful upgrade steps are performed (mainly the reinstallation of device terminals).

Common Steps after a Successful Upgrade

• Because of upgrade does not solve licensing of migrated devices and entities in general, there can be the notification that re-licensing of the product is necessary for Management Service notifications (after administrator signs in). Reactivation must be done within 10 days after upgrade otherwise the devices can be removed from the system. Also, devices will not work until reactivation because of technical limitations. See how to activate new license after upgrade.

• Check in general that migrated data are as expected.

• If Dispatcher Paragon manages printing devices, all device terminals must be reinstalled (use Devices > Printers > select all devices > Actions > Reinstall terminal). After re-installation check that devices working properly.

• • All Konica Minolta Embedded Terminals requires setting of " Terminal mode ".

• System configuration properties which should be reverted to default values:

  • mpsJobSendFailed

  • mpsMailAuthenticationFailed

  • mpsMailDuplicateAddress

  • mpsMailFooter

  • mpsMailHeader

  • mpsMailSendFailed

  • mpsMailSendOk

  • rejected-email-text

  • ruleBasedEngineConfigurationProblemsEmailBody

  • ruleBasedEngineConfigurationProblemsEmailSubject

  • sslPortInfo

  • welcome-to-safeq-text