Upgrading

The following section outlines the steps that should be taken to successfully upgrade MCS to a later version.

Apply license upgrades and Make a note of license details
Perform Database Maintenance (including backups)
Run the upgrade installation

Applying License Updates

If the version number of MCS is being upgraded then it is important to apply licenses updates before the software is upgraded. This ensures that the license is available and that SWAS is correctly in place before doing any work and will minimize the risk of having to perform a rollback.

A version number upgrade applies to major and minor version of software but not revisions. For example:

4.2 to 4.3 or 4.3 to 5.0 would constitute as a version upgrade.

4.3.1 to 4.3.2 would not constitute as a version upgrade and no license update would be required.

Once any license update has been applied, make a note of the Site ID and Serial number of the solution and the current version that is running. The Site ID and Serial Number can be found on the Server License section of the website. The Site ID and Serial number would be required to re-license the solution if any problems occur with the upgrade. The version number that is running can be found by hovering the mouse of the Mitel icon in the top left hand corner of the MCS website.

Database Maintenance & Backup

Before performing any sort of upgrade it is important that full backups of the solution are taken so that the software can be rolled back to a previous version or restored to another server if required.

Before performing a backup, it is good practice to perform an 'Archive Now' under the Database Maintenance section. This will make sure all call data has been moved to the archive databases.

Once this has been completed, the Backup process can be followed.

Running the Upgrade

When upgrading MCS, it is important to note that the installer will stop all services and all functions of the solution will stop working.

Installation notes:

There is no need to uninstall a previous version of MCS first, the installation can be run over the top.
When running the installation, right click on the file and select 'Run as administrator'
When running the installation, ensure the file is run from the local server and not from a network share.

When running the installation, following the instructions on screen. Once the installation has finished the Watchdog service will automatically be started. The watchdog service will then update the database schema for the solution, this can take some time to complete depending on the size of the MCS databases.

Once the database update process has been completed then the watchdog will restart all the appropriate MCS services and the solution should be operational again.

If for any reason the upgrade fails then the Rollback process can be followed to return the system to it's previous state.

The system will go offline during the upgrade process, no data or call audio will be recorded during this time. It is advised that this process is completed outside of normal operating hours for the system.

Detached Databases

If for some reason the SQL Instance has been removed and re-installed by the MCS setup process then a situation can occur where the setup cannot complete because it cannot create the required databases due to the fact that they already exist on the hard drive.

This occurs because the database was automatically detached when the SQL instance was uninstalled.

The following 'Error 27552' will be seen:

If this occurs then there are two options available to continue installation:

Reattach Database Files

This method will keep any existing data from a previous MCS installation. Exit the installation and start the 'SQL Management Studio' application. Connect to the SQL instance '127.0.0.1\MCS' using windows authentication.

Right click on the 'Databases' menu item and select 'Attach' from the menu. On the form that loads, press the 'Add' button and add all CallRecorder & CampaignManager .mdf files found in the following location:

C:\Program Files\Microsoft SQL Server\MSSQL12.MCS\MSSQL\DATA

Re-run the installation process, the install should now be able to see the existing databases and will be able to complete.

If there is a permission issue when attempting to re-attach databases, ensure you are logged into the server with the same windows credentials the software was installed with.

Move/Delete Existing Database Files

This method will allow the installation to create new databases when next run. Browse to the location below and move all CallRecorder/CampaignManager .mdf & .idf files to another location. It is recommended the files are moved and not deleted to reduce the risk of data loss.

C:\Program Files\Microsoft SQL Server\MSSQL12.MCS\MSSQL\DATA

Re-run the installation process.