> 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.30.md).

# Command Centre v9.30

This page answers: what's new in Command Centre v9.30, what you need to check before upgrading, and which operating systems, databases, apps and browsers are supported.

{% hint style="info" %}
**Note:** This page details the new features within Command Centre v9.30 and does not describe the entirety of Command Centre.
{% endhint %}

[Click here to download the PDF version.](https://resources.security.gallagher.com/@api/deki/files/21618/Command_Centre_Feature_Summary_v9.30.pdf?revision=4)

## Compatibility

This section contains important notices that must be read when considering Command Centre v9.30.

### Upgrading Command Centre

Changes made to Command Centre v9.30 may impact on the configuration of sites upgrading from earlier versions. Refer to the document '3E0068 Release Note Command Centre vEL9.30.XXXX (Upgrade Procedures).pdf' for further details.

**Supported upgrade paths**

| From                 | To                   |
| -------------------- | -------------------- |
| Command Centre v8.90 | Command Centre v9.30 |
| Command Centre v9.00 | Command Centre v9.30 |
| Command Centre v9.10 | Command Centre v9.30 |
| Command Centre v9.20 | Command Centre v9.30 |

**Controller firmware compatibility**

Command Centre v9.30 supports the Controller 6000 and Controller 7000 firmware vCR9.30.&#x20;

Command Centre v9.30 is compatible with older versions of firmware for upgrade purposes only.&#x20;

No configuration changes should be made on the Controller 6000 and Controller 7000 running pre v9.30 versions once Command Centre has been upgraded. It is recommended to upgrade all controller firmware to the latest version as soon as possible.

OneLink is available from Command Centre v9.30 and is only compatible with Controller 7000.

**GBUS obsolescence: upgrade to HBUS devices**

{% hint style="warning" %}
**Important:** From Command Centre v9.10, GBUS devices will no longer be supported. Customers will need to upgrade to HBUS devices to be able to continue 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:** From Command Centre v9.30, IDEMIA Legacy (MA2G) devices will no longer be supported. Customers will need to upgrade to Native (MA5G) devices to be able to continue 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="warning" %}
**Important:** Please read the pre-upgrade information below before upgrading to v9.30.
{% endhint %}

**Pre-Upgrade Validation Tool v9.30**

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 site in the 'Command Centre and Associated Files > Utilities' folder. This utility should be run prior to upgrade.

Security File Transfers site: <https://security.gallagher.com/downloads>

If your site has customizations running on a Controller, these must be removed prior to upgrading the Controllers to v9.30. 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.30**

| Current controller version | Upgrade path                    | Approximate time    |
| -------------------------- | ------------------------------- | ------------------- |
| v8.20 or later (Linux)     | Direct upgrade to v9.30         | 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 the document '3E2203 Release Note Command Centre vEL9.30.XXXX (Upgrade Procedures).pdf' for further details.
{% endhint %}

### Easy upgrade from Controller 6000 to Controller 7000

We've made it easy to upgrade from Controller 6000 to Controller 7000 with our Upgrader Tool. The tool automatically configures a C7000 with your existing C6000 configuration, reducing your set-up time.

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 device 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 below operating systems and follows Microsoft's lifecycle. Please refer to: <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" %}
**Note:** Command Centre is supported on a virtual server. However, due to virtual server environment configuration variability, if an initial fault resolution is inconclusive, Gallagher reserves the right to request customer replication of any errors in a non-virtual environment. Resources should be dedicated to the virtual environment. Command Centre installation is not supported on a Windows domain controller.
{% endhint %}

### Supported databases

| Command Centre database                  | Minimum Service Pack |
| ---------------------------------------- | -------------------- |
| Microsoft SQL Server 2022 / 2022 Express | n/a                  |
| Microsoft SQL Server 2019 / 2019 Express | n/a                  |
| Microsoft SQL Server 2017 / 2017 Express | n/a                  |
| Microsoft SQL Server 2016 / 2016 Express | SP2                  |

{% hint style="info" %}
**Note:** SQL Server Express is the default database that is freely available for Command Centre. It is recommended that sites utilize the Microsoft SQL version that suits their present and future needs.
{% 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.30 from a previous version (v9.20 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

### OneLink

**Business value:** OneLink uses the cloud to seamlessly extend Command Centre's power to any location in the world, delivering world-class security and next-level control anywhere the customer needs it.

**Description**

OneLink securely connects a Controller 7000 to an existing Command Centre Server via the cloud, providing a simple and cost-effective way to secure even the most remote sites.

This replaces VPNs and corporate network extensions, which were previously required to integrate a remote site into Command Centre.

**Benefits**

*End users*

* **Security, anywhere:** Protect any site or asset, no matter its location, and leverage Command Centre's capabilities that go beyond traditional protection to do more from your Security Operations Center.
* **Cut deployment time:** Leverage the "Connect & Go" deployment method to roll out remote security faster, and more easily than ever before, reducing IT strain and cutting project timelines.
* **Reduces costs:** Eliminate the need to purchase additional IT hardware required to support VPNs and network extensions, along with the hidden costs associated with maintaining these connection types.
* **Future-forward:** Secure your remote sites or assets with a cloud solution that's aligned with your IT department's vision, and where the world is headed.

*Channel Partners*

* **Streamlines deployment:** The Connect & Go deployment method removes the need to configure VPNs or extend the organisation's corporate network.
* **Reduces reliance on customers' IT:** Using a cloud solution reduces the level of involvement required from the organisation's IT department.
* **Increases revenue generating opportunities:** Deploy security to locations that were once too difficult, or complex to reach.

**Details**

*Requirements*

* Must be on Command Centre v9.30+.
* Controller must be a 7000 SD, Standard, Enhanced or High Sec. C6000 is not supported.
* Controller must be able to access the internet (either by local network or cellular modem).
* Command Centre Server needs to be connected to the Gallagher Cloud (TCP Port 443).
* Controller must be running v9.30 firmware before configuration.

*Overview*

OneLink consists of two new Gallagher Cloud services: the Controller Gateway Service and the Controller Registration Service.

The Controller Gateway is a cloud-deployed version of the regular on-premises Controller Service, hosted on Amazon Web Services (AWS). It maintains a secure websockets connection with each connected controller and routes messages from those controllers to the on-premises Command Centre Server Web API via the Gallagher Cloud API Gateway.

The Controller Registration Service is a separate cloud microservice. It maintains a repository of mappings between controllers and Command Centre sites, which is accessed by the Controller Gateway in order to determine which site each controller should be connected to. A controller becomes associated with a particular site when Command Centre Server sends a registration request to the Controller Registration Service. This occurs whenever a controller is configured as a cloud controller in Command Centre.

<figure><img src="https://content.gitbook.com/content/KCdkiDwo6GvHcOdxRaN4/blobs/lUBZhosntW2arkVZLnLc/assets/v930-onelink-architecture-overview.png" alt="OneLink architecture showing the Command Centre server, Gallagher Cloud services and a remote Controller 7000"><figcaption><p>OneLink architecture overview</p></figcaption></figure>

*Pre-requisites*

The Controller connects to OneLink through port 443.

If a site has one or more OneLink connected Controllers on a local network (the same network), they can talk to one another on port 1072, but will talk through OneLink to the server.

*Bringing a Controller online via OneLink*

**Cloud configuration:** Ensure you have enabled a connection to the Gallagher Cloud before configuring a OneLink connected Controller.

<figure><img src="https://content.gitbook.com/content/KCdkiDwo6GvHcOdxRaN4/blobs/SXi5u0nB18k66AauR0Vs/assets/v930-onelink-network-ports.png" alt="Diagram of a local Command Centre server and two Controller 7000s connecting to the Gallagher Cloud on TCP 443, with the controllers linked locally on TCP 1072"><figcaption><p>OneLink connections and ports</p></figcaption></figure>

**Controller configuration:** Enter the controller MAC address and Serial Number.

Once applied the controller will be registered to OneLink (visible in the Cloud setup location).

{% hint style="info" %}
**Note:** Controllers must be brought online within 14 days of registration. All registrations expire after this period. Controllers that have connected will continue to operate once the registration has expired. Controllers that haven't been connected will need to be re-registered (click **Refresh** to re-register).
{% endhint %}

<figure><img src="https://content.gitbook.com/content/KCdkiDwo6GvHcOdxRaN4/blobs/EcOjGzpxIjTHIMGBZzEJ/assets/v930-onelink-controller-registration-flow.png" alt="Numbered flow between the local Command Centre server, Gallagher Cloud, Controller Registration Service and a Controller 7000" width="375"><figcaption><p>Controller registration flow</p></figcaption></figure>

**Controller actions:**

{% stepper %}
{% step %}
Turn on DIP Switches 2 and 7.
{% endstep %}

{% step %}
Connect the controller to the internet.
{% endstep %}

{% step %}
Power on the controller.
{% endstep %}

{% step %}
Wait until the controller comes online (2 minutes max typically).
{% endstep %}

{% step %}
Once online, turn off the DIP Switches.
{% endstep %}
{% endstepper %}

**Licensing**

OneLink is a subscription-based service and will be included as a line in the Licensing file.

Charges will automatically be included in the annual SMA quote and will be based on the number of cloud-connected Controllers configured in Command Centre.

Customers must have an active SMA/Care plan to use OneLink.

### Remove Expired Credentials

**Business value:** Improve security by automatically removing expired credentials, reducing administrative workload and minimizing risks.

**Description**

Command Centre Bulk Change now supports the removal of credentials from cardholders based on the credential state. This allows organizations to automate the clean up of expired credentials, improving credential management. This enhancement supports all card types.

**Benefits**

* **Optimizes credential management:** Maximize the value of licensed mobile credential allotments by automatically removing 'Expired' and 'Invitation Expired' credentials from cardholders.
* **Optimizes multi-tenant management:** Makes it easier to manage multi-tenanted buildings by optimizing the use of shared mobile credentials.

**Details**

Perform the following procedure to initiate a new Cardholder Bulk Change:

{% stepper %}
{% step %}
In the Command Centre Client click **New Bulk Change**.
{% endstep %}

{% step %}
Click the **Select Cardholders to Update** drop-down and select cardholders using one of the following methods:

* by Access Group
* by Cardholder
* by Criteria
  {% endstep %}

{% step %}
Click the **Select Changes to Apply** drop-down then **Card or Credential Details**.

The Change Card or Credential Details pop-up displays.

<figure><img src="https://content.gitbook.com/content/KCdkiDwo6GvHcOdxRaN4/blobs/M0oOUqPXpUzHUgZ77lEH/assets/v930-bulk-change-remove-credentials.png" alt="Change Card or Credential Details dialog with Remove Credentials selected and the credential state list open" width="375"><figcaption><p>Change Card or Credential Details</p></figcaption></figure>
{% endstep %}

{% step %}
Click the **Card Type** drop-down then select the Mobile Credential Type.
{% endstep %}

{% step %}
Click the **Remove Credentials** radio button.
{% endstep %}

{% step %}
Tick the **Only credentials with state** checkbox then select the state you want to remove from the drop-down list.
{% endstep %}

{% step %}
Click the **OK** button.
{% endstep %}

{% step %}
Click the **Save** button.
{% endstep %}
{% endstepper %}

To schedule running of the Bulk Change, refer to the Macros chapter in the Command Centre Online Help.

### Encoding Kiosk Application

**Business value:** Streamline cardholder management by encoding Gallagher and third-party cards on one system, ensuring smooth reader transitions.

**Description**

The Encoding Kiosk Application reads third-party (non-Gallagher) card data from MIFARE Classic cards and encodes equivalent Gallagher data. This allows the same card to be used on both third-party readers and Gallagher T-Series readers.

This Application eliminates the need for cardholders to carry multiple cards when a site has both Gallagher and third-party readers. During a reader changeover, cardholders can continue to use a single card at multiple readers.

The kiosk also supports:

* Reading Gallagher data and converting it to a configurable third-party format.
* Reading third-party data and writing it back in a configurable third-party format.

**Benefits**

* **Simplifies card management:** Eliminates the need for cardholders to carry multiple cards when using both Gallagher and third-party readers.
* **Makes reader transition seamless:** Allows continued use of a single card across different reader types during system upgrades.

**Details**

The Encoding Kiosk Application requires configuration of all keys with which your non-Gallagher card sectors have been encoded, as well as the source and destination sectors. It is also possible to customize elements of the visible Application, including a logo, the background and text colour, and the error message displayed.

<figure><img src="https://content.gitbook.com/content/KCdkiDwo6GvHcOdxRaN4/blobs/NkzO2Z1RniX2i2uR01BZ/assets/v930-encoding-kiosk-application.png" alt="Encoding Kiosk Application full-screen success message on a laptop" width="375"><figcaption><p>Encoding Kiosk Application</p></figcaption></figure>

**Licensing**

The following license is required to use the Encoding Kiosk Application:

```
[Features]
EncodingKioskApp=1
```

{% hint style="info" %}
This feature requires use of the Gallagher USB MIFARE encoder (C41007).
{% endhint %}

### Custom Fields for Items

**Business value:** Improve system organization by tagging items with custom field values to tailor Command Centre to your site's unique needs.

**Description**

Command Centre now allows users to define custom fields and tag items (excluding cardholders) with specific values based on those definitions.

**Benefits**

* **Enhances categorization:** Enables better organization and classification of items within Command Centre.
* **Provides greater flexibility:** Allows sites to tailor item attributes to meet their unique operational needs.

**Details**

A new configuration menu option 'Custom Field Types' is available in the Command Centre Configuration Client, under the **Configure** menu item. This page allows for the setup of the Custom Field Types that can then be assigned to all FT Items other than Cardholders. Custom Field Types can currently be configured as either a String, String List or Boolean value.

<figure><img src="https://content.gitbook.com/content/KCdkiDwo6GvHcOdxRaN4/blobs/6I4v5XRwqIx1hJhKNtMu/assets/v930-custom-field-types.png" alt="Custom Field Types dialog with Colour, Note, Size and Vented field types" width="375"><figcaption><p>Custom Field Types</p></figcaption></figure>

Once these have been configured they can be allocated to FT Items via the Custom Fields property page.

<figure><img src="https://content.gitbook.com/content/KCdkiDwo6GvHcOdxRaN4/blobs/jfT5XR4aTcJwDAeGPclq/assets/v930-custom-fields-locker-properties.png" alt="Locker properties Custom Fields page with Colour, Size, Note and Vented values" width="375"><figcaption><p>Custom Fields property page on a locker</p></figcaption></figure>

Currently these fields are not searchable or used in the system other than for allowing information to start being associated with items. These custom fields are what is used to power the new Locker Attributes functionality and in time will be expanded to be used in other parts of Command Centre.

{% hint style="info" %}
This function provides the underlying capability that allows for attributes to be assigned to lockers and locker banks.
{% endhint %}

### Locker Attributes

**Business value:** Control locker access by assigning attributes like size and function, improving organization and enhancing security.

**Description**

Enhances the Locker feature by allowing lockers to be tagged with attributes (e.g., size or function). These attributes can be used to restrict cardholders to only self-assign lockers of specific types.

**Benefits**

* **Improves access control:** Ensures that only authorized cardholders can access specific types of lockers based on predefined attributes.
* **Improves locker management:** Allows sites to categorize and allocate lockers more effectively, optimizing their use.

**Details**

As this is an extension of the existing locker functionality, it requires the locker license to enable the function.

Once Lockers have been assigned Custom Fields, the Locker Bank can be configured to provide enhanced access options from the Assignment property page. This can allow users to be restricted to a particular type of Locker or give them the option to select which type they want when badging onto the reader.

<figure><img src="https://content.gitbook.com/content/KCdkiDwo6GvHcOdxRaN4/blobs/0jpSRsfpDwA2TIL1UgTy/assets/v930-locker-bank-assignment-options.png" alt="Locker Bank properties Assignment page with access group to attribute mappings" width="375"><figcaption><p>Locker Bank Assignment property page</p></figcaption></figure>

{% hint style="info" %}
This function utilizes the new Custom Fields service to provide the attributes available for lockers.
{% endhint %}

### Vortex Integration

**Business value:** Strengthen perimeter security with real-time ground movement detection to improve response time and prevent intrusions.

**Description**

Command Centre now integrates with Vortex Systems' unattended ground sensors via a serial plugin. This allows real-time event and alarm data from these sensors to be received directly into Command Centre. Alarms can be isolated for set time periods, with aggregation similar to alarm flooding.

**Benefits**

* **Enhances security:** Detects ground movement for improved intruder detection near or within perimeter boundaries.
* **Centralizes monitoring:** Eliminates the need for multiple user interfaces by consolidating data within Command Centre.
* **Provides real-time situational awareness:** Visualizes alarms in real-time using alarm viewers and site plans.
* **Automates responses:** Uses action plans and notifications for efficient alarm management.
* **Delivers comprehensive reporting:** Leverages Command Centre's reporting capabilities for better security insights.

Integrating Vortex ground sensors with Command Centre elevates security management by providing a centralized, intelligent, and highly responsive system that enhances situational awareness, streamlines operations, and improves overall security effectiveness.

**Details**

*Configuration*

Each Vortex Receiver must be connected to a Gallagher Controller 6000 or 7000 Enhanced via the Controller's RS-232 serial port and is configured in Command Centre as an External System.

Each Vortex Ground Sensor is configured in Command Centre as an External System Item, connected to the applicable Receiver (External System).

*Alarm Viewer and isolation*

Isolated sensors do not raise new alarms in the alarm viewer. Instead, an alarm counter increases alongside an existing alarm for each device.

Vortex Ground Sensors can be isolated from an Alarm Viewer, Status Tile, Site Plan Tile or Site Plan Viewer.

<figure><img src="https://content.gitbook.com/content/KCdkiDwo6GvHcOdxRaN4/blobs/DwKxco7F0aUXAIEB6btH/assets/v930-vortex-alarm-viewer-isolation.png" alt="Alarm Viewer with Vortex sensor alarms, alarm counts and the Isolate alarm source button"><figcaption><p>Vortex alarms in the Alarm Viewer</p></figcaption></figure>

**Licensing**

The following licenses are required to use the Vortex integration:

```
[Plugin]
PluginX=ControllerRS232Vortex
PluginX=ControllerTCPVortex
```

Where `X` is a number between 0 and 999.

{% hint style="info" %}
The Vortex Integration requires a controller customization package.
{% endhint %}

### Visit Counting

**Business value:** Manage the number of visits with automated tracking, helping sites enforce security policies and meet compliance requirements.

**Description**

Visitor Management now allows sites to set limits on the number of visits a person can make within a rolling period (e.g., a maximum of 28 visits in 12 months). Configurable warnings notify visitors when they are approaching the limit.

**Benefits**

* **Enforces site policies:** Helps sites control visitor access by limiting the number of visits per person.
* **Supports vetting requirements:** Ensures individuals do not exceed permitted visit thresholds, which is valuable for sites requiring background checks for extended stays.

**Details**

This is configured in **Server Properties → Advanced**. There are three thresholds:

1. Warning
2. Alert
3. Denial

This enables reception to warn the visitor after they have reached those limits in the chosen period. The Visitor Management Client will flash a warning that the guard/receptionist needs to clear.

Visitors are able to exceed the limit if the guard/receptionist types in a reason.

<figure><img src="https://content.gitbook.com/content/KCdkiDwo6GvHcOdxRaN4/blobs/HUJR50B8ICidouIHw5dH/assets/v930-visit-counting-server-properties.png" alt="Server Properties Advanced tab with Visit Counting thresholds"><figcaption><p>Server Properties > Advanced tab > Visit Counting selected</p></figcaption></figure>

<figure><img src="https://content.gitbook.com/content/KCdkiDwo6GvHcOdxRaN4/blobs/s69ieEtpmnM3Mdtry3kX/assets/v930-visit-counting-alert-warning.png" alt="Orange Visitor Management warning showing the visitor has reached the alert threshold"><figcaption><p>Visitor Management warning when an example visitor reaches the alert threshold</p></figcaption></figure>

<figure><img src="https://content.gitbook.com/content/KCdkiDwo6GvHcOdxRaN4/blobs/Mfwhl0mp2nMUaxZeznSh/assets/v930-visit-counting-denial-warning.png" alt="Red Visitor Management warning with a justification field when the visitor reaches the denial threshold"><figcaption><p>Visitor Management warning when an example visitor reaches the denial threshold</p></figcaption></figure>

**Licensing**

The following license is required to use Visit Counting:

```
[Feature]
VisitCounting=1
```

### Outgoing Email Authentication Update

**Business value:** Ensure secure and uninterrupted email functionality with Command Centre's updated authentication for Microsoft Exchange Online. The shift to OAuth 2.0 improves security, reduces risk, and ensures compliance with Microsoft's latest standards, keeping your system protected and operational.

**Description**

Command Centre is updating the authentication method for outgoing email when integrating with Microsoft Exchange Online. The existing Basic Authentication (username and password) method is being replaced with OAuth 2.0 via Microsoft Entra ID. This update aligns with Microsoft's plan to deprecate Basic Authentication by September 2025, improving security and ensuring uninterrupted email functionality.

**Benefits**

* **Enhances security:** OAuth 2.0 uses secure access tokens instead of static credentials, reducing the risk of phishing and credential-based attacks.
* **Future-proofs:** Ensures continued support for Exchange Online email functionality after Basic Authentication deprecation.
* **Enhances access control:** OAuth 2.0 enables more precise permission settings, improving overall access security.
* **Makes transition seamless:** Simple configuration using Tenant ID, Client ID, and Client Secret from Microsoft Entra ID.
* **Complies with Microsoft standards:** Keeps Command Centre aligned with Microsoft's security and compliance framework.

**Details**

*Overview*

To ensure continued support for email functionality in Gallagher Command Centre, we are updating the authentication method used for outgoing email when integrating with Microsoft Exchange Online. This change aligns with Microsoft's plan to deprecate Basic Authentication (username and password) and transition to a more secure authentication framework, OAuth 2.0, via Microsoft Entra ID. The update is essential to maintain security and compliance with Microsoft's evolving authentication standards.

*Why are we making this change?*

Microsoft has announced that Basic Authentication for Exchange Online will be fully deprecated by September 2025. Basic Authentication, which relies on static usernames and passwords, poses security risks such as phishing attacks, credential stuffing, and brute force attempts. In response, Microsoft is enforcing OAuth 2.0, a modern, token-based authentication protocol that offers enhanced security features, including:

* Granular access control and permission scoping
* Stronger protection against unauthorized access

By adopting OAuth 2.0, Command Centre ensures that customers can continue using email functionality securely and without disruption.

*What's changing?*

Command Centre will now integrate with Microsoft Entra for Exchange Online email authentication, replacing the deprecated Basic Authentication method. OAuth 2.0 will handle authentication using secure access tokens instead of static credentials.

Customers will need to enter their Tenant ID, Client ID, and Client Secret from their Entra ID application to enable outgoing email functionality.

<figure><img src="https://content.gitbook.com/content/KCdkiDwo6GvHcOdxRaN4/blobs/vTDWTxMhHWr3eOvidjsO/assets/v930-outgoing-email-oauth-settings.png" alt="Server Properties Outgoing Email page with Exchange Online selected and Tenant ID, Client ID and Client Secret fields" width="375"><figcaption><p>Outgoing Email settings for Exchange Online</p></figcaption></figure>

*Impact on customers*

* **Exchange Online users:** Customers using Exchange Online must transition to OAuth 2.0 authentication before September 2025 to ensure uninterrupted email functionality.
* **On-premises & hybrid Exchange users:** These configurations will continue to support Basic Authentication, as Microsoft has not announced its deprecation for on-premises Exchange.
* **Other email providers (e.g., Gmail):** Basic Authentication remains available where necessary.
* ADFS and B2C configurations are not yet supported.

## Readers and Controllers

### Date of Warranty Report

**Business value:** Proactively manage hardware replacement with clear warranty insights, ensuring reliable system performance and reducing downtime.

**Description**

Generates a list of all Controllers and HBUS Devices with their warranty status. The report includes filtering options to highlight out-of-warranty devices and considers extended warranties for sites with an active Care Plan.

**Benefits**

* **Enables proactive maintenance planning:** Helps sites track hardware warranties to prevent the use of outdated equipment.
* **Optimizes hardware lifecycle:** Supports the development of a structured hardware replacement strategy.

**Details**

It is quite common for customers to be unaware of the age of their security hardware. This can lead to business risk if hardware becomes aged, out of warranty or is no longer supported by the manufacturer. From Command Centre v9.30, sites will be able to generate a Hardware Warranty report from Command Centre. This report will return a list of Controllers and HBUS devices along with the date they were manufactured and when the warranty is due to expire, or if it has expired. An additional column extends the warranty period for sites that have an active Care Plan.

{% hint style="info" %}
The warranty period starts from the day the product is manufactured.
{% endhint %}

<figure><img src="https://content.gitbook.com/content/KCdkiDwo6GvHcOdxRaN4/blobs/Z22H2ij3XYoQGcWbCVpo/assets/v930-warranty-report.png" alt="Hardware warranty report listing controllers and HBUS devices with manufacture and warranty dates" width="375"><figcaption><p>Hardware Warranty report</p></figcaption></figure>

### Support for Sensor Bus on C7000

**Business value:** Enhance monitoring accuracy by connecting Z20 Disturbance Sensors directly to Command Centre for improved security oversight.

**Description**

The Controller 7000 now supports the Sensor Bus, with compatibility backported to Command Centre v9.00 through recent updates.

**Benefits**

* **Enhances perimeter security:** Enables sites using the Z20 Disturbance Sensor to connect directly to Command Centre via the C7000, improving system functionality and security monitoring.

**Details**

*Controller versions*

| Maintenance release | Controller version |
| ------------------- | ------------------ |
| MR6                 | vCR9.00.250213b    |
| MR5                 | vCR9.10.250213a    |
| MR2                 | vCR9.20.250213a    |

### Reserve Tamper Inputs

**Business value:** Improve alarm visibility and installation efficiency of cabinets by reserving dedicated tamper detection inputs.

**Description**

Allows Controller 7000s and select input boards to reserve inputs specifically for tamper, battery and PSU failure detection in cabinets.

**Benefits**

* **Simplifies installation:** Reduces setup time and effort for installers.
* **Enhances alarm management:** Improves site plan visibility by linking tamper alarms directly to the controller, making monitoring and response more efficient.

**Details**

Controllers and I/O boards can be configured individually or a default can be set and every controller or I/O board that is created will have their inputs pre-configured. Below are some images of the configuration pages and alarm messages.

<figure><img src="https://content.gitbook.com/content/KCdkiDwo6GvHcOdxRaN4/blobs/8JsSDQHzt8cDmQbp7om1/assets/v930-reserved-inputs-controller-properties.png" alt="Controller 7000 properties Reserved Inputs tab with an input being selected for Cabinet Battery Fail" width="375"><figcaption><p>A controller's property page showing which input will be used for battery failure reporting</p></figcaption></figure>

<figure><img src="https://content.gitbook.com/content/KCdkiDwo6GvHcOdxRaN4/blobs/WNexlCG5vjuKjF1zvqm5/assets/v930-reserved-inputs-defaults.png" alt="Server Properties Reserved Input Defaults page for setting default reserved inputs by I/O module type" width="375"><figcaption><p>New tab in general properties for setting default reserved inputs when a controller or I/O module is created</p></figcaption></figure>

<figure><img src="https://content.gitbook.com/content/KCdkiDwo6GvHcOdxRaN4/blobs/biv6bBo45wotjk2Yq5Tn/assets/v930-cabinet-tamper-alarm-properties.png" alt="Alarm properties stating the cabinet hosting Controller 7000 1 has detected vibration" width="375"><figcaption><p>Alarm properties with additional information indicating which cabinet has been tampered with</p></figcaption></figure>

<figure><img src="https://content.gitbook.com/content/KCdkiDwo6GvHcOdxRaN4/blobs/jNMWSnncfzCHpEDK9i3W/assets/v930-cabinet-tamper-alarm-details.png" alt="Alarm Viewer row showing a front tamper alarm on the cabinet hosting Controller 7000 1"><figcaption><p>Alarm details example</p></figcaption></figure>

{% hint style="info" %}

* Security health check has been updated to check for failure to configure physical tampers when using an NPSA licence and to allow for physical tamper switches to be allocated in place of optical tampers.
* We don't support reserving inputs for I/O boards that already have physical tampers.
  {% endhint %}

### Cloud Assisted Server Discovery

**Business value:** Eliminate manual server setup with automated discovery, simplifying installation and improving scalability for multi-site environments.

**Description**

Enables Controllers to automatically discover their associated server address via the Gallagher Cloud. Once the server address is obtained, communication continues over the local network, not the Cloud.

**Benefits**

* **Simplifies setup:** Eliminates manual server address entry, making it faster and easier to bring Controllers online while streamlining the installation process, especially for large or distributed sites.

**Details**

*Overview*

When configuring a Controller using Automatic (DHCP), if a user selects **Cloud set up** then Command Centre will load details of the Controller (MAC and Serial Number) into the new Controller Registration Service operating in the Gallagher Cloud.

When the Controller comes online (with DIP Switches 2 and 7), it will reach out to the Controller Registration Service to discover the server it is registered to.

From that point the Controller will communicate directly with the Server over the local network. Remaining network configuration (e.g. IP address assignment) will be handled by DHCP.

The Controller will not communicate with the Server via the Cloud (if you wish to leverage this functionality see [OneLink](#onelink)).

*Command Centre configuration*

* The Command Centre Server needs to be connected to the Cloud.
* Configure your controller (MAC and Serial).
* Set to Automatic (DHCP).
* Select Cloud setup.

<figure><img src="https://content.gitbook.com/content/KCdkiDwo6GvHcOdxRaN4/blobs/ijm6M8oosxWnRhEVCwll/assets/v930-cloud-assisted-discovery-setup.png" alt="Controller 7000 properties Network page with Automatic (DHCP) and Cloud setup selected" width="375"><figcaption><p>Automatic (DHCP) with Cloud setup</p></figcaption></figure>

* Select **Automatic (DHCP)/Cloud setup** to pass the server address to the Controller via the Gallagher Cloud.
* Click **OK** to register the Controller to the Gallagher Cloud.

*Controller configuration*

* The Controller must be connected to the internet via its local network connection.
* Turn on DIP Switches 2 and 7.
* Power on the Controller.
* Once the Controller is online to Command Centre, turn off the DIP switches.

The Controller will retrieve the appropriate server address from the Cloud and connect to that server via the local network. There are no further cloud communications beyond the initial retrieval of the server address.

### NIC Bonding

**Business value:** Ensure network reliability with dual-port redundancy and increased bandwidth for uninterrupted system performance.

**Description**

NIC Bonding will be introduced in Command Centre v9.30 and backported to v9.20 via a Maintenance Release: MR1 for Controller 7000 Enhanced and MR2 for High Sec Controller 7000. This feature allows Controllers with two network ports to combine both NICs into a single logical interface. Two configurable options will be available.

**Benefits**

* **Mode 1 – Active backup:** Provides redundancy by swapping to the secondary NIC if the primary NIC were to fail.
* **Mode 4 – 802.3ad:** Also known as Link Aggregation Control Protocol (LACP), combines both NICs to act as a single interface, providing increased bandwidth and redundancy.

**Details**

NIC Bonding can be configured from the Controller FT Item:

<figure><img src="https://content.gitbook.com/content/KCdkiDwo6GvHcOdxRaN4/blobs/n0aMurO6O3JK87ZZT7uM/assets/v930-nic-bonding-configuration.png" alt="Controller 7000 properties Network page with the NIC Bonding mode drop-down open" width="375"><figcaption><p>NIC Bonding configuration</p></figcaption></figure>

### Network Connectivity Tool

**Business value:** Reduce downtime and simplify troubleshooting. Technicians can quickly test network connectivity and port status directly from Command Centre to bring controllers online faster without needing IT support.

**Description**

Allows technicians to verify if a port is open when bringing a Controller online, helping to diagnose connectivity issues.

**Benefits**

* **Provides faster troubleshooting:** Reduces delays by enabling technicians to identify port issues without needing IT support.
* **Minimizes support calls:** Helps resolve one of the most common technical challenges, reducing the need for tech support intervention.

**Details**

This feature is available from the config or debug webpage and allows a technician to ping the server in order to prove that the port is open for the Controller to connect to. This is an update to the Controller webpage and it allows someone to enter an IP address (not necessarily the server, as cross controller communication may want to be checked), and the port to communicate on (1072 is not always the listen port).

<figure><img src="https://content.gitbook.com/content/KCdkiDwo6GvHcOdxRaN4/blobs/JZVK24JIxQ7l6xY1puSn/assets/v930-controller-config-page-network-tool.png" alt="Gallagher Controller Configuration web page with a Network connectivity tools link" width="375"><figcaption><p>Controller configuration web page</p></figcaption></figure>

<figure><img src="https://content.gitbook.com/content/KCdkiDwo6GvHcOdxRaN4/blobs/3qAZ7jhHA5h2V2OmdeLQ/assets/v930-network-connectivity-test-result.png" alt="Network Connectivity Tools web page showing a successful connection to a server IP address and port" width="375"><figcaption><p>Network connectivity test result</p></figcaption></figure>

## Third Party Products and Integrations

### IDEMIA VisionPass SP

**Business value:** Deliver fast, secure, and accurate access control. Its compact design, enhanced facial recognition algorithm, and advanced cybersecurity features provide reliable access in any environment, perfect for both small and high traffic areas.

**Description**

The VisionPass SP is IDEMIA's latest facial biometric access reader, now integrated with Gallagher Command Centre. It provides fast, contactless cardholder identification and authentication, regardless of lighting conditions. The SP version includes all core VisionPass features except mask enforcement and offers a sleek, compact design.

**Benefits**

* **Enhances biometric security:** VisionPass SP features cutting-edge anti-spoofing technology, ensuring secure and seamless facial recognition.
* **Delivers high accuracy, contactless access:** VisionPass SP provides precise matching results in less than one second, offering quick and accurate facial recognition. This ensures an effortless and efficient user experience with reliable, accurate access, particularly in high throughput areas such as turnstile entry points.
* **Requires minimal behavioural adaptation and an aesthetic design:** Users do not need to change their behaviour or positioning significantly, making the authentication process more natural and intuitive. Additionally, its sleek, aesthetically pleasing design allows for easy installation into various areas.

<figure><img src="https://content.gitbook.com/content/KCdkiDwo6GvHcOdxRaN4/blobs/dOmRPdenG1ghLJ1ISKiX/assets/v930-visionpass-sp.png" alt="IDEMIA VisionPass SP reader" width="375"><figcaption><p>IDEMIA VisionPass SP</p></figcaption></figure>

<figure><img src="https://content.gitbook.com/content/KCdkiDwo6GvHcOdxRaN4/blobs/YDEg14YfDpA66iAPmU8s/assets/v930-visionpass-sp-live-feedback.png" alt="VisionPass SP live feedback display during face recognition" width="375"><figcaption><p>Live feedback</p></figcaption></figure>

<figure><img src="https://content.gitbook.com/content/KCdkiDwo6GvHcOdxRaN4/blobs/Slqvp6g0axVuV95OKpAR/assets/v930-visionpass-sp-face-changes.png" alt="VisionPass SP recognising faces with glasses, hats, masks and beards" width="375"><figcaption><p>Supports face changes</p></figcaption></figure>

### Salto Automatic Key Assignment

**Business value:** Simplify credential management by automating Salto card updates, improving efficiency for sites using Salto Space integration.

**Description**

The Salto Key Assignment feature allows Salto cards to be automatically encoded when presented at a wired Salto update point. This streamlines credential management for sites using Salto Space integration with Gallagher Command Centre.

**Benefits**

* **Increases efficiency:** Automates Gallagher Command Centre Salto card encoding, reducing manual work.
* **Better convenience for remote sites:** Enables easier credential updates without requiring direct access to encoders.
* **Better compatibility:** Supports both MIFARE Classic and DESFire cards.
* **Enhances security:** Ensures DESFire settings remain consistent across systems, with access controlled by specific operator privileges.
* **Makes migration seamless:** Simplifies the transition for existing Gallagher sites adopting our Salto integration for access control.

**Details**

Automatic Key Assignment simplifies the process of encoding Salto cards by automatically assigning key identifiers to cardholders. Here's how it works:

{% stepper %}
{% step %}
Configuration

* **Enable Automatic Key Assignment:** This is done in both the Command Centre Configuration Client and Salto ProAccess SPACE.
* **Select Key Assignment Mode:** Choose between "Card Serial Number" for MIFARE Classic cards or "In-Memory Code" for DESFire cards.
  {% endstep %}

{% step %}
Cardholder setup

* **Assign card to cardholder:** The card with the encoded card number must be assigned to the cardholder along with the correct issue number.
* **Automatic encoding:** When the cardholder badges at a wired reader connected to a Salto Server, the system automatically updates the card with the necessary access credentials.
  {% endstep %}

{% step %}
Usage

* **Single-use for auto-encoded cards:** A card set for auto encoding can only be used once. After that, a new card number must be issued.
  {% endstep %}
  {% endstepper %}

This feature is particularly useful for sites upgrading to Salto systems or using pre-encoded cards, as it streamlines the process and reduces the need for manual encoding.

*Use cases*

1. **Adding Salto access to existing Gallagher cards (MIFARE Classic):** Helps migrate existing Gallagher users to Salto access, especially useful for remote campuses.
2. **Pre-encoded Salto cards (MIFARE DESFire):** Allows sites to adopt Salto gear freely by using pre-encoded Gallagher and Salto cards.

*Configuration steps*

{% tabs %}
{% tab title="Existing Gallagher cards (MIFARE Classic)" %}
**Command Centre Configuration Client**

1. Configure Salto settings.
2. Enable Automatic Key Assignment.
3. Select "Card Serial Number" mode.
4. Edit Card Layout to include the Salto MIFARE Classic object.

**Salto ProAccess SPACE**

1. Enable Automatic Key Assignment.
2. Select "Card Serial Number" format.
   {% endtab %}

{% tab title="Pre-encoded Salto cards (DESFire)" %}
**Command Centre Configuration Client**

1. Configure Salto settings.
2. Enable Automatic Key Assignment.
3. Select "In-Memory Code" mode.
4. Configure DESFire App Key and ID.

**Salto ProAccess SPACE**

1. Enable Automatic Key Assignment.
2. Select "In-Memory Code" format.
3. Configure SAM and Issuing options to match Command Centre settings.
   {% endtab %}
   {% endtabs %}

{% hint style="info" %}
**Notes**

* **Operator privilege:** Requires "Manage Keys" operator privilege.
* **Legacy mode:** Automatic Key Assignment options are not available.
* **Wired readers only:** Only wired readers (e.g., UBox4000, CU4000s) can be used.
* **Card types:** "In-Memory Code" for Salto DESFire cards and "Card Serial Number (CSN)" for Salto MIFARE Classic cards.
* **DESFire settings:** Must be consistent across Command Centre systems.
* **Single use:** Auto-encoded cards can only be used once.
* **Salto Ncoder:** The Salto Ncoder dongle needs to be online.
  {% endhint %}

### Salto Legacy Card Migration Tool

**Business value:** Enable seamless migration from Salto Legacy Cards to Salto Native Mode, ensuring secure and uninterrupted site access.

**Description**

The Salto Legacy Card Migration Tool enables a smooth transition from Salto Legacy Cards to Salto Native Mode, simplifying the upgrade process.

**Benefits**

* **Increases efficiency:** Automates card migration, reducing manual effort.
* **Enhances security:** Ensures consistent settings and secure handling of card data.
* **Makes transition seamless:** Maintains uninterrupted functionality for cardholders during the migration.

**Details**

*Steps to use the migration tool*

{% stepper %}
{% step %}
Export legacy card data

* In the Command Centre Configuration Client, enable SALTO Native Mode and export the migration data. This data is saved as a .bin file, protected by a password.
  {% endstep %}

{% step %}
Prepare the migration tool

* Move the .bin file to the Salto Server.
* Locate and extract the Salto Legacy Card Migration Tool from the `Utilities\SaltoLegacyCardMigrationTool` folder.
* Run the tool's executable file.
  {% endstep %}

{% step %}
Database connection

* The tool's Database Connection settings are pre-filled to match Salto's default installation settings.
* Test the connection to ensure it can proceed with the migration.
  {% endstep %}

{% step %}
Import migration data

* Enter the Migration Data Password set during the export.
* Import the .bin file into the tool. A successful import will display the number of legacy cards ready for migration.
  {% endstep %}

{% step %}
Run the migration

* Click the **Run Migration** button. The tool will migrate the legacy cards to native mode.
* Return to the Command Centre Configuration Client and confirm the migration by clicking the **Migrate Legacy Cards** button.
  {% endstep %}
  {% endstepper %}

*Post-migration*

* **Native mode:** Migrated cardholders will be in native mode and continue to receive updates via update points.
* **Re-encode requirement:** Migrated cards will need re-encoding to remove re-edition warnings.

{% hint style="info" %}
**Notes**

A registry key is required to perform the migration of Salto Legacy Cards to Salto Native Mode.

Implementation of card migration is split into the steps an installer needs to perform, as follows:

* There is a file export on Command Centre which identifies all the legacy mode cards.
* This file is imported into the migration tool, which runs on the Salto Server.
* The installer confirms the migration is complete on Command Centre and the migrated user's information is mapped into Salto Server.
* Migrated cardholders should be in native mode and should continue to get updates via update points.
  {% endhint %}

## Minor Enhancements

### C7000 Aperio door limit increased

Increased the Aperio door limit for Controller 7000 from 20 to 32. With Command Centre v9.30 and above, the Controller 7000 supports 16 Aperio doors per AperioBus.

| Controller        | Aperio doors | AperioBus ports     |
| ----------------- | ------------ | ------------------- |
| C7000 Standard    | 32           | 2 x RS485 (16 each) |
| C7000 Single Door | 16           | 1 x RS485           |

***

*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. 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.30.md?ask=<question>&goal=<user_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.
