Upgrading a customized installation of MailSite Express
Document ID: 10148
Synopsis
When upgrading MailSite Express, the installer overwrites all files. Restoring the customization can be expedited by following the procedure outlined below.
More Information
When upgrading MailSite Express, the installer overwrites all files. Restoring the customization can be expedited by following the procedure outlined below.
In this example, we shall store the Express pages in a non-default directory (eg. not MailSite\Express), with IIS pointing to this directory. The permissions on this directory should allow the user that the MailSite services are running under to have full access. An example directory would be: D:\web\iis\express523Before upgrading, a copy should be made of the Express directory, and renamed to reflect the version number. For example, D:\web\iis\express523 should be copied to D:\web\iis\express524
Once MailSite has been upgraded, all pages that cannot be customized, such as imap.asp, can be copied to the newly created directory (D:\web\iis\express524). This is in addition to the language files. The graphic files can also be overwritten if they have not been altered.
At this stage, all customized files are left in place. Those files are:
- default.asp
- loginerror.asp
- expresscfg.asp
- express.asp
- side.asp
- top.asp
- stylecfg.asp
- localcfg.asp
- compare the old and new pages line by line to find out which part(s) have changed. The login page (default.asp) is normally the hardest to modify this way
- find the page that is not working, overwrite it with the new version, and perform the customization again on the new page