> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/command-centre-releases/feature-summaries/command-centre-v9.40.md). # Command Centre v9.40 This page answers: what's new in Command Centre v9.40, what you need to check before upgrading, and which operating systems, databases, apps and browsers are supported. {% hint style="info" %} This page describes new Command Centre v9.40 features. It does not describe all Command Centre functionality. {% endhint %} [Click here to download the PDF version.](https://media.gallagher.com/m/62e4e799957787a4/original/Command-Centre-v9-40-Feature-Summary.pdf) ### Compatibility This section contains important notices that must be read when considering Command Centre v9.40. #### Upgrading Command Centre Changes in Command Centre v9.40 may affect sites upgrading from earlier versions. Refer to `3E0068 Release Note Command Centre vEL9.40.XXXX (Upgrade Procedures).pdf` for details. **Supported upgrade paths** | From | To | | -------------------- | -------------------- | | Command Centre v9.0 | Command Centre v9.40 | | Command Centre v9.10 | Command Centre v9.40 | | Command Centre v9.20 | Command Centre v9.40 | | Command Centre v9.30 | Command Centre v9.40 | **Controller firmware compatibility** Command Centre v9.40 supports the Controller 6000 and Controller 7000 firmware vCR9.30. Command Centre v9.40 is compatible with older versions of firmware for upgrade purposes only. No configuration changes should be made on the Controller 6000 and Controller 7000 running pre v9.40 versions once Command Centre has been upgraded. It is recommended to upgrade all controller firmware to the latest version as soon as possible. **GBUS obsolescence: upgrade to HBUS devices** {% hint style="warning" %} **Important:** Command Centre v9.10 and later do not support GBUS devices. Upgrade to HBUS devices before upgrading past Command Centre v9.00. {% endhint %} In answer to the industry's need for an improved device communications protocol, Gallagher released HBUS in 2012 for improved speed, data protection, and automated scalability. These considerable enhancements are a key driver behind our decision to remove software support of GBUS, which was released over 20 years ago. Supporting GBUS costs valuable development time with every release of Command Centre. Once removed, this time can be better used in delivering ongoing value to our customers. **IDEMIA Legacy (MA2G) obsolescence: upgrade to Native (MA5G) devices** {% hint style="warning" %} **Important:** Command Centre v9.30 and later do not support IDEMIA Legacy (MA2G) devices. Upgrade to Native (MA5G) devices before upgrading past Command Centre v9.30. {% endhint %} Due to a new IDEMIA SDK, which does not support Legacy (MA2G) and is required for supporting the VisionPass SP in Command Centre v9.30, we have removed the support for Legacy (MA2G) communication protocol in Command Centre v9.30. IDEMIA stopped supporting the Legacy (MA2G) communication protocol since January 2022, and as such, we will no longer continue to support the MA2G communication protocol. Please see the Product Advisory for more information. {% hint style="info" %} Read the following pre-upgrade information before upgrading to v9.40. {% endhint %} **Pre-Upgrade Validation Tool v9.40** Gallagher has developed the 'Pre-Upgrade Validation Tool'. This utility can be run on the Command Centre server to identify site compatibility issues prior to upgrading, including Controllers running customizations and/or custcard.dlls and legacy hardware. This utility can be found with the installation files (Utilities folder) or downloaded from the [Gallagher Security File Transfers](https://security.gallagher.com/downloads) site in the 'Command Centre and Associated Files > Utilities' folder. This utility should be run prior to upgrade. Security File Transfers site: If your site has customizations running on a Controller, these must be removed prior to upgrading the Controllers to v9.40. Once the Controller is upgraded to the new controller code, vCR9.20 (Linux OS) the newer version of the customizations will need to be re-installed. All custcard DLLs prior to v8.20 are not compatible with Controller vCR8.20 or later. Once the Controller is upgraded to the new Controller version, updated DLLs may be required. Please contact Tech Support for assistance. **Pre-v7.10 Controllers** Pre-v7.10 Controllers are not supported from v8.50 or later of Command Centre. The Windows TLS stack cannot communicate with pre-v7.10 Controllers due to the combination of SSLv3 and AES. Pre-v7.10 Controllers will need to be upgraded to v7.10 or above before they are connected to v8.50 or later. To eliminate the chance of a site upgrading to v9.10 and then finding their Controllers are not compatible, the installer will check for pre-v7.10 Controllers. If they exist, the installer will halt and inform the technician that upgrade of the Controllers is first required. The Gallagher Pre-Upgrade Validation Tool will also identify pre-v7.10 Controllers. **Upgrading a Controller to vCR9.40** | Current controller version | Upgrade path | Approximate time | | -------------------------- | ------------------------------- | ------------------- | | v8.20 or later (Linux) | Direct upgrade to v9.40 | Less than 2 minutes | | v8.10.179 onwards (WinCE) | Direct migration to v9.10 Linux | Up to 4 minutes | | Older than v8.10.179 | Two-step upgrade | Up to 7 minutes | It is recommended that sites re-sync Controller databases when they are first migrated to Linux OS (v8.20 or later). {% hint style="info" %} Refer to `3E2203 Release Note Command Centre vEL9.40.XXXX (Upgrade Procedures).pdf` for details. {% endhint %} #### Easy upgrade from Controller 6000 to Controller 7000 The Upgrader Tool automatically configures a C7000 with your existing C6000 configuration. This reduces setup time when upgrading from Controller 6000 to Controller 7000. Upgrading to Command Centre v9.00+ unlocks the Controller 7000, which offers streamlined upgrades, advanced cyber protection, and will take you into the future with confidence. #### Check reader compatibility for mobile wallets with the FT Support Tool Mobile wallets are only supported on Gallagher Multi Tech readers. Support for mobile wallets is based on technical capability of the reader, with a change to a chipset that supports ECP occurring around 2018 (date of manufacture). The 2018 date is provided as a guideline only. From Command Centre v8.90 readers report their device attributes. The FT Support Tool can be used to report all readers that are wallet capable, their assigned door(s), and controller. The FT Support Tool is included with the Command Centre installation software in the `Utilities\FT Support Tool` directory. #### Supported operating systems Gallagher supports the following operating systems and follows the [Windows lifecycle FAQ from Microsoft](https://docs.microsoft.com/en-us/lifecycle/faq/windows). | Command Centre server | Command Centre workstation | | ------------------------- | -------------------------- | | Windows 11 Pro/Enterprise | Windows 11 Pro/Enterprise | | Windows 10 Pro/Enterprise | Windows 10 Pro/Enterprise | | Windows Server 2025 | | | Windows Server 2022 | | | Windows Server 2019 | | | Windows Server 2016 | | {% hint style="info" %} Command Centre supports virtual servers. If initial fault resolution is inconclusive, Gallagher may request error replication in a non-virtual environment. Dedicate resources to the virtual environment. Command Centre does not support installation on a Windows domain controller. {% endhint %} #### Supported databases {% hint style="warning" %} **Important:** Windows Server 2016, SQL Server 2016, and SQL Server 2017 are approaching the end of Extended Support under Microsoft's Fixed Lifecycle Policy. Microsoft will also cease support for Windows 10 Professional from 14th October 2025, under their Modern Lifecycle Policy. What this means for you: * Command Centre v9.40 will be the final version to support Windows Server 2016, SQL Server 2016, and SQL Server 2017. * Command Centre v9.40 will also be the final version to support Windows 10 Professional and 32-bit operating systems. {% endhint %} #### Command Centre licensing A valid license file is required to install or upgrade Command Centre. Any new sites created after Full Release will have the latest version by default. Sites upgrading to Command Centre v9.40 from a previous version (v9.30 or earlier) will require an updated Command Centre license file. To obtain an updated license file from Sales or Technical Support, the site must have an active Software Maintenance Agreement. When Gallagher is requested by a Certified Channel Partner to update the key devices in a site license file, due to failure or removal of the key device from that site, the key device is required to be returned to the nearest Gallagher regional sales office within 30 days. Should the Channel Partner not be able to return the key device, Gallagher reserves the right to invoice the Channel Partner for the full cost of the site's Gallagher Command Centre software based on the price list in effect at the date of invoice. #### Command Centre Mobile app compatibility | Device | Operating system | | ----------------- | ---------------- | | iPhone 8 or later | iOS 15 or later | | Android | 7.0 or later | #### Command Centre Mobile Connect app compatibility | Device | Operating system | | ----------------- | ---------------- | | iPhone 8 or later | iOS 15 or later | | Android | 7.0 or later | #### Command Centre Web browser compatibility * Google Chrome version 122+ * Microsoft Edge version 122+ * Safari 17+ #### FIDO2 compatibility FIDO2 logon requires Windows 10 version 1903 or later. ### Command Centre Features and Enhancements #### AccessNow (available early 2026) **Business value:** AccessNow makes getting access simple. Users request what they need, the right people approve it, and access is granted automatically, all in minutes, not days. **Description** AccessNow is Gallagher's new cloud-native platform that automates the entire access and credential request process. It enables users to request access from any device, instantly routes requests to the right approvers, and provisions access automatically in Command Centre once approved. With its intuitive, no-code workflow builder, security teams can easily design and customise automation for every type of request they receive. **Benefits** AccessNow makes getting access simple. Users request what they need, the right people approve it, and access is granted automatically, all in minutes, not days. Security teams no longer waste time on repetitive admin, approvals are accurate and traceable, and everyone enjoys a faster, smoother experience.
**AccessNow annual subscription overview** AccessNow is provided as an annual subscription service with a two-part pricing structure: * **Workflow Licensing (each)**\ Charges apply for each automated use case (also referred to as a workflow), such as employee credential issuance, or access request and provisioning etc. * C16110 – ACCESSNOW WORKFLOW (EACH): includes a Workflow, 1000 Requests, and one-off integration with the Command Centre. * `[Feature] AccessNow Command Centre Integration = 1` * **Request Packs**\ Charges also apply based on the volume of requests processed through AccessNow. Available packs include: * C16111 – ACCESSNOW SMALL REQUEST PACK (1000): pack of 1,000 requests. * C16112 – ACCESSNOW LARGE REQUEST PACK (30000): pack of 30,000 requests. **AccessNow requirements and constraints** To learn about the requirements and constraints of the service visit: [AccessNow requirements and constraints](https://help.security.gallagher.com/enterprise/help-resources/accessnow-requirements-and-constraints) **AccessNow account setup instructions** AccessNow is a SaaS platform that requires an account to be created before use. This account is then linked to Command Centre via an API key. To request a new account, please follow these steps: 1. **Contact your Gallagher Business Development Manager** to initiate the request. 2. **Submit a Purchase Order (PO)** for the service. 3. **Complete the onboarding form** available at: Once these steps are completed, your account will be provisioned and integrated accordingly. #### Bulk random selection **Business value:** Ensure site compliance by randomly selecting Cardholders without bias for random Drug and Alcohol testing. **Description** Bulk Random Selection enhances Gallagher's existing controller-based random selection solution. It supports ad hoc, scheduled, and event-driven server-based selection of filtered cardholders. **Benefits** Cardholders can be selected before or during a shift to support health and safety requirements. Gallagher cardholder filtering and randomized selection support unbiased drug and alcohol testing independently from reader selection. **Details** Random Selection was introduced in Command Centre v8.30 as a controller-based feature to randomly select Cardholders as they accessed a site area at a Gallagher reader. Bulk Random Selection complements the original Random Selection feature by independently selecting Cardholders from a pool of filtered Cardholders. The rich filtering (also available in Cardholder Bulk Change, Reporting, and Cardholder Viewer Advanced Search) can select Cardholders by Division, Access Group, Location, Competency Status, Personal Data Field, and many other attributes.
The Cardholder last entered Access Zone filter has been modified to optionally (or exclusively) include Cardholders who are Outside the System. This filter allows selection of Cardholders based on their current location. Sites can therefore randomly select Cardholders before, during, or after attendance at the workplace.
**Operation** A privileged operator can run a Bulk Random Selection from: * The Random Selection admin viewer * A Status tile * A Site Plan viewer * A Site Plan tile * A Macro **Privileges** * An operator requires **Run Bulk Random Selection** in the division of the Bulk Random Selection item, to run a bulk random selection, and if required change the probability of selection, and the maximum Cardholders selected. * An operator requires **Edit Random Selection** (existing privilege) in the division of the Bulk Random Selection item to create, edit or delete a Bulk Random Selection item. * An operator requires **View Random Selection** (existing privilege) in the division of the Bulk Random Selection item to view a Bulk Random Selection item. * An operator requires **Edit Macros** and **Run Bulk Random Selection** in the division of the Bulk Random Selection item to create, edit or delete a macro used to run a Bulk Random Selection. **Reporting** The Cardholder report includes Random Selection columns that now support both controller-based Random Selection and Bulk Random Selection: * Random Selection Name * Last Selected Time * Last Selected Event Summary * Last Selected Time (Random Selection Name) {% hint style="info" %} Do not combine reports using these Random Selection columns with event columns or event filters. {% endhint %} Two filters also support both types of random selection: * Cardholder Random Selection * Cardholder Last Random Selection Time This allows two reports to be configured. The first report example shows data in 'per selection' format where data on the same row is related to the selection event. This report can be grouped.
The second report example shows data in a flat structure where each row contains multiple random selection items. It is not recommended to group this report. A requirement exists to add Access Group or Card Type columns when filtering by these items.
**Licensing** Bulk Random Selection is included in the existing controller-based Random Selection license. #### Manual Access Events **Business value:** Improve Tagboard and Evacuation Report location, and correct fatigue management calculations. **Description** Privileged operators can now initiate historical movement events from a Cardholder Viewer. **Benefits** When cardholders tailgate entering or exiting a site, manually creating historical movement events can help: * Improve Tagboard and Evacuation Report location (when the event is the most recent movement). * Correct fatigue management calculations to enforce required rest-from-work policies. **Details** In the Cardholder Viewer, the previously named Action menu item 'Move to Location' has been renamed 'Create Manual Access Event'. This control now supports moving Cardholders at the time of the action (Now), or historically (In the past). Historical movement actions will only update the Cardholder location if the event is the most recent movement event.
**Events** Two new events capture historical movement events and complement the two existing events: * Operator moved Cardholder * Operator moved Cardholder to outside of the system * Operator moved Cardholder historically * Operator moved Cardholder to outside of the system historically **Privileges** An operator requires **Manage Historical Cardholder Location** privilege in the division of the Cardholder and the target Access Zone (or any Access Zone when moving to Outside the system), to move a Cardholder historically. **Licensing** Manually moving cardholders currently or historically does not require explicit licensing. #### Half Cycle Lock Type **Business value:** Reduce the risk of unauthorized access and accidental or unauthorized unlocking to increase control over secure areas. **Description** The Half-Cycle Lock is a security mechanism commonly used in correctional facilities. When a Cardholder is granted access at a Half-Cycle door, the unlocking process is initiated. The lock completes a half-cycle, meaning the bolt is retracted, but the lock is not fully disengaged. The door must be opened by its handle, often with a key, to fully unlock. When doors with the Half-Cycle Lock Type are unlocked (with a valid credential or override), they remain unlocked until the door is opened and then closed, or overridden to locked, upon which the door locks. **Benefits** The Half-Cycle Lock reduces risk of unauthorized access. The mechanism prevents accidental or unauthorized unlocking, increasing control over secure areas. The lock mechanism streamlines the unlocking and locking processes saving time and increasing efficiency at correctional facilities. Half-Cycle locks help facilities meet regulatory requirements and industry standards. **Details** *Configuration* For doors configured with Half-Cycle lock type: * Door Open Too Long warnings and alarms can optionally be disabled. * Door unlock time and Extended access time settings are disabled and not applicable. * Reader LEDs flash green on access granted but then revert to solid green when doors are unlocked but remain closed. Note: T2x terminals will only exhibit this behaviour if configured as Cardax IV readers.
*Overrides and privileges* A new 'Lock Door' override and 'Override - Lock door' privilege have been introduced. An operator with this privilege in the Door's division can override a Half-Cycle lock type Door to locked. A Half-Cycle door will remain unlocked after access is granted until either it is opened and shut, or the Lock Door override is used. The existing 'Open Door' override and 'Override - Open door' privilege can be used to override a Half-Cycle lock type Door to unlocked. *Licensing* Half-Cycle Lock Type is available with a standard Door license. #### Jacques intercom monitoring **Business value:** Discreetly monitor conversations and enhance surveillance in sensitive areas. **Description** Gallagher's Jacques Intercom integration now supports Intercom Monitoring allowing an operator to put an intercom into a listen-only state. Intercoms can also be isolated from a Status tile and Site Plan tile (but not a Site Plan Viewer). Incoming intercom calls are blocked when an intercom is isolated. **Benefits** Operators can discreetly monitor conversations or other sounds from targeted areas. This feature enhances surveillance capabilities in sensitive areas. **Details** An operator can initiate a monitoring call from a: * Jacques Intercom Viewer * Status tile * Site Plan tile or Site Plan viewer Monitor-only calls cannot be placed on hold, nor forwarded to other workstations/operators.
**Privileges** An operator requires the **Monitor Intercom** and **View Site** privileges in the division of the intercom device to use this functionality. **Licensing** Jacques intercom monitoring is included in the existing Jacques license. #### Automatic Workstation Routing **Business value:** Improve location handover procedures and minimize delays and errors. **Description** Workstation Routing was introduced in v7.30 allowing system handover between control rooms where responsibility for certain functions transfers between locations regularly. Command Centre v9.40 introduces automation to the routing behaviour. When operators log in to remote workstations, routing automatically transfers functions to the remote operators. When all operators are logged out of the remote locations, routing automatically returns function to the central/local control room. **Benefits** Workstation Routing is used predominantly in the Corrections market, to transfer responsibility to and from remote control rooms at various times of day. Automation of routing ensures that responsibility coincides with operator presence improving location handover procedures and minimising delays and errors. Operators are assured of responsibility at time of login and logout. **Details** Previously, routing direction was interchangeable i.e., Group A and Group B were directionless. With Automatic Workstation Routing the 'central' workstations are represented as Group A and the 'remote' workstations as Group B. The feature introduces a new 'Route Automatically' option actionable from: * The Workstation Routing Viewer * Site Plans (Tile and Viewer) * Status Tile When routing is configured automatically: * When all Group B workstations are logged off Command Centre, routing to Group A (central) occurs automatically. * When at least one Group B workstation is logged onto Command Centre, routing to Group B (remote) occurs automatically.
Workstation Routing items can be configured to display the highest priority alarm from any configured division. While a Workstation Routing item is automatically routed to Group B, it displays on Site Plans the current highest priority alarm of all items in the Divisions assigned to its 'Alarm Alert Divisions' tab. The same applies to shapes with the Workstation Routing item as an Associated Item. **Privileges** | Privilege | Description (and previous name) | | ---------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Configure Workstation Routing** | Configure Workstation Routing items (no change). | | **Manage Workstation Routing** | Perform all Overrides on Workstation Routing items, including Disable Workstation Routing and Route Automatically (previously named Disable Workstation Routing). | | **Use Manual Workstation Routing** | Perform Route to Group A and Route to Group B Overrides on Workstation Routing items (previously named Use Workstation Routing). | **Licensing** Automatic Workstation Routing is included in the existing Workstation Routing license. #### Workstation Disablement **Business value:** Disable and re-enable access to Command Centre or end active sessions when maintenance or security situations arise. **Description** Workstations can now be disabled and re-enabled by privileged operators to prevent access to Command Centre or to end active sessions. **Benefits** Command Centre access can be prevented at remote control room locations when maintenance or security situations arise. Active workstation sessions can also be immediately terminated returning security control to privileged central operators. **Details** Workstation access can be disabled and re-enabled in Command Centre from: * The Status and Overrides property page of each workstation item * Status Tiles * Site Plan Viewers and Tiles * Macros * Operator Sessions window/tile (Disable only)
**Privileges** The following privileges are required in the division of the workstation to disable and re-enable workstation access: * Disable Workstation * Enable Workstation #### Encoding Kiosk Application **Business value:** Read Gallagher or third-party (non-Gallagher) card data from MIFARE Classic and DESFire cards and encode the equivalent data so that cards can be used at both third-party readers and Gallagher T-series readers. **Description** The Kiosk supports: * reading Gallagher data and writing that data back to other Gallagher sectors/applications. * reading Gallagher data and writing that data back to other sectors/applications with a configurable third-party card format (non-diversified). * reading third-party data and writing that data back to other Gallagher sectors/applications. * reading third-party data and writing that data back to other sectors/applications with a configurable third-party card format (non-diversified). **Benefits** This Kiosk Application can provision cards with a second Gallagher application to allow base building and tenant systems to be accessed with a single card. The Kiosk can provision cards with a non-diversified application for use by non-Gallagher readers (e.g., elevators or key cabinets), eliminating the security risk of sharing keys. During a reader changeover, cardholders can continue to use a single card at multiple readers. **Details** The Encoding Kiosk Application has been designed to be used at a self-service "kiosk", with the intention that Cardholders will use it without assistance. The utility displays full-screen and does not require end users to physically interact with anything other than the USB card encoder. Configuration of all keys with which your existing card sectors and applications have been encoded, as well as the keys to be used to encode new sectors and applications, is required. It is also possible to customize elements of the visible Application, including a logo, the background and text colours, and the error message displayed.
**Configuration** For details of implementation recommendations and use of the configuration utility please review the C12950 Encoding Kiosk Application release note. **Licensing** The following licenses are required to use the Encoding Kiosk Application: ``` [Features] EncodingKioskApp=1 Encoding=1 [Configuration] EncodingKioskFCs=, ``` Where `Xnnnnn` and `Ynnnnn` represent the facility codes able to be used by the Encoding Kiosk app. {% hint style="info" %} This feature requires a Gallagher USB MIFARE encoder (C41007). {% endhint %} {% hint style="warning" %} **Important:** The Encoding Application does not support the Gallagher MIFARE DESFire default key seed. {% endhint %} #### Non-English Language Support **Business value:** Enable operators to use Command Centre in a language more familiar to them, and support compliance and regulatory requirements in certain regions where non-English support is mandatory. **Description** We have historically offered a variety of language packs which would be installed alongside Command Centre, providing non-English language support for the four desktop clients (Configuration Client, Command Centre Client, Visitor Management Client and Visitor Management Kiosk). This feature introduces in-built language support to the core Command Centre product without the need to install language packs after the fact. All languages are provided at no additional cost and no longer require the relevant 'Languages' licence string. **Benefits** This capability will allow operators to use our software in a language that may be more familiar to them. It will also help with meeting compliance and regulatory requirements in certain regions where non-English language support is mandatory. **Details** The supported languages are: * Arabic * Brazilian Portuguese * Canadian French * Chilean Spanish * Dutch * Simplified Chinese * Swedish * Traditional Chinese The 'Languages' licence string is now obsolete and will not be used for anything going forward. New CEIP counters have been added to allow product uptake analysis of how many operators are using each language.
#### Diagnostics install by default **Business value:** Collect diagnostic information without having to manually enable it. **Description** Command Centre 9.40 changes the way that the Diagnostics Service is installed from being opt-in to install and register, to being a core subproduct installed and registered as part of Command Centre. This allows diagnostics information to be collected without having to wait for sites to enable it, allowing the collection of improved trace data and workstation log aggregation. **Details** Diagnostics server is included in the Installation Type and ticked by default.
Post installation, the Diagnostics Service is listed on the CCFT Service Manager utility.
{% hint style="info" %} The Diagnostics service is installed automatically unless the customer explicitly disables it. {% endhint %} #### Apple Shareable Keys **Business value:** Streamline access across your site and enable access via third-party readers. **Description** This feature enables the retrieval of an Apple Read Key from Command Centre. The key can then be programmed at a supported third-party reader, allowing Apple credentials to be read at the reader. **Benefits** Using Apple credentials, an employee can authenticate at all readers onsite. **Details** An operator with the **Manage Keys** privilege can retrieve an Apple Read Key from Command Centre. Six Apple Read Keys can be retrieved. Operator events for key retrieval are supported. Key states "Active" and "Retired" allow an operator to track key usage. Each key shared must be labelled (e.g. secure print key). To program a supported third-party reader, enter the Apple TCI, Privacy Key, Read Key and Key Number into the reader configuration utility.
{% hint style="info" %} * Marking a key as "Retired" does not revoke the key. This state is to inform the operator not to share the key. * Employee Badge in Apple Wallet is a licensed feature of Command Centre. {% endhint %} #### Entra ID single sign on **Business value:** Enable secure and seamless authentication with Entra ID Single Sign On. **Description** Command Centre Client now supports integration with Microsoft Entra ID (formerly Azure AD) for single sign-on (SSO), enabling secure and seamless authentication using OpenID Connect. **Benefits** This integration supports an organization's cloud-first identity strategy. It reduces reliance on legacy AD infrastructure and centralizes access control, multi-factor authentication, and conditional access policies in Microsoft Entra. **Details** Gallagher Command Centre Client supports single sign-on (SSO) using Microsoft Entra ID. It uses OAuth 2.0 and OpenID Connect through the Microsoft Authentication Library (MSAL). From initial setup to migration, it's easy for IT teams to get started: 1. **Configure your Entra ID tenancy settings**\ Quickly set up your Command Centre application in the Microsoft Entra Admin Portal with a few straightforward steps. 2. **Set up Entra ID SSO in Command Centre**\ Enjoy full flexibility with global and individual cardholder-level controls, ideal for managing test groups and rolling out SSO in phases. 3. **Migrate from Active Directory SSO to Entra ID SSO**\ For customers currently using Active Directory SSO, Command Centre supports running both systems in parallel, ensuring a smooth and disruption-free transition. 4. **Log in with Entra ID**\ Once configured, users can select Microsoft Entra ID at login and authenticate successfully. From then on, access is seamless. Command Centre Client will automatically log them in using SSO, making day-to-day use simple and secure. **Licensing** **C12942 - LIC ENTRA ID SSO** may be licensed in two ways: * Included in the Entra ID Sync licence (no additional charge for Entra ID SSO). * Individually licensed as follows: * `[Features] EntraIDSingleSignOn=1` ### Perimeter Fence Controllers #### F5/F6 Fence Controllers (available early 2026) **Business value:** Ensure network reliability with dual-port redundancy and increased bandwidth for uninterrupted system performance. **Description** The F5/F6 Fence Controllers utilize safety software to provide a product that complies with the latest energizer safety standards (IEC 60335-2-76). While the F5/F6 models function similarly to their predecessors, there are key updates related to synchronisation and permitted installation scenarios. **Key update: Smart Sync** To meet the latest international safety standards (IEC 60335-2-76), Gallagher's F5 and F6 Fence Controllers now feature bi-directional synchronisation intelligence. If synchronisation between energizers is lost, the system will automatically reduce its output energy to a safe level of 1.2 Joules per channel or less (no more than 2.5 Joules). Once synchronisation is restored, the controller resumes normal operation without any manual intervention. This safety response is fully automated and managed by the controller's onboard safety software. Any sync-related events are reported in Gallagher Command Centre, allowing customers to monitor and respond efficiently. **Key update: Permitted installation scenarios** To maintain compliance, all installations must follow one of the approved configurations. These guidelines help ensure that every system is installed safely and performs as expected, whether it's a new site, an upgrade, or an extension. **Sites with F3 or F4 Fence Controllers** Gallagher has released an update to the synchronisation protocol that enables F3 and F4 Fence Controllers to synchronise with F5 and F6 series controllers using Smart Sync. This enhancement allows sites currently operating F3 or F4 controllers to function in the same manner as new installations, ensuring consistent and unified system performance across all controller generations. Extensions to sites where an F3 or F4 Fence Controller is installed are allowed under the following conditions: 1. **Primary synchronization source:** The F5 or F6 Fence Controller must act as the primary synchronization source. 2. **Firmware update requirement:** The firmware of the F3/F4 Fence Controllers must be updated to support enhanced synchronization before activating the F5/F6. **Stand-alone sites** If the site extension operates as a stand-alone system, the firmware update for the existing Fence Controllers must be performed via a temporary connection to Command Centre using a Controller 7000. **Sites with Trophy FT & F22 Fence Controllers** Trophy FT and F22 Fence Controllers are obsolete and cannot be updated to support the synchronisation protocol used by F5 and F6 Fence Controllers. For sites using Trophy FT or F22 that require expansion, it is strongly recommended to upgrade all fence controllers and the Command Centre to the latest generation (F5/F6). This approach is referred to as a Staggered Upgrade. To ensure maximum safety during a staggered upgrade, fence zones powered by Trophy FT or F22 that border F5/F6 zones must operate at reduced power. This allows F5/F6 controllers to enforce safe limits, enhancing site safety in accordance with the latest IEC standards.
### Controller 7000 #### Lock cycle counting **Business value:** Prevent failures, reduce downtime, and plan replacements more effectively. **Description** This feature introduces proactive maintenance capabilities by tracking the number of lock/unlock cycles per door. It enables Channel Partners and site owners to monitor lock usage and receive alarms when locks approach their rated cycle limits, helping prevent failures, reduce downtime, and plan replacements more effectively. **Product availability** * **Preventative Maintenance:** Alerts when locks approach their cycle limits (default threshold: 80%, configurable). * **Data Persistence:** Cycle counts are stored both in the controller and Command Centre, surviving restarts and offline periods. * **Customizable Thresholds:** Users can set the cycle limit and alarm percentage (e.g. 400,000 cycles with an 80% threshold). * **Flexible Notifications:** Alarms can trigger emails or SMS alerts to site owners or Channel Partners. * Controller-side persistence ensures counts are retained across reboots unless dipswitch 2 is activated.
**Details** Command Centre v9.40 adds a new Lock Cycle Counting tab to the Door FT Item configuration page. This tab allows users to: * Enable or disable lock cycle alarms. * View and configure the lock cycle count, limit and alarm threshold. * Receive notifications when a lock reaches a defined percentage of its cycle limit. The feature is off by default but continues counting in the background, allowing users to activate it later without losing historical data. *Key benefits* * Preventive Maintenance: Alerts when locks approach their cycle limits (default threshold: 80%, configurable). * Data Persistence: Cycle counts are stored both in the controller and Command Centre, surviving restarts and offline periods. * Customizable Thresholds: Users can set the cycle limit and alarm percentage (e.g., 400,000 cycles with an 80% threshold). * Flexible Notifications: Alarms can trigger emails or SMS alerts to site owners or Channel Partners. * Controller-side persistence ensures counts are retained across reboots unless dipswitch 2 is activated. *UI integration* Located between "Tag Tracking Settings" and "Challenge" in the Door FT Item. Includes: * Lock cycle count (read-only) * Lock cycle limit (editable) * Alarm threshold percentage (editable) * Enable alarms checkbox (unticked by default) *Example use case* A Channel Partner receives an alert that a mortice lock has reached 90% of its rated 750,000 cycles. They proactively schedule a replacement, avoiding a failure during peak hours and strengthening customer trust. #### Licensed support for up to 24 doors per Controller 7000 **Business value:** Support larger installations, reduce infrastructure costs, and simplify system architecture. **Description** With Command Centre v9.40, variants of the Controller 7000 (Standard, Enhanced, High Security) can now support up to 24 doors. Sites will need to purchase an 'Extended Controller Door' license per additional door connected to a controller. Without these licenses, controllers will be hard limited to 10 doors and trigger alarms if exceeded upon upgrade.
**Benefits** This enhancement expands Gallagher's controller capacity by allowing each Controller 7000 to support up to 24 doors, increased from the previous limit of 10. It enables larger installations, reduces infrastructure costs and simplifies system architecture, especially for high-density access control environments. **Details** *Key benefits* * **Scalability:** Supports larger sites. * **Cost Efficiency:** Reduces cost of network infrastructure, hardware and cabling. * **Simplified Migration:** Eases transition from legacy systems with 10+ door configurations. * **Performance Assurance:** C7000 controllers maintain access responsiveness even at full 24-door capacity. *Licensing model* * Sites can purchase a pool of 'Extended Controller Doors' licenses, assignable to any controller exceeding 10 doors. * A hard limit of 24 doors is enforced. Gallagher does not support configurations beyond this threshold. * Licensing violations trigger a License Warning alarm, and unresolved violations will place the system in read-only mode after 30 days.
*Upgrade experience* During upgrade to v9.40, installers are prompted with a terms and conditions dialog acknowledging the new door limits.
The Pre-Upgrade Tool scans for controllers exceeding 10 doors and flags them for review.
*Example use case* A large facility with 24 access points can now be managed by a single C7000 controller, streamlining deployment and reducing total cost of ownership. {% hint style="info" %} Controller 6000 is not recommended for more than 10 doors because of performance constraints. Reconfigure a C6000 exceeding the ten-door limit, or purchase an `Extended Door License` until the Controller is upgraded to a C7000. {% endhint %} #### Platform health: Linux upgrades **Business value:** Strengthened architecture to ensure long-term reliability, enhanced performance, and robust cyber security. **Description** As part of Gallagher's ongoing commitment to platform excellence, Command Centre v9.40 introduces a significant upgrade to the Linux kernel powering our Controller 6000 and Controller 7000 platforms. This update strengthens the foundation of our controller architecture, ensuring long-term reliability, enhanced performance and robust cyber security. **Benefits** * **Cyber Security First:** The upgraded kernel incorporates the latest protections and aligns with Gallagher's commitment to maintaining the highest standards of cyber security across all products. * **Optimised Performance:** Improved system responsiveness and efficiency help ensure controllers operate smoothly in demanding environments. * **Future-Ready Infrastructure:** Supports modern hardware components and prepares the platform for upcoming innovations and features. * **Platform Health and Longevity:** Reinforces Gallagher's dedication to maintaining the health and resilience of its controller platforms over time. **What this means for you** Whether you're deploying new controllers or upgrading existing ones, this kernel enhancement ensures your Gallagher system remains secure, stable, and ready to evolve with your needs. It's another step in our mission to deliver trusted, high-performance solutions that stand the test of time. #### Enhanced web server architecture for Controller 7000 **Business value:** Enhanced scalability to ensure our solutions are future-ready and meet the highest standards of cyber security. **Description** Command Centre v9.40 introduces a major upgrade to the web server architecture embedded in the Controller 7000. This enhancement reflects Gallagher's commitment to delivering secure, scalable, and future-ready solutions, ensuring our controller platforms continue to meet the highest standards of cyber security and performance. **Benefits** This enhancement significantly boosts the scalability and flexibility of Controller deployments by allowing each C7000 controller to support up to 100 inter-controller communications, up from the previous limit of 60. This enables larger, more complex controller networks without compromising performance or manageability.
#### Identify controller override **Business value:** Improve installation efficiency and technician experience by allowing the identification of specific controllers when multiple units are installed in close proximity. **Description** This feature improves installation efficiency and technician experience by allowing physical identification of a specific Controller 7000 from within Command Centre. It eliminates confusion when multiple controllers are installed in close proximity, helping installers and site managers quickly locate the correct unit. **Benefits** * **Simplifies Installation:** Technicians can visually confirm which controller is being worked on. * **No Event Raised:** The override does not affect controller status or generate events. * **Privilege Controlled:** Only operators with View Site or Edit Site privileges can access the override. * **UI Integration:** Available in the Controller Status and Override Page, Site Plan Viewer, Monitor Site Viewer, and View Status windows.
**Details** Command Centre v9.40 introduces a new override for Controller 7000 FT items: * Stop Identifying Controller * Start Identifying Controller When activated, the controller's Run LED flashes five times, repeating every three seconds until stopped. This override mimics the existing "Identify HBUS Reader" functionality and uses the same Invalid Key LED flash pattern already available in firmware. *Use with C7000 Single Door* If the C7000 Single Door is configured to turn off the status LED when the cover is installed, Start Identifying Controller override takes higher priority. {% hint style="info" %} * Only available for Controller 7000 models. * Controller must be online to receive the override. * Override does not persist or queue if the controller is offline. {% endhint %} *Example use case* During a multi-controller installation, a technician at the head end can trigger the override while a colleague in the field watches for the flashing LED to confirm the correct controller is being configured. #### Dual ethernet: Phase 1 **Business value:** Enhance network reliability and deployment flexibility. **Description** Phase 1 of the Independent Dual Ethernet feature on Controller 7000 introduces foundational capabilities that enhance network reliability and deployment flexibility. **Benefits** * **Cyber Security First:** All web server communications are now authenticated using short-lived tokens and verified through Gallagher's trusted public key infrastructure, ensuring secure and tamper-proof connections. * **Smarter Session Management:** Operator sessions are now securely managed and automatically refreshed, providing a seamless experience without compromising security. * **Modular Application Support:** The upgraded web server lays the foundation for future plug-in modules and app-based extensions, enabling faster innovation and easier deployment across Gallagher's ecosystem. * **Platform Health and Resilience:** These changes reinforce Gallagher's long-term commitment to maintaining the health and reliability of its controller platforms, ensuring they remain robust and adaptable to evolving customer needs.
#### Increase HBUS readers from 20 to 48 **Business value:** Enhanced scalability to support larger sites, and increased cost efficiency by reducing additional controller and infrastructure costs. **Description** Command Centre v9.40 introduces support for up to 48 HBUS readers on all variants of the Controller 7000. This change applies to Standard, Enhanced, and High Security models. The previous limit of 20 readers has been lifted following successful performance testing across extended cable lengths up to 500m. **Benefits** This enhancement significantly increases the scalability of Gallagher's access control deployments by doubling the number of supported HBUS readers on the Controller 7000, from 20 to 48. This will enable C7000s to support more doors. * **Scalability:** Supports larger sites with more doors and devices per controller. * **Cost Efficiency:** Reduces the need for additional controllers and associated infrastructure. **Details** *Licensing notes* * No additional licensing is required for the increased HBUS reader count. * Applies only to HBUS readers. *Example use case* A multi-building facility can now connect up to 48 HBUS readers to a single C7000 controller, streamlining access control across multiple entry points while maintaining centralized management. #### Increase OSDP readers from 16 to 32 **Business value:** Enhanced support for high-density access control deployments, broader coverage, reduced hardware overheads, and support for more flexible site configurations. **Description** Command Centre v9.40 introduces support for up to 32 OSDP readers on all variants of the Controller 7000. Each RS485 port can support up to 16 OSDP readers, and with two ports available, the total capacity per controller is now doubled. **Benefits** This enhancement significantly improves Gallagher's ability to support high-density access control deployments by increasing the number of supported OSDP readers per Controller 7000 from 16 to 32 readers. It enables broader coverage, reduces hardware overhead and supports more flexible site configurations. * **Scalability:** Supports larger installations. * **Cost Efficiency:** Reduces the need for additional controllers and associated infrastructure. * **Improved Site Takeover:** Aligns with Quick Switch functionality, allowing up to 16 doors per controller during migration scenarios. *UI and configuration updates* * The Command Centre UI now allows configuration of up to 32 OSDP readers per C7000. * A warning message will appear if more than 16 readers are assigned to a single RS485 port: *"There are too many OSDP devices assigned to this bus."* *Hardware integration* * Customers may use OSDP hubs to connect multiple readers, but the per-Controller port limit of 16 remains. *Example use case* A facility can now deploy 32 OSDP readers per Controller 7000, enabling centralized control of multiple entry points while maintaining fast and reliable access response. #### Increase inter-controller comms from 60 to 100 **Business value:** Enhanced scalability and flexibility of Controller deployments to enable larger, more complex controller networks without compromising performance or manageability. **Description** Starting with Command Centre version 9.40, all variants of the Controller 7000 will support up to 100 concurrent inter-controller communication links. This change applies to Standard, Enhanced, and High Security models. The Controller 6000 remains capped at 60 links. **Benefits** This enhancement significantly boosts the scalability and flexibility of Controller deployments by allowing each C7000 to support up to 100 inter-controller communications, up from the previous limit of 60. This enables larger, more complex controller networks without compromising performance or manageability. * **Greater Network Scalability:** Supports larger controller meshes for expansive sites. * **Improved Redundancy and Coordination:** Enhances peer-to-peer messaging for alarms, inputs, and outputs. * **Futureproofing:** Aligns with roadmap goals for high-density deployments and advanced controller features. **Details** *Compatibility notes* * C7000 units running versions prior to 9.40 will retain the previous 60-link limit. * No changes are made to C6000 controller capabilities. *Example use case* A large campus with up to 100 C7000s can now fully interlink all C7000 controllers without needing to segment or compromise on peer communication, simplifying configuration and improving system responsiveness. ### Minor Enhancements #### Nedap ANPR Lumo and Nedap DESFire Boosters in Core **Description** Command Centre v9.40 includes in core enhancements to support the Nedap ANPR Lumo Cameras and Nedap Boosters for DESFire cards, eliminating the need for a separate CustCard DLL. **Benefits: Nedap ANPR Lumo cameras** * **Simplified setup:** Operators can now enter license plates directly as text-format card numbers, eliminating the need for Universal Card Format (UCF) conversion. * **Native integration:** No need for a separate CustCard DLL, reducing complexity and maintenance overhead. * **Flexible configuration:** Supports direct Wiegand64 communication, enabling real-time access decisions based on plate recognition. * **Multi-region support:** Classifiers for New Zealand, Australia, and US plates ensure accurate recognition across geographies. **Benefits: Nedap DESFire Boosters** * **Secure vehicle access:** Enables MIFARE DESFire cards to be used with Nedap Boosters for high-assurance vehicle identification. * **Dual authentication:** Supports configurations where both vehicle and driver credentials are required for access, enhancing security. * **Streamlined configuration:** Uses a configuration card to program boosters. * **No DLL required:** Like the ANPR Lumo, this feature is now part of the core system, reducing reliance on custom software. #### Mobile Credentials support with SALTO wired Readers **Description** Command Centre v9.40 introduces support for 128-bit Wiegand data format, enabling mobile credentials to work seamlessly with wired SALTO readers and Gallagher controllers via the UBOX 4000 hardware. Command Centre now supports access and event tracking for mobile devices alongside traditional cards at SALTO wired readers set up as Gallagher Third party Wiegand readers. {% hint style="info" %} This functionality is only available in SALTO Native mode. {% endhint %} **Benefits** * **Modern credential support:** Enables mobile devices to be used for access at SALTO wired readers via 128-bit Wiegand format. * **Seamless integration:** Works with Gallagher controllers and UBOX 4000 hardware, allowing mobile and card credentials to coexist. * **Enhanced security:** Native mode supports encrypted HTTPS communication with SALTO servers, improving data protection. #### MorphoWave XP2 supported with Command Centre v9.40 **Description** Command Centre v9.40 introduces support for the MorphoWave XP2, enabling seamless integration of IDEMIA's advanced contactless 3D fingerprint scanning technology for secure, high-throughput access control. Cardholders can be identified in less than one second with a simple wave of the hand. The MorphoWave XP2 supports up to 100,000 biometric templates and offers various authentication options including biometrics, card and PIN code credentials. **Benefits** * **High-throughput access:** Identifies cardholders in under one second with a simple wave of the hand. * **Multi-factor authentication:** Supports biometrics, card, and PIN for layered security. * **Scalability:** Handles up to 100,000 biometric templates, suitable for large-scale deployments. * **Touchless experience:** Ideal for hygiene-sensitive environments and fast-moving entry points. *** *Information contained in this document is intended for general information only. While every effort has been taken to ensure accuracy as at the date of the document, there may be errors or inaccuracies and specific details may be subject to change without notice. Copyright © Gallagher Group Limited 2025. All rights reserved.* --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.security.gallagher.com/knowledge-hub/command-centre-releases/feature-summaries/command-centre-v9.40.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.