Upgrade from 2.x

In the upgrading process, steps differ between Linux and Windows systems. Quickly navigate to your preferred section:

Windows

The greatest part of MailScheduler 3.x is that it has a built-in webserver. In other words, it does not need to have IIS or XAMPP for serving the application anymore.

This guide will explain how to transfer configuration to the new MailScheduler 3.0 application and how to disable/remove the current webserver to be able to reuse the system ports.

The upgrade setup of MailScheduler 3.x requires the following information:

  • The .env file of your current installation.

  • The LICENSE file (downloaded from our portal or copied from your current installation)

  • The URL and port that is used by the current installation.

  • The SSL Certificate (in .pfx or .crt & .key format) that applies to the aforementioned URL

In this guide, we will extract this information from the current installation.

Lets get started!

  1. Create a backup of the installation directory of MailScheduler.

You will need the .env and LICENSE files that are in there for the new installation.

Your current version of MailScheduler can be served by either XAMPP or IIS. Follow the steps for your type of installation in the appropriate section below.

Internet Information Services (IIS)

We need to do 3 things:

  • Export SSL Certificate

  • Retrieve the URL and port

  • Stop IIS

Export SSL Certificate

The first step is to locate and export the SSL Certificate. Note that it is only possible to export the SSL certificate when it was marked as `Exportable` while it was imported in the past. When the certificate is not exportable, you need to get the original certificate from your IT Department.

  1. Open the Internet Information Services (IIS) Manager. You can usually find it by searching for “IIS” in the Start menu.

  2. In the left-hand pane of the IIS Manager, click on the server node

  3. In the middle pane, double-click on the `Server certificates` icon.

  4. Right-click the certificate that is valid for the URL of your MailScheduler instance

  5. Select `Export` from the context menu.

  6. Export to Desktop and set a password. You will need this password in the MailScheduler 3.0 installation.

Retrieve URL and Port

The second step is retrieving the URL and port number that is configured for MailScheduler:

Stopping the Webserver

The third step is about unlocking the port that is being used by IIS so the new MailScheduler application can run on the same port.

When MailScheduler is one of multiple sites served by IIS you can simply stop the website by right-clicking on the MailScheduler site in the left pane and select `Manage Website` -> `Stop`.

When MailScheduler is the only site that is configured in IIS we can safely stop IIS completely:

  1. In the left pane, Right-click on the server node (the root node)

  2. Select Stop from the context menu.

  3. We should now remove IIS as a service to prevent it from being started automatically on system startup:

    • Open the start menu and type ‘Services’.

    • Open the Services app.

    • Search for `World Wide Web Publishing Service`

    • Right-click on it and select Properties from the context menu.

    • Set the startup type to `Disabled`. Then press OK.

XAMPP

  1. Open the vhosts file of your XAMPP configuration. The file is typically located at C:\XAMPP\apache\conf\extra\httpd-vhosts.conf

    • From this file, you’ll need to find the location of the SSL certificates of this domain. (search on SSLCertificateFile to find it easily)

    • When MailScheduler is not the only site served by Apache2, you need to remove the whole block of the MailScheduler site.

  2. Open the XAMPP control panel as an administrator

    • Stop Apache2 as a service

  3. When the repository database of MailScheduler is MySQL you still need XAMPP to keep that database running. In that case, you can simply stop the Apache process by opening the XAMPP Control panel and stop Apache manually. Do not forget to stop the service as well.

    • When the repository database of MailScheduler is NOT MySQL, you can remove XAMPP from your system. This will make the ports available for the new MailScheduler 3.0 installation

When MailScheduler is NOT the only site that is served by XAMPP, you’ll need to change the DNS of the MailScheduler domain to use another port than 443 or 80 since that is still in use by XAMPP.

Upgrading through Installer

After stopping the old MailScheduler you can launch the new 4.x Installer by double-clicking the application. On the first screen, select Upgrade from 2.x? the link.

This page allows you to upload the .env file of the old installation. After uploading the application starts the installation process. You will see that step 3 (database Setup) and step 4 (User creation) can be skipped.

Linux

The greatest part of MailScheduler 3.x is that it has a built-in webserver. In other words, it does not need to have Nginx or LAMPP for serving the application anymore.

This guide will explain how to transfer configuration to the new MailScheduler 3.x application and how to disable/remove the current webserver to be able to reuse the system ports.

The upgrade setup of MailScheduler 3.x requires the following information:

  • The .env file of your current installation.

  • The LICENSE file (downloaded from our portal or copied from your current installation)

  • The URL and port that is used by the current installation.

  • The SSL Certificate (in .pfx or .crt & .key format) that is applicable to the forementioned URL

In this guide we will extract this information from the current installation.

Lets get started!

  1. Create a backup of the installation directory of MailScheduler and database.

  2. Stop the Nginx or Apache service, so MailScheduler is no longer running.

  3. Disable the Nginx and Apache services so they don’t restart after reboot.

  4. Copy the files above to a safe location.

  5. Start the installation procedure from stap 1 in this installation guide.

  6. You will need the .env and LICENSE files that are in there for the new installation.

PS: When MailScheduler is NOT the only site that is served by Nginx or Apache, you’ll need to change the DNS of the MailScheduler domain to use another port than 443 or 80 since that is still in use by Nginx or Apache.

Last updated