WinDeveloper Software
Innovation. The seed to our Solutions
Follow us on Twitter WinDeveloper on Facebook WinDeveloper YouTube Channel WinDeveloper Updates
HomeDownloadOrderSupportPartnersCompanyContact
IMF Tune - Bringing Back the Exchange Connection Filter
IMF Tune - Bringing Back the Exchange Connection Filter

Upgrading/Migrating to IMF Tune v5.6

This article discusses various upgrade/migration scenarios you may encounter when deploying IMF Tune v5.6. In both Upgrades and Migrations our primary goal is that of retaining the configuration settings of the old IMF Tune installation.

Upgrade - Installing the latest IMF Tune version on a machine that is currently running an earlier IMF Tune version.

Migration - Transferring an IMF Tune installation to new hardware.

IMF Tune v5.6 is made up of two components:

  1. IMF Tune Server for Exchange 2003, 2007 and 2010
  2. IMF Tune Moderator/Reporting Web Interface

The Web interface component is optional. In fact IMF Tune can be run without it ever being installed, but of course we would be missing all the functionality this interface delivers.

More importantly, when upgrading/migrating we are able to first focus exclusively on the IMF Tune server component. Completing the IMF Tune server upgrade, the core filtering functionality is immediately available. The Web component installation may then be completed without causing any disruption.

 

General Considerations

The Moderator/Reporting Web Component was first introduced in IMF Tune v5.5. If you are currently running IMF Tune v5.0 or earlier, or if running IMF Tune v5.5 without the Web Component, a complete upgrade involves:

  1. Upgrade/Migrate the IMF Tune Server
  2. Fresh installation of the Web Component

On the other hand if you are currently running IMF Tune v5.5 together with the Web Component upgrading involves:

  1. Upgrade/Migrate the IMF Tune Server
  2. Upgrade/Migrate the Web Component

In this document we only discuss upgrading/migrating. If installing the Web component for the first time please also refer to Installing IMF Tune Moderator/Reporting.

 

Upgrade/Migrate the IMF Tune Server

Upgrading to IMF Tune server v5.6 may involve an in-place upgrade or a move to new server hardware. This is especially true because IMF Tune v5.6 supports all of Exchange 2003, 2007 and 2010. Since Exchange version upgrades require migration to new hardware, IMF Tune needs to move along whenever Exchange is upgraded.

 

1. In-Place Upgrade from IMF Tune v2.x/v3.x

When installing IMF Tune v5.6 on a machine where IMF Tune v2.x/v3.x is already installed, follow these steps in order to retain your current configuration settings.

  1. From the Control Panel Add/Remove Programs applet, uninstall the current IMF Tune build.
  2. Restart the IIS Admin service.
  3. Install the latest build to the same disk location where the previous build was installed. IMF Tune will automatically adopt the configuration of the previous installation.

 

2. In-Place Upgrade from IMF Tune v4.x/v5.x

When upgrading from earlier IMF Tune v4/v5 builds, start by downloading the latest IMF Tune v5.6 build from the WinDeveloper Software site. Run the installation on the machine where IMF Tune v4/v5 is currently installed. The setup will automatically detect the installed build and guide you through the upgrade procedure.

 

3. Moving any IMF Tune version to IMF Tune v5.6 on a New Machine

When moving IMF Tune to a new machine we have two options for preserving the configuration settings. The first option is that of moving the configuration files manually and then let the installation do any upgrading. The second involves performing a configuration backup on the old server and a restore on the new machine.

 

3.1. Manually Moving Settings

This method is very useful since it only requires the availability of the IMF Tune configuration files from the old IMF Tune server machine. In case of disaster recovery, all we need is access to the HDD of the machine being replaced.

Note: The IMF Tune Un-Installation does not delete the configuration settings. Thus you can still follow this procedure as long as you did not manually delete the IMF Tune application directory.

IMF Tune v5.6 will automatically upgrade the configuration settings of earlier releases when found on the local machine at installation time. To benefit from this automatic upgrade we need to first move the configuration of earlier IMF Tune versions to the new machine as follows:

  1. If IMF Tune v5.6 was already installed on the new destination machine, uninstall this and delete the IMF Tune application directory.

  2. On the destination machine create the following directory:
    <Program Files>\WinDeveloper IMF Tune

  3. On the source machine running the old IMF Tune server locate the following directories:
    <Source Machine IMF Tune dir.>\config
    <Source Machine IMF Tune dir.>\configv3
    <Source Machine IMF Tune dir.>\configv4
    <Source Machine IMF Tune dir.>\configv5

    NOTE: Depending on your IMF Tune installation history some of these directories may not be present.

  4. Copy these directories and all files within them to the destination machine under:
    <Program Files>\WinDeveloper IMF Tune

  5. On the destination machine install IMF Tune v5.6 to:
    <Program Files>\WinDeveloper IMF Tune

 

3.2 Moving Settings with a Backup-Restore Cycle

This method can be employed if the old IMF Tune server is still up and running. In this case we rely on the Backup/Restore Wizard included with IMF Tune v5.6. Here are the steps:

  1. Upgrade the old IMF Tune server to version 5.6. Here, depending on your old IMF Tune version, follow the relevant procedure: In-Place Upgrade from IMF Tune v2.x/v3.x or In-Place Upgrade from IMF Tune v4.x/v5.x.

    Note: The Backup/Restore wizard will still work even if we don't license the server being decommissioned.

  2. On the old IMF Tune server machine, from the IMF Tune application program group, run the Backup/Restore wizard. Select the Backup option and follow the wizard steps to create a configuration backup (*.ibak) file.

  3. If you didn't do so already, install IMF Tune v5.6 on the new server machine.

  4. Transfer the configuration backup file created in step 2 to the new server.

  5. On the new server run the Backup/Restore Wizard in Restore mode. Just make sure to:

    • Select the *.ibak backup file at the Restore Source step
    • Select 'Restore all settings' at the Restore Items step
    • Select 'Automatically adjust file paths if replicating settings across servers' at the Restore Options step

Note: The Backup/Restore Wizard can only be used when moving configurations across IMF Tune installations running the same version.

 

Upgrade/Migrate the Web Component

Since the Moderator/Reporting Web Component was first introduced in IMF Tune v5.5, this section is not relevant to those running earlier IMF Tune versions. Likewise it is not relevant to users running IMF Tune v5.5 without the Web Component. In these cases to start using the Web Component check Installing IMF Tune Moderator/Reporting.

Version 5.6 does not introduce any major changes over the Version 5.5 Web Component. Most changes are related to Sender Auto-Whitelisting Reporting. For this reason it is possible to run the IMF Tune v5.5 Web Component together with the IMF Tune v5.6 server. At worst you may see some strange entries under the Reporting section. However you won't experience any significant loss in functionality.

Upgrading the Web Component simply involves updating the IIS ASP.NET application interface. To do that, just run the v5.6 Web Component installation on the same machine where it is currently running.

If you would like to move the Web Component to new hardware, simply uninstall the Web Component from its current machine and install it on the new machine. When at the end of the installation the database connection wizard is launched, make sure to connect to the SQL Database that was in use by the previous installation.

 

Privacy Policy Partners About Us Contact

Copyright © 2004 - 2024 WinDeveloper Software Ltd. All rights reserved.