Limitations in Genetec Mission Control™ 2.7 GA - Genetec Mission Control™ 2.7 GA

Genetec Mission Control™ Release Notes 2.7 GA

series
Genetec Mission Control™ 2.7 GA
revised_modified
2018-02-01

Limitations are software or hardware issues that cannot be fixed. For certain limitations, workarounds are documented.

Genetec Mission Control™ 2.7 GA includes the following limitations:

Issue Description
1188735 Profile auto-assignment: When operators allowed to use profiles log on through a Security Desk workstation without Genetec Mission Control™ installed, the profiles are auto-assigned to them.
1108767 The incident configuration audit trails are never deleted.
815690 RabbitMQ: On machines that are running Windows 7 and Windows Server 2008 R2, you cannot connect to RabbitMQ using an IPv4 address when IPv6 is enabled.
Workaround: Disable IPv6 from the machine's network configuration, or use the local name of the machine to connect instead of the IPv4 address.
721822 When you delete an incident icon from the Properties tab, the icon is only removed for the selected incident not all incidents.
632319 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).
591238 Monitoring task: When you save and close an incident workspace, the workspace reopens with the General tab displayed instead of the Incident tab.
583248 Incident report: If a custom State label contains underscore characters (_), these characters are not displayed in the contextual menu when you right-click on an incident to change the state.
545314 Incident monitoring: Grouping over 5000 incidents can take up to three minutes, and Security Desk does not respond during this time.
518515 Incident monitoring: When you maximize and restore a map in the task, the Incident pane size also changes.