To upgrade your Security Center system to a collaborative decision management system,
you must install Genetec Mission Control™ on all Security Center servers hosting the Incident
Manager role on all Security Center client workstations.
Before you begin
- Read the most recent version of the release notes known issues, supported
upgrade paths, system requirements, and other information about the release.
- Close all applications related to Microsoft Management Console (MMC), such as Services,
Event Viewer, and so on. They might lock the Security Center services and prevent them from being
updated.
- Install a supported version of Security Center
before installing Mission Control.
IMPORTANT: Install the same version of Mission Control on all Security Center
servers that need to host the Incident Manager role.
Procedure
(Required for isolated systems) Disable Windows automatic root certificate
updates:
NOTE: This procedure is required for all systems where the
Directory isn’t connected to the internet and also on all computers running a Directory
role.
-
Open Command Prompt as an administrator and run gpedit.msc.
-
Go to .
-
Set Turn off automatic root certificate update to
Enabled and click
Apply.

-
Go to .
The Certificate Path Validation Settings Properties
dialog
opens.
-
In the Network Retrieval tab select the Define these
policy settings checkbox.
-
Deselect Automatically update certificates in the Microsoft Root Certificate
Program(recommended).
-
In the Default retrieval timeout settings section, set the
timeout values for Default URL retrieval timeout and
Default path validation cumulative retrieval timeout to 1 second
and click Apply.
-
Open Command Prompt as an administrator and run
gpupdate /force
. Click
Enter on your keyboard.
Download Mission Control 3.3.1.0:
-
Open the GTAP Product Download page.
You need a username and password to log on to GTAP.
-
From the Download Finder list, select your version of Security Center.
-
From the Mission Control section, download the required Mission Control installation package.
You can also get the Mission Control installation package from your representative of
Genetec™ Inc.
-
Extract the package and double-click setup.exe.
The Mission Control installer
launches.
Install Mission Control:
-
On the Choose Setup Language page, select English or French and
click Next.
-
On the Welcome to the InstallShield Wizard page, click the links
to read Mission Control documentation, and then
click Next.
-
On the License Agreement page, read the terms in the Genetec™ Software License Agreement, select
I accept the terms in the license agreement, and then click
Next.
-
On the Setup Type page, choose an installation setup:
- Typical
- This option installs Genetec Mission Control™, Mission Control Web API, Genetec
Document Service, and RabbitMQ on a Security Center server.
If only Security Center
Client is installed, selecting this option only installs Mission Control.
- Advanced
- This option opens the Custom Setup page, where you can choose to
install Mission Control, Genetec Document Service, or RabbitMQ individually.
- Mission Control WebAPI is installed by default starting from Mission Control
3.3.1.0.
IMPORTANT: If you choose to install
RabbitMQ, the latest version is installed.
For Advanced setup type:
-
Select the application that you want to install.
A custom setup is useful when you want to install one of the applications on another
server for high availability.
- Mission Control
- Installed on all servers that host the Incident Manager role on all client
workstations.
- Genetec™ Document Service
- Installed on all servers that host the Incident Manager role.
It’s required to
enable adding documents to an incident in Security Desk.
- RabbitMQ Server
- Can be installed on any server, not necessarily a Security Center server.
If
RabbitMQ is already installed on this machine for another product, clear this
option.
Tip: Don’t change the existing
RabbitMQ hostname.
NOTE: The option to Restart Genetec™ Server after
installation of selected applications is selected by default. If you clear this option,
you can manually restart the Genetec™ Server later.
-
Click Next.
RabbitMQ configuration page
-
Enter the credentials for the RabbitMQ server on the RabbitMQ
Configuration page:
- Username and Password
- Credentials used by the Incident Manager to connect to the RabbitMQ server.
- Port to use for secure connection (SSL)
- Communication port for connections between Security Center applications and the RabbitMQ server.
The default port is 5671.
Best Practice: Ensure optimal performance of the RabbitMQ
service and avoid potential issues by configuring your anti-virus software to exclude
the RabbitMQ database folder during scans.
Folder location:
C:\ProgramData\Genetec\RabbitMQ\db
NOTE: The Incident Manager role can only connect to RabbitMQ using the SSL port. Using the
non-SSL port results in a failed connection. For instructions on modifying the port
assignment, see
Modifying RabbitMQ ports.
As of Mission Control 2.13.4.0, the minimum required
version of RabbitMQ is 3.8.3.
-
Click Next.
Genetec Mission Control™ Web API configuration
page
-
Select the Web Documentation checkbox to access Web API
documentation.
NOTE: (Optional) You can change the default Web API
port and install location for the Mission Control Web API. The default
port is 9550.
Best Practice: Disable web documentation in a production
environment.
-
Click Next.
Genetec Document Service
configuration page
-
(Optional) You can change the default location to install Genetec Document
Service.
-
Click Next and you’re ready to install the program.
-
Click Install.
-
If you didn’t select the option to restart the Genetec Server service as part of the
installation, restart it after the installation is complete.
Adding the Incident Manager role:
-
From the Config Tool homepage, open the System task and click the
Roles view.
-
Click Add an entity (
) and then click
Incident Manager (
).
The
Creating a role: Incident Manager window opens.
NOTE: The Incident Manager role is hosted by default on your main server
and there can be only be only one instance of this role on your
system.
-
On the Specific info page, do the following:
-
In the Database server field, select or type the name of the
database server.
-
In the Database field, select or type the name of the
database (for example, IncidentManager).
-
In the Authentication field, choose
Windows or SQL Server as your
authentication method.
-
Click Next.
-
On the Basic information page, do the following:
-
Type the Entity name (Incident
Manager).
-
Type an Entity description for the role.
-
Click Next.
-
On the Summary page, do the following:
-
Verify the information you entered.
-
If everything is correct, click Create, or click
Back to modify your settings.
When the role is created, you see the following message in the
Entity creation outcome page:
The operation was successful.
NOTE: Incident Manager role configuration can also be modified after
the role has been created.
-
Click Close.
Results
The following are added to Security Center: