EN - Mission Control Release Notes 3.0.4.0

Genetec Mission Control™ Release Notes
3.0.4.0
Click here for the most recent version of this document.
Document last updated: February 7, 2021

Legal notices
©2021 Genetec Inc. All rights reserved.
Genetec Inc. distributes this document with software that includes an end-user license agreement and is
furnished under license and may be used only in accordance with the terms of the license agreement. The
contents of this document are protected under copyright law.
The contents of this guide are furnished for informational use only and are subject to change without notice.
Genetec Inc. assumes no responsibility or liability for any errors or inaccuracies that may appear in the
informational content contained in this guide.
This publication may not be copied, modified, or reproduced in any form or for any purpose, nor can any
derivative works be created therefrom without Genetec Inc.’s prior written consent.
Genetec Inc. reserves the right to revise and improve its products as it sees fit. This document describes the
state of a product at the time of document’s last revision, and may not reflect the product at all times in the
future.
In no event shall Genetec Inc. be liable to any person or entity with respect to any loss or damage that is
incidental to or consequential upon the instructions found in this document or the computer software and
hardware products described herein.
Genetec™, AutoVu™, AutoVu MLC™, Citywise™, Community Connect™, Curb Sense™, Federation™, Flexreader™,
Genetec Airport Sense™, Genetec Citigraf™, Genetec Clearance™, Genetec ClearID™, Genetec Mission Control™,
Genetec Motoscan™, Genetec Patroller™, Genetec Retail Sense™, Genetec Traffic Sense™, KiwiVision™,
KiwiSecurity™, Omnicast™, Privacy Protector™, Sipelia™, Stratocast™, Streamvault™, Synergis™, Valcri™, their
respective logos, as well as the Mobius Strip Logo are trademarks of Genetec Inc., and may be registered or
pending registration in several jurisdictions.
Other trademarks used in this document may be trademarks of the manufacturers or vendors of the
respective products.
Patent pending. Genetec™ Security Center, Omnicast™, AutoVu™, Stratocast™, Genetec Citigraf™, Genetec
Clearance™, and other Genetec™ products are the subject of pending patent applications, and may be the
subject of issued patents, in the United States and in other jurisdictions worldwide.
All specifications are subject to change without notice.
Document information
Document title: Genetec Mission Control™ Release Notes 3.0.4.0

Original document number: EN.705.001-V3.0.4.0(1)
Document number: EN.705.001-V3.0.4.0(1)
Document update date: February 7, 2021
You can send your comments, corrections, and suggestions about this guide to
documentation@genetec.com.
Contents
Preface
Legal notices . . . . . . . . . . . . . . . . . . . . . ii
Chapter 1: Release notes

What's new in Genetec Mission Control™ 3.0.4.0 . . . . . . . . . . . . . 2
Documentation enhancements in Genetec Mission Control™ 3.0.4.0 . . . . . . . 3
Resolved issues in Genetec Mission Control™ 3.0.4.0 . . . . . . . . . . . 4
Resolved security-related issues in Genetec Mission Control™ 3.0.4.0 . . . . . . . 5
Known issues in Genetec Mission Control™ 3.0.4.0 . . . . . . . . . . . . . 6
Known issues in Genetec Mission Control™ Web API . . . . . . . . . . . 7
Limitations in Genetec Mission Control™ 3.0.4.0 . . . . . . . . . . . . . 8
Limitations in Genetec Mission Control™ Web API . . . . . . . . . . . 11
Genetec Mission Control™ 3.0.4.0 system requirements . . . . . . . . . . . 12
Supported languages in Genetec Mission Control™ 3.0.4.0 . . . . . . . . . . 13
Supported upgrades from earlier versions of Genetec Mission Control™ . . . . . . . 14
Product compatibility for Genetec Mission Control™ 3.0.4.0 . . . . . . . . . . 15
Chapter 2: Installation and upgrade notes

Upgrade tips for Genetec Mission Control™ . . . . . . . . . . . . . . 17
Upgrading Genetec Mission Control™ on the server . . . . . . . . . . . 17
Upgrading RabbitMQ . . . . . . . . . . . . . . . . . . 19
Restarting services . . . . . . . . . . . . . . . . . . . 20
Upgrading RabbitMQ on the server . . . . . . . . . . . . . . . 20
Validating RabbitMQ upgrade . . . . . . . . . . . . . . . . 22
Where to find product information . . . . . . . . . . . . . . . 23
Technical support . . . . . . . . . . . . . . . . . . . . 24
techdocs.genetec.com | Genetec Mission Control™ Release Notes 3.0.4.0

EN.705.001-V3.0.4.0(1) | Last updated: February 7, 2021 iii
1
Release notes
Genetec Mission Control™ 3.0.4.0 is a general availability release that includes new features and enhancements. This
document describes the release in detail, and provides late-breaking or other information that supplements the
Genetec™ Security Center documentation.
This section includes the following topics:

• "What's new in Genetec Mission Control™ 3.0.4.0" on page 2
• "Known issues in Genetec Mission Control™ 3.0.4.0" on page 6
• "Limitations in Genetec Mission Control™ 3.0.4.0" on page 8
• "Genetec Mission Control™ 3.0.4.0 system requirements" on page 12
• "Supported languages in Genetec Mission Control™ 3.0.4.0" on page 13
• "Supported upgrades from earlier versions of Genetec Mission Control™" on page
14
• "Product compatibility for Genetec Mission Control™ 3.0.4.0" on page 15

EN.705.001-V3.0.4.0(1) | Last updated: February 7, 2021 1
Release notes
What's new in Genetec Mission Control™ 3.0.4.0

Genetec Mission Control™ 3.0.4.0 includes the following enhancements.
Genetec Mission Control™ installer updates
You can choose to install Genetec Mission Control™ Web API and enable access to web documentation
directly from the Genetec Mission Control™ installer. For more details, see the Genetec Mission Control™
Deployment Guide.
RabbitMQ compatibility notice
It is recommended to upgrade to RabbitMQ version 3.9.1 using the Genetec Mission Control™ installer,
depending on your system environment. For more information, see the Genetec Mission Control™ Deployment
Guide.
For more information about how to upgrade your RabbitMQ failover cluster, see the official RabbitMQ
Clustering Guide.
General enhancements
• New automation activity:

• Maintenance: Use the Maintenance activity to enable or disable maintenance mode for source
entities associated with an active incident.
• Updates to the automation activities:
• Send an email: From the Send an email activity message field list, select the Snapshot field to include
2 snapshots captured by camera entities attached to the active incidents. Snapshots are taken 5
seconds before the incident and at the time of incident occurrence.
• Export incident: Use the Export incident activity to export incidents in XML, PDF, or HTML formats to
a specified folder.
• Updates to the Incident monitoring task: You can customize the following from Incident monitoring >
Settings > Options:
• Source entities display in Monitoring task: Choose to display or hide source entities that lack video.
By default this option is selected.
• Font size for the incident list view: Select a font size between 10 - 18 for the incident list view in the
Incident monitoring or Incident report tasks.
• Default operational status for new incident types: When configuring or importing incident types, the
operational status is set to Not in service by default. You must manually reset the status from Incident
configuration > <incident type> > Operational status to use these incident types.
Web API enhancements
Genetec Mission Control™ Web API 2.5 includes the following enhancements:
• Get a list of entities manually attached to an incident: Use the GET /v2/Incidents/{id}/
ManuallyAttachedEntityIds endpoint to retrieve a list of entities manually attached to a specified incident.
• Get URLs linked to dynamic user procedure steps: The AttachedLinks property retrieves URLs linked to
dynamic user procedure steps:

Release notes
• When using the GET/v2/Incidents/{id}/CurrentProcedureStep endpoint, you can see all the URLs attached to
the current dynamic user procedure step of the specified incident.
• When using the GET/v2/Procedures/{id} endpoint, you can see the linked URLs for all steps in the specified
the dynamic user procedure.
For technical information about API endpoints and other programming considerations, see the Web API
developer documentation. For instructions to open the Web API help page, see the Genetec Mission Control™
Deployment Guide.
Important links
• For features introduced in previous releases, see Genetec Mission Control™ Release Notes on the TechDoc
Hub.
• For an overview of product availability, support, and available services, see the Product Lifecycle page on
GTAP.
• For an overview of what Genetec Mission Control™ can do for your organization, see our product
description web page.
Documentation enhancements in Genetec Mission Control™ 3.0.4.0

Genetec Mission Control™ 3.0.4.0 includes the following documentation enhancements.
IMPORTANT: Translation of documentation is ongoing. Documentation in languages other than English
might not be complete at the time of release. For the latest version of the documentation, see the Genetec™
TechDoc Hub.
Documents updated
The following documents were updated in this release:
Document title Languages available this release
Genetec Mission Control™ Administrator Guide English, German
Genetec Mission Control™ Deployment Guide English , German
Genetec Mission Control™ User Guide English, French
Genetec Mission Control™ Release Notes English, French, German, Spanish, Turkish,
Italian
Troubleshooting Genetec Mission Control™ English
Product compatibility for Genetec Mission Control™ English
Major documentation changes
The Genetec Mission Control™ Web API Release notes have been merged with Genetec Mission Control™
Release notes.
Documents removed
Genetec Mission Control™ Web API Release notes.

Release notes
Resolved issues in Genetec Mission Control™ 3.0.4.0

The following software issues are resolved in Genetec Mission Control™ 3.0.4.0.
Issue Description
3011594 After upgrading from Genetec Mission Control™ 3.0.2.0 to 3.0.3.0, database update fails with
a Database action failed error message.
2991206 After a system reboot, the Incident Manager role does not connect to RabbitMQ, incidents
cannot be triggered, and the directory is offline.
2989674 When a standard incident type is changed to collaborative incident type using automation
workflow, you cannot add a reminder to the sub-incident.
2988946 When multiple incidents occur, the system is overloaded and the automation workflow
stops working and the Latest activity displays the Automation loop detected, automation execution
stopped following error message.
2974810 When an operator logs off from Security Desk, the active incidents are dispatched again
without updating the associated incident owner.
2973867 Active incidents in Security Desk do not use custom tile layouts in the Monitoring task.
2972015 When Recipients > Specific list in collaborative incident type is empty, Copy configuration
does not copy all the details of the incident type.
2971734 Sorting the incident list view in the Incident report task by ascending or descending order of
Additional fields does not work if the field values are negative or greater than 10.
2967347 In the Incident monitoring task, the Sort by list remains visibile after making a selection for
sorting incident list view.
2964538 After saving a new incident trigger that is configured with multiple events, the event source
for the first event disappears and the last event in the list has the source that was assigned
to the first event in the list.
2911010 When an active incident has a dynamic SOP step with Change incident location
configuration, the system displays the following warning message in the Incident details
pane: Custom action configured for this step cannot be executed. Notify management and check for
alternative action.
2805413 When there are 100 or more events aggregated in an incident automation workflow, the
Latest activity widget displays only the first event.
Workaround: To see the list of aggregated events, click More in the Latest activity widget.
Resolved issues in Genetec Mission Control™ Web API 2.5

The following software issues are resolved in Genetec Mission Control™ Web API 2.5.
Issue Description
2989158 When a command is sent using an incorrect type number, an InternalServerError error
message is received instead of BadRequest.

Release notes
Resolved security-related issues in Genetec Mission Control™ 3.0.4.0

There are no security-related issues in Genetec Mission Control™ 3.0.4.0.
Resolved security-related issues in Genetec Mission Control™ Web API 2.5

There are no security-related software issues in Genetec Mission Control™ Web API 2.5.

Release notes
Known issues in Genetec Mission Control™ 3.0.4.0

Genetec Mission Control™ 3.0.4.0 includes the following known issues.
Issue First Description

reported
in
3020988 3.0.4.0 If an incident is triggered on an ESRI map configured with Initial map zoom level
for selected incidents, the zoom level cannot be changed on the map.
2989703 3.0.4.0 In the Monitoring task, door entities are missing from the display layout even
when the Display entity activity is configured within the automation workflow of
the incident.
2973873 3.0.3.0 When the Genetec™ Server is restarted with an unsaved incident type
configuration in Config Tool, the Incident Manager role might do one of the
following:
• Display an error message
• Lose the configuration
• Prompt to save changes
2972219 3.0.3.0 The Acknowledge alarm button in the General pane of the Incident monitoring
task does not work for active alarms associated with active incidents.
2936276 3.0.3.0 When an incident is triggered on a custom entity created using a plugin, the
incident is not displayed in the Monitoring task.
2934726 3.0.3.0 If a user does not have the TTR Metrics privilege, TTR notifications are not
displayed in Security Desk.
2922169 3.0.3.0 An active incident triggered by an Access denied event plays live video in the
Monitoring task, even when the camera associated with the door is configured for
playback.
2921316 3.0.3.0 When enabling the Advanced event filtering option in the incident trigger
configuration, clicking Save in the event configuration dialog box does not save
the settings.
Workaround: Click Apply in the Triggers page.
2863008 3.0.2.0 Genetec Mission Control™ cannot be uninstalled using the installer due to
RabbitMQ errors.
2827777 3.0.2.0 When active incidents are grouped by Latest event time, the group header
includes an invalid date for manually triggered incidents.
2827533 3.0.2.0 Expanding the view of a sub-incident in the Incident details pane refreshes the
Incident details pane widget view to the parent collaborative incident.
2810731 3.0.2.0 The list of Available columns in the Incident monitoring task Select columns dialog
box does not automatically refresh to reflect the updates to the Custom columns
list in the Incident Manager properties.

Release notes

reported
in
2806862 3.0.2.0 When there are active incidents triggered on different maps, and the Show all
incidents on default map option is selected in the Incident monitoring task
Settings > Incident options dialog box, the map view does not refresh to
display an accurate list of active incidents.
2777100 3.0.3.0 When an incident type is configured to be triggered by an Access denied event
followed by the user starting a camera recording, sometimes the trigger rules are
not followed.
2739311 3.0.1.0 Security Center users without TTR Metrics privilege can see TTR notifications in
Security Desk.
2738316 3.0.1.0 When a sound file used in an automation activity is deleted, there is no warning
message about missing sound file in the automation workflow.
2697093 3.0.1.0 When configuring the Column color automation activity, the color palette popup
does not always collapse automatically.
1962199 2.10 GA Unable to cycle between live and playback streams from the dashboard Camera
widget in Incident management.
1787956 2.9 GA After deleting a user who is the only recipient of a specific incident type, new
incidents of that type have an invalid state with no recipients.
Workaround: Configure incidents to fall back to other recipients if no one
responds.
1668680 2.10 GA Activating Maintenance mode on the Incident Manager role has no effect.
1184508 2.7 GA Genetec Mission Control™ is not compatible with earlier versions and does not
display a warning message when incompatible versions are used together.
1108578 2.10 GA Audit trails: Document changes made in the Document management view of the
Incident configuration task are not reported in the Audit trails task.
Known issues in Genetec Mission Control™ Web API

Genetec Mission Control™ Web API includes the following known issues.

reported in
2833501 2.3 No error message is received when the sortBy command in the GET /v2/Incidents
endpoint is configured with multiple incident properties.
2833485 2.3 The sortBy command in the GET /v2/Incidents endpoint does not accommodate
multiple incident properties to sort an incident list.

Release notes
Limitations in Genetec Mission Control™ 3.0.4.0

Genetec Mission Control™ 3.0.4.0 includes the following known limitations.

reported in
2949285 3.0.3.0 When running the CCure plugin, opening an active incident with a camera
attached to the associated alarm in the Monitoring task, prevents the CCure
widget from being displayed.
2938704 3.0.3.0 When opening an incident with associated alarms on a tile in the Incident report
task, the alarm is not visible.
2862461 3.0.2.0 When RabbitMQ logon password is changed in the web management portal,
connection to RabbitMQ is still live in Config Tool with the old password
configuration.
2835512 3.0.2.0 The Monitoring task does not refresh dynamically to show new location when
active incident location is changed.
2833670 3.0.2.0 Right-clicking an incident not linked to an area or a map and triggered on
a federated entity does not include the same list of options as an incident
triggered on a non-federated entity.
2828081 3.0.2.0 The location of an incident is not refreshed in the Monitoring task, when the
incident type's automation workflow includes a Wait for incident state activity
before a Display entity activity.
2825388 3.0.2.0 When the workstation version of Genetec Mission Control™ is 3.0.1.0 and the
server has a later version of Genetec Mission Control™, the Incident monitoring
task displays a black screen.
2824205 3.0.2.0 The tile view is different when opening an incident in Monitoring task from
Incident report or Incident monitoring task.
2822997 3.0.2.0 When selecting a value other than the default value for the Incident details
pane font size option in Incident monitoring > Settings > Options, there
are extra line breaks after incident description in the Overview widget in the
Incident details pane.
2777927 3.0.3.0 Upgrading to Genetec Mission Control™ 3.0.3.0 from an earlier version the
upgrade is blocked with an error message.
2776991 3.0.2.0 When incident descriptions are long, exporting the incident report in CSV and
JPG to include Charts mode of the report crops the image and description.
2765501 3.0.2.0 There is a delay in updating door state after a door event in Conditional
activities.
Workaround: Do not use door state check immediately after Wait for event
> Specific event > <door event> in incident type Conditional activities
automation activity.
2738978 3.0.1.0 Sometimes when multiple users are connected to the same system and are
viewing the same incident, the dynamic SOP widget has a minor time lag.

Release notes

reported in
2734972 3.0.1.0 Sometimes when an active incident automation workflow includes multiple
video entities, Security Desk freezes while the video streams load.
2730468 3.0.1.0 When adding multiple auto validation conditions to a dynamic SOP step, the Edit
option dialog box expands out of view.
2708341 3.0.1.0 When opening the Incident monitoring task, the incident Name and
Locationcolumn widths are set to the width of the strings of the incident
displayed and not to the maximum width needed for other incidents in the list.
2658251 3.0.1.0 Custom widget headers in the Incident details pane use the class name in the
code instead of set display name.
2600265 2.13.4.0 When emailing an incident report from the System > Scheduled tasks in Config
Tool, the incident category detail is missing.
2565676 2.13.4.0 If a user or user group assigned as recipient for an incident type is deleted
when an incident's Recipients tab is open, the recipients list is not automatically
updated to reflect the change.
2565626 2.13.4.0 If a new user group is created when the Incident configuration page is open, the
Auto-assign recipients list is not automatically updated to show the new user
group.
Workaround: Close and reopen the Incident configuration task.
2562012 2.13.4.0 When an incident is triggered on an alarm with a door entity attached, the door
entity is not visible in the General tab of the Incident monitoring task.
2542520 2.13.3.0 Triggered incident pins disappear when switching between maps in the Incident
monitoring tasks.
2462156 2.13.3.0 When adding more than one output entity in the Trigger output workflow
activity, the dialog box shows unnecessary entities.
2446797 2.13.3.0 When logging on to a saved workspace in Security Desk with a triggered
incident in the Monitoring task, the Incident details pane is not displayed
accurately.
Workaround: Select another incident in the Incident monitoring task.
2438786 2.13.3.0 When configuring the Trigger output workflow activity, the dialog box displays
roles and entities that have no valid outputs.
2432621 2.13.2.0 The Contact entity list in the Call action configuration dialog box gets
deselected when searching for the contact entity.
2431627 2.13.2.0 When the Export incident activity is used immediately after the Trigger and
add sub-incident activity in an incident workflow, the exported information
does not include sub-incident ID.
2421575 2.13.2.0 Activating or deactivating a profile for a user already logged into Security Desk,
reloads the queue of incidents configured with auto-open in the notification tray
in Security Desk.

Release notes

reported in
2416095 2.13.2.0 When Synchronize incident monitoring tasks is selected in Security Desk for
a set up with multiple monitors, selecting multiple incidents with different map
configurations, displays the default map with missing incident details.
2372085 2.13.2.0 When multiple images are configured as documents for a dynamic SOP step,
selecting the option All documents in the step displays only one of the images.
2371156 2.13.2.0 When an incident configured with Auto-open in Monitoring is triggered,

the Monitoring task does not close automatically even when the incident is
transferred to another recipient.
2370643 2.13.2.0 When saving an Incident report task in Security Desk, the default sort option for
incident reports is not saved.
2236819 2.12.0.0 Sometimes the workflow does not run because the system reads it inaccurately.
NOTE: For more details, see Unable to parse incident type workflow error.
2211429 2.11 SR1 If the Wait for state > New activity is at the beginning of the workflow, it will
not be executed.
2119187 2.11 GA Incidents triggered from the Web API with geographical coordinates do not
display correctly on an image map if the map is not georeferenced, or if the map
is georeferenced and the incident is triggered outside the image boundary.
2049698 2.11 GA Incidents triggered in an area on a .jpeg image map do not include the incident
location (latitude and longitude).
2020510 2.10 GA Incident is not triggered by an Access denied event from a cardholder group,
when the specific user is in a subgroup under that group.
1861305 2.9 GA Documents that are available on a schedule remain visible in the Documents
widget on the incident dashboard, if an associated incident is selected when the
scheduled period ends.
Workaround: Refresh the Documents widget by logging off and logging back
on, or briefly switching to another incident.
1753448 2.8 GA When using the Change incident type workflow activity to change an incident to
another type with TTR enforced, TTR events will not be triggered, if they were
already triggered in the previous incident type.
1633372 2.8 GA After generating an incident report with several incidents displayed on the
same map, selecting one of the incident pins, does not select the corresponding
incident in the incident list.
1188735 2.7 GA Profile auto-assignment: When operators who are allowed to use profiles log on
through a Security Desk workstation without Genetec Mission Control™ installed,
the profiles are auto-assigned to them.
1108767 2.7 GA The incident configuration audit trails are never deleted.
721822 2.3 GA When you delete an incident icon from the Properties tab, the icon is only
removed for the selected incident, not all incidents.
632319 2.3 GA Failover: After a failover occurs, the configured Delay for the workflow of an
incident is not respected. The Delay duration reverts to the default setting (0).

Release notes

reported in
545314 2.3 GA Incident monitoring: Grouping over 5000 incidents can take up to three minutes,
and Security Desk does not respond during this time.
518515 2.3 GA Incident monitoring: When you maximize and restore a map in the task, the
Incident pane size also changes.
Limitations in Genetec Mission Control™ Web API

Genetec Mission Control™ Web API includes the following known limitations.

reported in
2594509 Web API 2.0 Even when there are multiple items retrieved for the GET /v2/Incidents endpoint
with the IsRecipient filter set to false and the GET /v2/Incidents/{id}/Events endpoint,
the TotalResultsCount still shows null value.
2489269 Web API 1.5 To apply filters on active incidents through Web API Report privilege is required.
2280989 Web API 1.3 The ChangeLocation command in Genetec Mission Control™ Web API only accepts
latitude and longitude coordinates for georeferenced maps.
2117590 Web API 1.1 When triggering an incident through the Web API, if you specify the location
as both an entity identifier and geographic coordinates, the location will show
as the entity in the incident list, but the incident will appear on the map at the
provided coordinates.
2117554 Web API 1.1 WAPI: After changing the language in Security Center, incident states and
priorities retrieved by the Web API are shown in the language set at installation.
Workaround: Change culturename in the Security Center language.xml file to the
correct language.
2047551 Web API 1.0 WAPI: Genetec Mission Control™ Web API does not support automatic failover
like other Security Center roles.
2030530 Web API 1.0 WAPI: C# code sample is not visible when the Web API developer documentation
is open in Internet Explorer.
2025944 Web API 1.0 WAPI: Audit trail report shows logon events from the machine where the Web
API is installed, not the machine where the request originated.
1957969 Web API 1.0 WAPI: Cannot connect to Security Center with the Web API after changing the
secure HTTP port in Server Admin.
Workaround: Restart the Genetec™ Server service.

Release notes
Genetec Mission Control™ 3.0.4.0 system requirements

Systems running Genetec Mission Control™ 3.0.4.0 must meet or exceed the recommended Security Center
server requirements.
For Security Center server metrics, refer to Security Center server requirements topic in the Security Center
System Requirements Guide.

Release notes
Supported languages in Genetec Mission Control™ 3.0.4.0

Genetec Mission Control™ 3.0.4.0 software is available in the following languages.
• Arabic
• Dutch
• English
• French
• Italian
• Spanish
• Thai
• Turkish
• Japanese
• Korean
• German
Genetec Mission Control™ Web API is available in English.

Release notes
Supported upgrades from earlier versions of Genetec

Mission Control™
Not all earlier versions of Genetec Mission Control™ can upgrade directly to Genetec Mission Control™ 3.0.4.0.
Before you upgrade, you must check which upgrade path applies to your current version.
A one-step upgrade is supported for the following Genetec Mission Control™ releases:
• Genetec Mission Control™ 2.13.4.0 and later.
A two-step upgrade is required for Genetec Mission Control™ releases before 2.13.4.0:
• Step 1: Upgrade to Genetec Mission Control™ 2.13.4.0.
• Step 2: Upgrade to Genetec Mission Control™ 3.0.4.0.
NOTE: For versions 2.12.0.0 and earlier it is recommended you run Legacy Workflows using Mission
Control commands command from the Server Admin:
1. Click <Your server name>.
2. Click Actions > Console > Commands > Mission Control commands > Legacy Workflows.
Example: When you have legacy workflows running for active incidents from 2.11 GA the upgrade is blocked.
NOTE: If you have Genetec Mission Control™ Web API installed, it is automatically upgraded to a compatible
version when upgrading Genetec Mission Control™.

Release notes
Product compatibility for Genetec Mission Control™ 3.0.4.0

Genetec Mission Control™ 3.0.4.0 is compatible with specific versions of Security Center and other products.
Genetec Mission Control™ 3.0.4.0 is compatible with Security Center Enterprise, version 5.10.0.0 or later.
NOTE: As of Genetec Mission Control™ 2.13.4.0, you must have RabbitMQ 3.8.3 or higher installed.
For the latest up-to-date compatibility information and a list of other compatible products, see Product
compatibility for Genetec Mission Control™.

2
Installation and upgrade notes
This section includes the following topics:
• "Upgrade tips for Genetec Mission Control™" on page 17

Upgrade tips for Genetec Mission Control™

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

Get the latest build of Genetec Mission Control™. For information on how to get the package, see the Genetec
Mission Control™ Deployment Guide.
What you should know

If you are running RabbitMQ version 3.8.3 or later, it is optional to upgrade your RabbitMQ version. However,
it is recommended you upgrade RabbitMQ to the version available with the installer package.
Follow the instructions below to upgrade your system:
1 Upgrade the Directory server.
2 Upgrade any failover Security Center Directory servers.
3 Upgrade the Genetec Mission Control™ server.
NOTE: This process upgrades Genetec Mission Control™, Genetec Mission Control™ Web API, the Incident
Manager database and RabbitMQ if it is on the same server as Genetec Mission Control™.
4 Upgrade any failover Genetec 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:
a) Deactivate the Incident Manager role:
1. Select System > Roles > Incident Manager.
2. Right click the Incident Manager role to select Maintenance > Deactivate role.
b) Upgrade your RabbitMQ configuration.

7 If the server is not back online, start the Genetec™ Server service on the Directory server.
8 If the server is not back online, start the Genetec™ Server service on the Genetec Mission Control™ server.
9 Upgrade all Genetec Mission Control™ workstations.
You have successfully upgraded your Genetec Mission Control™ environments.
Upgrading Genetec Mission Control™ on the server

Follow the procedure below to upgrade Genetec Mission Control™ on the server.
To upgrade Genetec Mission Control™ on the server:
1 Launch the Genetec Mission Control™ Installer.
2 On the Choose Setup Language page, select English or French and click Next.
3 On the Welcome to the InstallShield Wizard page, click the links to read Genetec Mission Control™
documentation, and then click Next.
4 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.

5 On the Setup Type page, choose Advanced and click Next.
6 On the Custom Setup page, clear the RabbitMQ Server and Restart Genetec™ Server options.
NOTE: If you have RabbitMQ on this server, select the RabbitMQ option in the dialog box to update both
Genetec Mission Control™ and RabbitMQ.
7 Click Install to complete the Genetec Mission Control™ upgrade.

NOTE: Do not restart the Genetec™ Server manually.

Upgrading RabbitMQ
If RabbitMQ is deployed on a standalone machine or in a high availability configuration with multiple nodes,
you must use an adapted procedure to upgrade RabbitMQ to version 3.9.1 or later, as applicable.
Before you begin

This procedure is specific to the deployment of RabbitMQ by the Genetec Mission Control™ installer. For
external deployment of RabbitMQ with third party solutions, refer to the third party documentation as
deployment process may differ.
To see how .erlang cookie paths are constructed, see the RabbitMQ Clustering Guide
Copy the Genetec Mission Control™ 3.0.4.0 installation package to all RabbitMQ servers.
TIP: It is recommended to use a 3-node cluster for high availability. For details, see the Genetec Mission
Control™ Deployment Guide.
What you should know

Before you upgrade your RabbitMQ, validate your existing RabbitMQ configuration.
To upgrade RabbitMQ on standalone machines, perform the following steps on each node:
1 Stop the RabbitMQ service.
2 Backup the .erlang.cookie file to a temporary storage location.
Usual file path for the .erlang.cookie is C:\Windows\ServiceProfiles\LocalService.
3 Paste the .erlang.cookie file from the temporary storage location to the following folders:
• C:\
• C:\Users\<username>\
• C:\Windows\System32\config\systemprofile
NOTE: If an .erlang.cookie file exists in the destination folder, overwrite it with the copied file.
4 If using your own certificates in C:\Program Files (x86)\Genetec\RabbitMQ, you must create a backup for
them as well.
5 Use the advanced setup in the Genetec Mission Control™ 3.0.4.0 installation wizard to only upgrade
RabbitMQ.
If you have a RabbitMQ configuration for high availability with 3 or more nodes, on each node:
1 Right-click the Notepad application, select Run as administrator, and then open the RabbitMQ.conf file in
Notepad.
By default, the RabbitMQ configuration file, RabbitMQ.conf, is found in C:\ProgramData\Genetec\RabbitMQ
\config.
TIP: Using Notepad++ with Makefile set as language improves the readability of the file.
2 Modify the following line from:
# cluster_partition_handling = pause_minority
to:
cluster_partition_handling = pause_minority
By removing the # symbol, the line is no longer flagged as a comment and becomes part of the code.
3 Save the file.
4 Restart the RabbitMQ service.

Restarting services
You can restart Genetec™ Server and RabbitMQ service from the Microsoft Management Console Services.
Restarting Genetec™ Server service:
1 On the server, open Microsoft Management Console Services (services.msc).
2 Select the Genetec™ Server from the list of services and click Restart.
Security Desk remains offline until Genetec™ Server is back online.
Restarting RabbitMQ service:
1 On the RabbitMQ server, open Microsoft Management Console Services (services.msc).
2 Select the RabbitMQ from the list of services and click Restart.
Upgrading RabbitMQ on the server

If your deployment architecture includes RabbitMQ on a dedicated server, use the following procedure to
upgrade your system.
Before you begin

If you are upgrading from Genetec Mission Control™ 2.13.3.0, you would not need to upgrade your RabbitMQ
setup. However, it is recommended that you validate your RabbitMQ setup after the upgrade to ensure
optimal operational efficiency.
To upgrade your RabbitMQ version on the server:
1 Launch the Genetec Mission Control™ Installer.
2 On the Choose Setup Language page, select English or French and click Next.
3 On the Welcome to the InstallShield Wizard page, click the links to read Genetec Mission Control™
documentation, and then click Next.
4 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.

5 On the Setup Type page, choose Advanced and click Next.
6 On the Custom Setup page:

• Select the RabbitMQ Server option.
• Clear both the Mission Control and Restart Genetec™ Server options.
7 Click Install to complete the RabbitMQ upgrade.

Security Desk and the Genetec Mission Control™ Incident monitoring task remain online during the
RabbitMQ upgrade. The RabbitMQ cluster configuration is not disturbed during this upgrade.

Validating RabbitMQ upgrade

If you are upgrading your Genetec Mission Control™ environment, it is recommended to validate your
RabbitMQ setup before and after the upgrade.
To validate your RabbitMQ setup:
1 Open the RabbitMQ web portal (https://localhost:15671).
2 In the Overview tab, ensure that all RabbitMQ nodes are green. This indicates that the nodes are active
within the cluster.
Your RabbitMQ configuration has been validated.

Where to find product information
You can find our product documentation in the following locations:
• Genetec™ TechDoc Hub: The latest documentation is available on the TechDoc Hub. To access the
TechDoc Hub, log on to Genetec™ Portal and click TechDoc Hub. Can't find what you're looking for?
Contact documentation@genetec.com.
• Installation package: The Installation Guide and Release Notes are available in the Documentation folder
of the installation package. These documents also have a direct download link to the latest version of the
document.
• Help: Security Center client and web-based applications include help, which explains how the product
works and provide instructions on how to use the product features. To access the help, click Help, press
F1, or tap the ? (question mark) in the different client applications.

Technical support
Genetec™ Technical Assistance Center (GTAC) is committed to providing its worldwide clientele with the best
technical support services available. As a customer of Genetec Inc., you have access to TechDoc Hub, where
you can find information and search for answers to your product questions.
• Genetec™ TechDoc Hub: Find articles, manuals, and videos that answer your questions or help you solve
technical issues.
Before contacting GTAC or opening a support case, it is recommended to search TechDoc Hub for
potential fixes, workarounds, or known issues.
To access the TechDoc Hub, log on to Genetec™ Portal and click TechDoc Hub. Can't find what you're
looking for? Contact documentation@genetec.com.
• Genetec™ Technical Assistance Center (GTAC): Contacting GTAC is described in the Genetec™ Lifecycle
Management (GLM) documents: Genetec™ Assurance Description and Genetec™ Advantage Description.
Additional resources
If you require additional resources other than the Genetec™ Technical Assistance Center, the following is
available to you:
• Forum: The Forum is an easy-to-use message board that allows clients and employees of Genetec Inc. to
communicate with each other and discuss many topics, ranging from technical questions to technology
tips. You can log on or sign up at https://gtapforum.genetec.com.
• Technical training: In a professional classroom environment or from the convenience of your own office,
our qualified trainers can guide you through system design, installation, operation, and troubleshooting.
Technical training services are offered for all products and for customers with a varied level of technical
experience, and can be customized to meet your specific needs and objectives. For more information, go
to http://www.genetec.com/support/training/training-calendar.
Licensing
• For license activations or resets, please contact GTAC at https://portal.genetec.com/support.
• For issues with license content or part numbers, or concerns about an order, please contact Genetec™
Customer Service at customerservice@genetec.com, or call 1-866-684-8006 (option #3).
• If you require a demo license or have questions regarding pricing, please contact Genetec™ Sales at
sales@genetec.com, or call 1-866-684-8006 (option #2).
Hardware product issues and defects
Please contact GTAC at https://portal.genetec.com/support to address any issue regarding Genetec™

appliances or any hardware purchased through Genetec Inc.


EN - Mission Control Release Notes 3.0.4.0

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

EN - Mission Control Release Notes 3.0.4.0

Uploaded by

Copyright:

Available Formats

Genetec Mission Control™ Release Notes

Click here for the most recent version of this document.

Document last updated: February 7, 2021

Document title: Genetec Mission Control™ Release Notes 3.0.4.0

Chapter 1: Release notes

Chapter 2: Installation and upgrade notes

techdocs.genetec.com | Genetec Mission Control™ Release Notes 3.0.4.0

This section includes the following topics:

techdocs.genetec.com | Genetec Mission Control™ Release Notes 3.0.4.0

What's new in Genetec Mission Control™ 3.0.4.0

Genetec Mission Control™ installer updates

RabbitMQ compatibility notice

• New automation activity:

Web API enhancements

techdocs.genetec.com | Genetec Mission Control™ Release Notes 3.0.4.0

Documentation enhancements in Genetec Mission Control™ 3.0.4.0

The following documents were updated in this release:

Document title Languages available this release

Genetec Mission Control™ Administrator Guide English, German

Genetec Mission Control™ Deployment Guide English , German

Genetec Mission Control™ User Guide English, French

Troubleshooting Genetec Mission Control™ English

Product compatibility for Genetec Mission Control™ English

Major documentation changes

Genetec Mission Control™ Web API Release notes.

techdocs.genetec.com | Genetec Mission Control™ Release Notes 3.0.4.0

Resolved issues in Genetec Mission Control™ 3.0.4.0

Resolved issues in Genetec Mission Control™ Web API 2.5

techdocs.genetec.com | Genetec Mission Control™ Release Notes 3.0.4.0

Resolved security-related issues in Genetec Mission Control™ 3.0.4.0

Resolved security-related issues in Genetec Mission Control™ Web API 2.5

techdocs.genetec.com | Genetec Mission Control™ Release Notes 3.0.4.0

Known issues in Genetec Mission Control™ 3.0.4.0

Issue First Description

techdocs.genetec.com | Genetec Mission Control™ Release Notes 3.0.4.0

Issue First Description

Known issues in Genetec Mission Control™ Web API

Issue First Description

techdocs.genetec.com | Genetec Mission Control™ Release Notes 3.0.4.0

Limitations in Genetec Mission Control™ 3.0.4.0

Issue First Description

techdocs.genetec.com | Genetec Mission Control™ Release Notes 3.0.4.0

Issue First Description

techdocs.genetec.com | Genetec Mission Control™ Release Notes 3.0.4.0

Issue First Description

2371156 2.13.2.0 When an incident configured with Auto-open in Monitoring is triggered,

techdocs.genetec.com | Genetec Mission Control™ Release Notes 3.0.4.0

Issue First Description

Limitations in Genetec Mission Control™ Web API

Issue First Description

techdocs.genetec.com | Genetec Mission Control™ Release Notes 3.0.4.0

Genetec Mission Control™ 3.0.4.0 system requirements

techdocs.genetec.com | Genetec Mission Control™ Release Notes 3.0.4.0

Supported languages in Genetec Mission Control™ 3.0.4.0

techdocs.genetec.com | Genetec Mission Control™ Release Notes 3.0.4.0

Supported upgrades from earlier versions of Genetec

techdocs.genetec.com | Genetec Mission Control™ Release Notes 3.0.4.0

Product compatibility for Genetec Mission Control™ 3.0.4.0

techdocs.genetec.com | Genetec Mission Control™ Release Notes 3.0.4.0

techdocs.genetec.com | Genetec Mission Control™ Release Notes 3.0.4.0

Upgrade tips for Genetec Mission Control™

Before you begin

What you should know