An Environment with a Single Management Server

1. If you have only one standalone Dispatcher Paragon Management Server, uninstall it.

2. Prepare a server (or virtual machine) with the new IP address.

3. If you are using an external database (on another server), check its state.

   1. If the external database is damaged, perform a Recovering Databases but skip the Finalization part for now.

4. Check the backup of the configuration files and note the following:

   1. Which optional features were installed:

      1. Mobile Print Server – the MPS folder is available in the backup files.

      2. Payment System – the YPS folder is available in the backup files.

   2. A Management Server GUID. It is noted in the safeq.properties file as the value of the parameter communicator.cml.guid. For example:

      backup\Management\conf\safeq.properties

      # COMMUNICATOR

      communicator.cml.guid = MGMT1

   3. A SPOC GUID. It is noted in the guid.conf file as the value of the LocalGUID option. For example:

      backup\SPOC\conf\modules\guid.conf

      localGUID = ectp5o8ep0op3hzi

5. Reinstall Management Server using the same build version of the installation package as you were using before.

   1. Enable optional features if they were used before (see step 4.a.)

   2. Provide the wizard with the same Management Server GUID that was used before (see step 4.b.)

   3. Finish the installation.

      See First server installation for a detailed procedure.

6. Stop almost all Dispatcher Paragon services after installation has finished.

   1. Leave only this YSoft service running:

      1. YSoft Bundled PostgresSQL 9.4 (available if embedded PostgresSQL DB is used)

   2. You can use the following PowerShell script to perform the task

      Get-Service *YSoft* | Where-Object {$_.Name -notmatch 'YSoftPGSQL'} | Stop-Service

7. If you are using an embedded PostgreSQL database, perform a Recovering Databases but skip the Finalization part for now (as new empty databases were created during installation).

8. Update the IP addresses in the database.

   1. Connect to the SQDB6 database, the cluster_mngmt schema, and check the contents of the cluster_server table:

      1. If there is only one record with the server_guid of the reinstalled node, then update the ip_address value to match the new node.

      2. If there are two records with the same server_guid but different ip_address, then delete the record that contains the IP address of the old server.

   2. Connect to the SQDB6 database, tenant_1 schema (or the schema to which your server with the replaced IP address belonged, tenant_1 is default), and check the contents of spooler_controllers table:

      1. Find the record where spooler_controller_guid equals the GUID of your replaced SPOC (see step 4.c), then update the network_address value to match the new IP.

9. Edit <instal_dir>\SPOC\conf\modules\guid.conf (e.g. c:\DispatcherParagon\SPOC\conf\modules\guid.conf) and rewrite the localGUID to the value that was used before (see step 4.c.).

10. Delete the SPOC cache by deleting the whole folder <install_dir>\SPOC\SpoolCache

11. Start Dispatcher Paragon services with an Automatic startup type again.

    Do not start the Dispatcher Paragon Spooler Controller Group Service service. It will be started by the Dispatcher Paragon Spooler Controller service when the proper configuration is ready.
    

    1. You can use the following PowerShell script to perform the task:

       Get-Service *YSoft* | Where-Object {$_.Name -ne 'YSoftSQ-SPOCGS'} | Start-Service

12. Re-activate your Dispatcher Paragon license using your preferred method (online/offline). See Management Interface - License Activation for detailed instructions.

13. If Dispatcher Paragon Payment System is installed on this server, update paymentSystemApiUrl.

    • In Dispatcher Paragon Print Management web, system update paymentSystemApiUrl to reflect the new IP address.

14. Restore customized configuration:

    1. If you had services running under a specific domain account, set it up again.

    2. If you used customized scripts on the server (e.g., for batch files launched by Rule-Based Engine or customized batch files used by Workflow Processing System), restore those scripts from the backup.

    3. If you used a customized configuration (such as your own certificates for the web services), locate the relevant documentation and set the configuration again.

15. Check that Spooler Controller is correctly connected on the management web.

An Environment with Two Management Servers in the Cluster

1. Make sure both existing servers (including the one that should be replaced by the other one with a new IP address) are functional.

2. If you have two node cluster, add a third node that is using the new IP address.

3. Then uninstall the node that is being replaced.

4. Edit <install_dir>\SPOC\conf\modules\spoc.conf on both remaining Management Servers

   1. Make sure the details about and correct IPs for both remaining nodes are stored in the properties: serverGUID1, serverPORT1, serverIP1, serverGUID2, serverPORT2, serverIP2

   2. Should details about any node (except the one which is going to be removed) be missing, add them.

5. Remove IP address of the uninstalled node from the database

   1. Connect to the SQDB6 database, cluster_mngmt schema and check the contents of the cluster_server table.

   2. Delete the record that contains ip_address and server_guid of the server that was uninstalled.

6. Restart the Dispatcher Paragon Management Service service on both Management Servers in the cluster.
   

7. If the reinstalled node was the one on which the Dispatcher Paragon license was activated, re-activate Dispatcher Paragon license using your preferred method (online/offline). See Management Interface - License Activation for detailed instructions.
   

8. If the reinstalled node also contained a SPOC:

   1. move the MFDs managed by the uninstalled SPOC to the SPOC with a new IP address (Dispatcher Paragon management interface -> Devices).

   2. delete the uninstalled SPOC from Dispatcher Paragon (Dispatcher Paragon management interface -> Devices -> Spoler Controller groups).

   3. if the old SPOC was member of a SPOC group, move the newly installed server to a SPOC group (Dispatcher Paragon management interface -> Devices -> Spooler Controller groups).

      • other necessary steps to fully initialize a SPOC group are described later in this guide.

An Environment with Three or More Management Servers in the Cluster