Here you will find how to update a UMS installation under Windows or Linux.
Update instructions for the UMS High Availability (HA) installation can be found under Updating the Installation of an HA Network.
Before the installation, check that your hardware and software fulfill the installation requirements. See also Devices Supported by IGEL Universal Management Suite.
We recommend that you install the new version of the UMS on a test system before installing it on the productive system. Once you have checked the functions of the new version on the test system, you can install the new version on the productive system. This also applies to hotfixes, patches etc. for the server system and database.
Installing a version of the UMS which is older than the one currently used is only possible if you have a backup of the database with the corresponding older schema. You can only switch from an older database schema to a newer one, not the other way around. You should therefore create a backup of your existing system before you start the update.
Since the version of the database schema always corresponds to the current major.minor version of the UMS (i.e. 6.10 for all 6.10.x releases, 6.08 for all 6.08.x. releases), the downgrades are only possible within a major.minor version. Example: you can downgrade from 6.10.140 to 6.10.120, but not from 6.10.140 to 6.09.120.
If the version of the UMS Console is older than the version of the UMS Server, you will not be able to establish a connection to the UMS Server (
Unable to load tree error message). In this case, you will need to update the installation of the UMS Console.
If you use an older version of the IGEL Remote Manager with SAP DB, we recommend that you switch to the embedded database before updating the UMS. For a more detailed description of this switch, please contact IGEL Support.
ums_filetransfer or subdirectories created in it for WebDAV downloads. The installer offers you the option of moving existing directories to this new default folder.
During a UMS upgrade, e.g. from 6.06 to 6.07, the database schema is changed by the installer. With large production databases, this process can last up to 2 hours. Do not abort the installation during this time.