This article describes a step-by-step procedure to manually switch from a High Availability IGEL Universal Management Suite (UMS) to a Distributed UMS installation. You can find the procedure for Windows and for Linux.


Before the migration, learn about the differences between High Availability UMS and Distributed UMS under IGEL UMS Installation.

The migration procedure consists of the following tasks:

  1. Removal of some objects from the current installation which indicate High Availability to the installer, like UMS Watchdog, Load Balancer, and config file for ActiveMQ.
  2. Normal installation or upgrade workflow with downtime. For details, see Updating HA Installation: With Downtime of the Servers (igel.com).
  3. Validation of the installation.

Switch the Installation on Windows

Before the switch, create a backup of the database and create backups of all the servers.

To switch the installation, you need to perform the following steps. All the steps must be executed with Administrator privileges:

  1. Stop the UMS Server service on all servers.

  2. Choose one server and perform the following:

    1. Go to the installation folder of the UMS.

    2. Stop the Windows Services for the Load Balancer and the Watchdog.

    3. Execute the following commands in the Windows command shell:
      • umswatchdog\etc\bin\jsl.exe -remove
      • umsbroker\etc\bin\jsl.exe -remove

        Both Windows Services should now be removed from the Windows Services.

    4. Delete the folders umswatchdog and umsbroker from the installation home directory.

    5. Delete the file rmguiserver\conf\IAMQ_info_storage.xml.

    6. Reinstall the current UMS version or upgrade the UMS.

    7. You should get the possibility to choose Distributed UMS in the selection dialog of the installation. Choose Distributed UMS and finish the installation.

    8. Verify in the UMS Administrator that the Device Communication Port is set to 30001.

    9. Open the UMS Console, navigate to Server Network Settings and verify that Distributed UMS is selected.

  3. Execute step 2 for the remaining servers. This can be done in parallel.

  4. Delete existing UMS Load Balancers which are installed on other servers where no UMS Server is installed.

  5. Update load balancing configurations if they are using UMS Load Balancer addresses.

Switch the Installation on Linux

Before the switch, create a backup of the database and create backups of all the servers.


To switch the installation, you need to perform the following steps. All steps must be executed with Administrator privileges. We omit sudo in the following description:

  1. Stop the UMS Server service on all servers.

  2. Choose one server and perform the following:

    1. Go to the installation folder of the UMS.

    2. Stop the Windows Services for the Load Balancer and the Watchdog:
      • systemctl stop igel-ums-broker.service
      • systemctl disable igel-ums-broker.service
      • rm /etc/systemd/system/igel-ums-broker.service
      • systemctl stop igel-ums-watchdog.service
      • systemctl disable igel-ums- watchdog.service
      • rm /etc/systemd/system/igel-ums- watchdog.service

    3. Delete the folders umswatchdog and umsbroker from the installation home directory.

    4. Delete the file rmguiserver/conf/IAMQ_info_storage.xml.

    5. Reinstall the current UMS version or upgrade UMS.

    6. You should get the possibility to choose Distributed UMS in the selection dialog of the installation. Choose Distributed UMS and finish the installation.

    7. Verify in the UMS Administrator that the Device Communication Port is set to 30001.

    8. Open the UMS Console, navigate to Server Network Settings and verify that Distributed UMS is selected.

  3. Execute step 2 for the remaining servers. This can be done in parallel.

  4. Delete existing UMS Load Balancers which are installed on other servers where no UMS Server is installed.

  5. Update load balancing configurations if they are using UMS Load Balancer addresses.

Final Steps - Validation

To validate the Distributed UMS installation you can do the following:

  • Test the communication to some devices.
  • Check if IGEL Cloud Gateway (ICG) is still connected to all UMS Servers.
  • Create a ‘Save Support Information’ archive. The archive should contain log files from all UMS Servers.
  • Perform other checks that you do after an upgrade of UMS.