logo

Contact Us  |  Log In  |  Sign Up  |  Blog

 
MailSite Knowledge Base
Find answers and solutions to MailSite questions and problems
Upgrading to MailSite Fusion 9.5
Document #:10523

Applies To:
  • MailSite 9.5

Synopsis:

This document outlines the recommended steps when upgrading to MailSite 9.5. The document is designed to help system administrators plan MailSite server upgrades.

For customers running the SQL Connector on SQL 2000, please review the notes carefully below.

More Information:
The latest version of MailSite is available from the MailSite Customer Portal.

When upgrading from a previous version of MailSite the installer will overwrite current MailSite Express and MailSite ExpressPro files. Therefore any customizations/branding will need to be reapplied after upgrading.

For the Webmail related services, MailSite 9.5 requires IIS and the Microsoft.NET Framework 4.0 to be installed on the server beforehand. The ActiveSync server will be automatically installed if you elect to install 'MailSite ExpressPro, Calendar & AirSync Services' when running the 9.5 installer.

MailSite Express is no longer available by default in MailSite 9.4 and later. MailSite ExpressPro is now the default client shipped with the MailSite installer. For existing customers still needing Express, please open a support ticket with Technical Support.



Registry Connector


If you are using the Registry Connector (typically customers with SE & LE keys) then you should:
  1. Back up your current accounts & settings. This can be done using the MSBACK tool*.
  2. Backup any Express, ExpressPro or Web Console customizations.
  3. If you are running MailSite 4.x, 5.x, 6.x**, 7.x, 8.x or a previous version of V9, then you can simply run the 9.x installer and it will upgrade your server. Any Express, ExpressPro or Web Console customizations will be overwritten and must be reapplied.
  4. For customers running webmail, it is recommended that the option to 'Overwrite virtual directory if it exists' is unselected during the installation. This will avoid the IIS settings/anonymous user from being reset.
  5. After the installation is complete, apply any hotfixes. Hotfix rollup packages are available from the Download section of the MailSite website. If there is no download package for hotfixes then check the following FTP site: ftp://ftp.rockliffe.com/mailsite/latest/hotfixes. (paste link into Windows Explorer)
  6. Restart the MailSite services and ensure you can send and receive mail.
  7. Reapply any Express and ExpressPro customizations.

*The backup file created from MSBACK is only required should you need to roll back during the upgrade.
**Customers running MailSite 6.0.6 will need to upgrade to MailSite 6.0.11 first and then upgrade to 9.x. MailSite 6.0.11 is available from ftp://ftp.mailsite.com/mailsite/6.0.11/

SQL Connector



With the release of MailSite 9.5, support for Microsoft SQL Server 2000 has been removed from the standard SQL procedures. Customers running SQL server 2000 should download the MailSite SQL 2000 Tables and Procedures Upgrade Scripts , apply these to the MailSite database, then upgrade. Steps 6 and 7 do not apply if you update the tables and procedures prior to installing/upgrading MailSite. We recommend customers consider upgrading SQL Server to 2005, 2008 or later.

The general upgrading steps are:
  1. Back up your SQL Database
  2. Back up any customizations to Express, ExpressPro and the Web console. These customizations will need to be reapplied to MailSite V9.
  3. Stop the MailSite services on the node you are upgrading. If you plan to refresh the stored procedures and tables then you should stop the services on ALL nodes at that time.
  4. If you are running MailSite 4.x, 5.x, 6.x, 7.x, 8.x or a previous version of V9, then you can simply run the 9.x installer.
  5. For customers running webmail, it is recommended that the option to 'overwrite virtual directory if it exists' is unselected during the installation. This will avoid the IIS settings/anonymous user from being reset.
  6. During the installation de-select the option to automatically start the MailSite Services. Apply any hotfix rollup packages after the installer completes. Hotfix rollup packages are available from the Download section of the MailSite website. If there is no download package for hotfixes then check the following FTP site: ftp://ftp.rockliffe.com/mailsite/latest/hotfixes. (paste link into Windows Explorer)
  7. After installation is complete open up the MailSite Console and navigate to the "SQL Connector" option under "Server". Run though the wizard and select to refresh the stored procedures. This will update your Database to the version 9 Tables and Stored Procedures.
  8. You can bypass step 7 and use MS SQL Query Analyzer to manually refresh the stored procedures and tables. These files are located in the MailSite directory tables.sql & procedures.sql. (Tables should be run first, followed by Procedures).
  9. Start the MailSite services and ensure you can send and receive mail.
  10. If you have more than one node you can continue to upgrade those servers. This can be done without interrupting the service (MailSite 8 engine can run against the MailSite 9 database).
  11. Reapply any Express or ExpressPro customizations.


Additional Information on Permissions


If the message store (commonly known as the BOX directory) is located within the MailSite directory and the size of the BOX directory is in the GB size range then there may be a delay caused when the installer attempts to write the permissions to the MailSite installation directory. In MailSite 6.1.2x and later you will be given a prompt as to whether you want the installer to silently set the permissions or if you wish to do this manually. If your BOX directory is located somewhere other than the default then you will need to set the permissions manually (if any change is required). If you have already had MailSite running previously then most customers will not need to change any permissions on the BOX.

See the related knowledge base articles below for recommended permissions.

Related:
See these other knowledge base documents:
Last revised 2013-6-3

Products  |  Features  |  Support  |  Resources  |  Partners  |  Site Map  |  FAQ  |  Privacy  |  Contact Us