Upgrading tips for Mission Control - Upgrade your Genetec Mission Control™ environment based on your deployment architecture. - Mission Control 3.3.0.0 | Mission Control Web API 2.13

Genetec Mission Control™ Release Notes 3.3.0.0
Product
Mission Control
Content type
Release notes
Version
3.3
Release
3.3.0.0
ft:locale
en-US
Last updated
2025-06-13

Upgrade your Genetec Mission Control™ environment based on your deployment architecture.

Before you begin

Get the latest build of Mission Control. For information on how to get the package, see Installing Mission Control 3.3.0.0..

What you should know

It’s recommended you upgrade RabbitMQ to the version available with the installer package.

Procedure

  1. Upgrade the Directory server.
  2. Upgrade any failover Security Center Directory servers.
  3. Upgrade the Mission Control server.
    NOTE: This process upgrades Mission Control, Genetec Mission Control Web API, the Incident Manager database and RabbitMQ if it is on the same server as Mission Control.
  4. Upgrade any failover Mission Control servers.
  5. Validate the existing RabbitMQ configuration setup.
  6. If you have RabbitMQ on one or more standalone machines, upgrade the RabbitMQ nodes:
    1. Deactivate the Incident Manager role:
      1. Select System > Roles > Incident Manager.
      2. Right-click the Incident Manager role to select Maintenance > Deactivate role.
    2. Upgrade your RabbitMQ configuration.
  7. If the server isn’t back online, start the Genetec™ Server service on the Directory server.
  8. If the server isn’t back online, start the Genetec™ Server service on the Mission Control server.
  9. Upgrade all Mission Control workstations.
    You have successfully upgraded your Mission Control environments.
    Best Practice: Verify that all your documents have been migrated to the SQL Server before you uninstall MongoDB from your system.