Overview

This article provides the methods of migrating FaxMaker from one server to another without losing its configuration settings.  

Diagnosis

When server hardware or operating system has to be upgrade it may be necessary to move the FaxMaker installation to a new Windows Server and upgrade to the latest version when doing so.  

Prerequisites 

• The upgrade is not reversible, so you cannot downgrade to the last version.
• GFI FaxMaker 20 works with a subscription model, where after the subscription expires, the product stops sending faxes and SMS. A renewal of the subscription is required to resume the service.  See the post license expiration grace period article for applicable grace periods when the subscription expires.  
• GFI FaxMaker 19.2 and later only support 64-bit installations. It is not possible to upgrade over a 32-bit instance, and a new installation in a supported environment is required. For more information, refer to Migrating GFI FaxMaker article.
  
• GFI FaxMaker 2015 introduces GFI Directory as a new user management system when Active Directory is not available. When upgrading over an installation without Active Directory, run the Configuration Wizard after the installation to automatically install and import all users to GFI Directory.  Installing FaxMaker in SMTP mode is no longer an option that is usable.  
• When upgrading over an installation that uses a Microsoft Access archive database, GFI FaxMaker migrates archive data to a Firebird database. When using a Microsoft^® SQL/MSDE database, GFI FaxMaker upgrades the database schema. These database changes are automatically done in the background separate from the installation. It is recommended to take a backup of the database before starting the upgrade. This backup may be useful to re-import the database if the upgrade fails.
• When upgrading to a new major release, you also need to upgrade your license key. 

Solution

There are two methods for migrating FaxMaker to another server.  Both methods require running the installer and following the installation article.  Both methods also require retaining the original configuration and your choice will depend on if any possible downtime is allowed and the version from which you are upgrading.

Method #1

Method 1 involves upgrading the server in place and moving the configuration files to the new server and installing there.  This method is generally the least favored due to it requires upgrading a production server.  This could cause possible down time if something were to go awry during the upgrade.  

At other times this method is mandatory, as with method 2, the current version is required to be installed on the new server.  When one uses version 17, released in 2014 and wishes to upgrade to version 20 and migrate to a Windows Server 2016.  Since version 17 does not support this server version, an in place upgrade is required.  

1. Upgrade the GFI FaxMaker to the latest version on the current server.  Please see the upgrading FaxMaker article for further instructions.  
2. Migrate GFI Directory (if applicable). Review the moving GFI Directory user list article. 
3. Copy the old configuration files. See the backup FaxMaker configuration article. 
4. Move configuration files. Copy the configuration files to the FaxMaker directory on the new server.  This directory will not yet exist so it will need to be created.  C:\Program Files (X86)\GFI\Faxmaker
5. Install GFI Faxmaker.  See the installing FaxMaker article. followed by the FaxMaker Configuration Wizard article.   
6. Reconfigure mail server connectors.  
7. Update/verify feature settings.  These would be any setting to your specific installation in the FaxMaker Configuration.  Your routing rules or if there is a prefix set for each line, for example.  
8. Test the new faxing setup.  See Confirmation.  

Method #2

Many customers do not like to perform an upgrade on their production servers (as mentioned in method #1). Most prefer to move the existing data (FaxMaker folder) to the new server and install the currently running version of FaxMaker on the new server. 

Once the installation is complete on the new server, the customer will upgrade the GFI Faxmaker to the latest version, leaving the production server to operate without interruption.

In such cases, follow the steps below to migrate FaxMaker.

1. Copy the old configuration files (FaxMaker folder) to the new server in this location C:\Program Files (X86)\GFI\Faxmaker and for the safety of data, copy it to a backup location as well.
2. Migrate GFI Directory (if applicable).  Review the moving GFI Directory user list article. 
3. Install GFI FaxMaker, the same version that is on the production server.  See the installing FaxMaker article.
4. Upgrade the new server to the latest version of GFI Faxmaker.  Please see the upgrading FaxMaker article for further instructions.  
5. Reconfigure mail server connectors. 
6. Update/verify feature settings.  These would be any setting to your specific installation in the FaxMaker Configuration.  Your routing rules or if there is a prefix set for each line, for example.  
7. Test the new faxing setup. See Confirmation.  

Confirmation

Once the configuration is in place and the services have been restarted test using your normal sending method and monitor via the FaxMaker Monitor.

• Go to the GFI FaxMaker Monitor and ensure that fax lines are present and initialized.
  
  
  • Select Start > Programs > GFI FaxMaker Web Interface
    
    
  • Login to the FaxMaker Web Interface
    
    
  • Select the Monitor tab and verify lines are in place and initialized.  
    
    
• Test the functionality of GFI FaxMaker by sending and receiving test fax.