How to upgrade to the latest version DC2

Please follow the steps below to upgrade your server to the latest version.

Windows version - Upgrade from v12.2 to DC2 on Windows Server 2012+

1. Run the daily server backup procedure (configuration and databases).
2. Download a new version installation package from here. (please note that upgrading to EPOS requires upgrading first to v 13.0, then to v13.0.3.10 and finally to v14.x)
3. Stop the previous IceWarp Server. Although the installer allows to kill the server, it is always better to stop it manually (and wait till it is done).
4. Run the installer (.exe file).
5. Follow the screen instructions, they are very similar to a fresh installation. When asked, choose to upgrade.
6. In the end, you will be asked whether you want to run upgrade procedures. Answer YES in this case. You can also run upgrade procedures later for some reason. Do not use the newly installed server before upgrade procedures are finished.

Linux version - Upgrade from v12.2 to DC2 on CentOS 7+

1. Run the daily server backup procedure (config, calendar, spam, including the dump of all seven databases).
2. Download a new version installation package from here. (please note that upgrading to EPOS requires upgrading first to v 13.0, then to v13.0.3.10 and finally to v14.x)
3. Unpack a new version installation package (tar xvyf <archive name>).
4. Stop IceWarp Server services. Although the installer allows killing the server, it is always better to stop it manually (and wait till it is done).

5. Turn off the Watchdog if it's enabled.

6. Shut down the Icewarp server via /opt/icewarp/icewarpd.sh --stop

7. Run the install.sh file from the unpacked installation package.
8. Follow the screen instructions, they are very similar to a fresh installation. When asked, choose to upgrade.
9. In the end, you will be asked whether you want to run upgrade procedures. Answer YES in this case. You can also run upgrade procedures later for some reason. Do not use the newly installed server before upgrade procedures are finished.
(you can also run the install.sh in automatic mode with -a parameter, then you can skip steps 6 and 7)

10. When the installer finishes, check logs and if services are running, also briefly check basic functions in Webclient.