Upgrade MSPControl

Use this procedure to upgrade any MSPControl 3.0 or 3.1 installation to the latest available MSPControl 3.1 build.

Keep every component on the same build

Portal, Enterprise Server, Servers, and Scheduler must all run the same MSPControl version after the upgrade. Do not leave a production environment with mixed component versions.

Before you upgrade

1. Identify every installed MSPControl component. Record the current versions of Portal, Enterprise Server, Servers, and Scheduler.
2. Back up the MSPControl database. MSPControl uses one database. Create a complete, restorable backup before changing any component.
3. Back up the component folders. Preserve the installed MSPControl folders on disk, including their configuration files.
4. Keep the backups together. The database backup and component-folder backup must represent the same pre-upgrade installation state.

Upgrade to the latest 3.1 build

1. Run the current MSPControl 3.1 upgrade package. Upgrade every installed MSPControl component.

2. Allow the installer to update the database. MSPControl applies the database migrations required by the target build automatically. Individual internal migration scripts are not part of the administrator procedure.

3. Confirm component versions. Portal, Enterprise Server, Servers, and Scheduler must report the same final 3.1 build.

4. Reset IIS. After all components have been upgraded successfully, run:

   iisreset

5. Verify the installation. Sign in to the Portal, confirm communication with Enterprise Server and managed Servers, and verify that Scheduler operations run normally.

License and Windows Agent compatibility

• The MSPControl license is not tied to a specific MSPControl version and remains in place during the upgrade.
• Existing Windows Agents remain compatible after the server-side upgrade.
• Update the agents when a newer build is available so that endpoints receive product fixes and important security updates.

Roll back

If the upgraded installation must be reverted, restore the database and component folders from the matching pre-upgrade backup set:

1. Stop IIS. Run iisreset /stop.
2. Restore the MSPControl database. Use the complete pre-upgrade database backup.
3. Restore the component folders. Restore the matching Portal, Enterprise Server, Server, and Scheduler folders on disk.
4. Start IIS. Run iisreset /start.
5. Verify the restored installation. Confirm that all components report the same restored version and that the Portal, Enterprise Server, Servers, Scheduler, license, and agents operate normally.

Do not restore a database and component folders from different points in time.