> 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/deployment-resources/engineering-and-design-reference/migrate-and-upgrade/command-centre-server-upgrade-guidelines.md).

# Command Centre server upgrade guidelines

Plan, test, execute, and validate a Command Centre server upgrade.

### Purpose and audience

Upgrading a Command Centre server can be straightforward for simple installations, but complex and highly integrated sites require planning, testing, and careful sequencing. This guide provides practical best practice for planning and executing upgrades on production systems, including recommendations for test validation, roll-back preparation, and post-upgrade verification.

**Audience:** Channel Partners, site IT teams, and Gallagher engineers involved in planning or performing Command Centre upgrades.

### Scope, responsibilities and limitations

Gallagher can provide guidance for Command Centre components and supported upgrade paths. Sites remain responsible for their operating environment, including OS and application patching and external integrations.

* Gallagher guidance applies to Command Centre software, licensing, and supported upgrade sequencing.
* External systems are site-owned and may require independent vendor engagement (e.g. REST-connected systems, CCTV, lifts, middleware, EDI imports, AD/Entra connections, SIEM/VPN/AV tooling).
* If the current system is unsupported, the target environment is incompatible, or there are complex integrations/customisations, engage your Gallagher representative for in-depth support and consider Professional Services.
* If issues cause disruption during an upgrade, the Channel Partner should involve Gallagher engineers to assist.

{% hint style="warning" %}
**Important sequencing rule**

When upgrading across multiple Command Centre versions, each intermediate version must be installed sequentially. For each step: start services, confirm operation, and resolve issues before proceeding.
{% endhint %}

### Upgrade overview

Gallagher recommends maintaining your system on a current supported release and planning upgrades at least annually.

#### Benefits of upgrading

* Improved cybersecurity posture (maintenance releases may include defect fixes and CVE remediation).
* Improved functionality and performance.
* Access to new features and capabilities.

### Typical upgrade scenarios

<table><thead><tr><th width="199">Scenario</th><th>Description</th></tr></thead><tbody><tr><td><strong>Basic</strong></td><td>Command Centre only, no third-party integrations.</td></tr><tr><td><strong>With integrations</strong></td><td>Command Centre plus third-party systems (REST, CCTV, lift integrations, etc.).</td></tr></tbody></table>

### Pre-upgrade planning

#### Engage stakeholders and set expectations

* Notify your local Gallagher representative and Channel Partner of the intended upgrade window.
* Communicate planned outages and impacts to all end users.
* Identify stakeholders for integration testing (IT, security operations, vendors).

#### Validate supported upgrade path

Use the [Compatibility matrix](https://help.security.gallagher.com/knowledge-hub/deployment-resources/engineering-and-design-reference/compatibility-matrix.md) to determine required intermediate Command Centre versions and supported OS/SQL combinations. Also confirm legacy device support where applicable.

#### Environment readiness (host / VM / OS / SQL)

* Confirm OS version requirements for the target Command Centre version and apply current OS patches.
* Confirm SQL version requirements; plan SQL upgrade steps where necessary.
* For virtual machines: ensure resource allocation is dedicated, and host performance is stable.
* If sustained utilisation exceeds \~75% for CPU, disk, memory or network, remediate capacity before upgrading.
* Confirm third-party applications (AV, SIEM, VPN agents, etc.) are compatible and up to date.

#### Database sizing (SQL Express)

{% hint style="info" %}
SQL Express has a 10 GB database size limit.
{% endhint %}

Ensure your databases are comfortably below this limit before upgrading. A practical guideline is to be below \~75% capacity, because databases may expand temporarily during the upgrade. If required, migrate to SQL Standard (minimum) before upgrading Command Centre.

#### Licensing and install media

* Run the latest [Upgrade Validation Tool](https://help.security.gallagher.com/knowledge-hub/deployment-resources/support-tools-and-troubleshooting/upgrade-validation-tool.md) and remediate findings before proceeding.
* Ensure you have a valid Recovery Code and can validate it (see [Recovery Code Validation and Handling](#recovery-code-validation-and-handling)).
* Obtain test licences and required software from Gallagher Technical Support (no cost for test licences).
* Ensure install media is trusted (not marked as "untrusted" by Windows) before running installers.

### Standard pre-upgrade actions

These actions apply to both test and production upgrades.

#### Recovery Code validation and handling

* Confirm you have the current Recovery Code for the system.
* Test/validate the Recovery Code (e.g. using the Recovery Code utility in the `Bin` directory) prior to upgrade activities.
* Store the validated Recovery Code securely and remove any uncontrolled copies.

#### Housekeeping (reduce upgrade risk)

* Clear surplus/historical alarms.
* Purge pending messages from offline devices/controllers where practical.
* Remove or tidy configuration for decommissioned devices (particularly devices that may queue messages).
* Confirm controller DIP switch settings as required (e.g. DIP switch 2 off) and ensure controller firmware alignment where possible.

#### Backups (roll-back preparation)

* Perform and verify backups for roll-back: back up the `CCFTCentral` and `CCFTEvents` databases once Command Centre services are stopped (see the upgrade procedures). See [Roll-back Procedure](#roll-back-procedure) for how they are used.
* If SQL is remote, confirm backup procedures on the SQL host.
* Record current versions/build numbers for Command Centre, SQL, OS, and controller firmware.

#### Run the FTSupport tool

Run the [FT Support Tool](https://help.security.gallagher.com/knowledge-hub/deployment-resources/support-tools-and-troubleshooting/ft-support-tool.md) once Command Centre services are stopped, and store the output with the backups.

### Logging configuration for upgrade troubleshooting

Enable enhanced logging during test and production upgrade windows to support fault finding. Disable enhanced logging after successful completion to reduce resource use.

* **During the upgrade window:** enable Trace and Trace Performance in Command Centre Service Manager.
* Set Minidump type to All (3) during upgrade and validation.
* **After completion:** disable Trace/Trace Performance and set Minidump type back to normal (e.g. (1)).

### FTSupport tool

The FTSupport tool collects a great deal of detail about the Command Centre server's configuration. Its output file helps Gallagher developers with fault finding, and can also help restore a system if needed.

The tool is located in `C:\Program Files (x86)\Gallagher\Command Centre\Bin` by default (`FTSupportTool.exe`). It can be run from anywhere on the server by a Windows user that has at least read access to the Gallagher SQL instance. The output file is dumped into the same folder that it's run from, and has a date/time stamp in the file name.

Running this tool prior to an upgrade helps in two ways:

* Identifies the installed versions of Command Centre, controller firmware, customisations, plugins and more.
* Gives Gallagher developers the detail they need to resolve issues, should they need to be involved.

### Recovery Code

During installation of Command Centre, a Database Recovery Code is generated that is unique to each site. Losing this code can make restoring a backup impossible, and Gallagher cannot regenerate it if it cannot be found.

If you are unsure whether you have the correct Recovery Code, check it using the Recovery Code tool (`CCFTRecoveryCode.exe`), located by default in `C:\Program Files (x86)\Gallagher\Command Centre\Bin`.

If you cannot locate the correct Recovery Code and the Command Centre service is running, you can generate a new one. Any backups made before the new Recovery Code was generated will no longer be valid, so take a new backup immediately after generating it.

### Test environment and validation strategy

* Gallagher strongly recommends an isolated test environment prior to upgrading production.
* Replicate production parameters as closely as practicable (hosts, OS, SQL version, network characteristics).
* Use a test licence with the same feature set as production (different serial). For 8.50+, swapping the licence file is typically sufficient.
* Ensure the test system is isolated to prevent clashes (email, REST endpoints, controllers, workstations, integrations).
* Use the Anonymiser utility where appropriate to remove cloud configuration and communications details and/or swap licence serials (e.g. `-cloud`, `-comm`, `-serial`).
* Conduct a user acceptance test (UAT) on the upgraded test system, including controller upgrade and operator workflows.
* Run the end-to-end upgrade in test at least twice to build confidence in process and timings.

#### Estimating upgrade duration

Upgrade duration varies by site. The best predictor is a full test upgrade. Key drivers include database size, server performance, number of controllers, number/complexity of integrations, and whether intermediate version steps are required.

### Upgrade execution

#### What the Command Centre installer does

* Checks compatibility and halts with a warning if prerequisites are not met.
* Stops Command Centre services.
* Updates installed files and rebuilds required configuration and workstation setup content.
* Rebuilds ClickOnce deployment manifests.
* Upgrades key database components before restarting services, then completes remaining database upgrades.
* If customisations are detected, services may remain stopped until the correct customisation version is installed.

{% hint style="info" %}
During service downtime, controllers buffer events and upload aggregated messages when Command Centre returns online. Workstations will time out and must reconnect once services restart (including REST API operator sessions).
{% endhint %}

#### Test upgrade procedure (recommended)

{% stepper %}
{% step %}
**Perform pre-upgrade preparation**

Perform [Pre-Upgrade Planning](#pre-upgrade-planning) and [Standard Pre-Upgrade Actions](#standard-pre-upgrade-actions).
{% endstep %}

{% step %}
**Apply prerequisite upgrades**

Apply OS/SQL prerequisite upgrades in the required sequence (host resources → OS → SQL).
{% endstep %}

{% step %}
**Stop third-party integration communications**

Stop third-party integration communications where applicable.
{% endstep %}

{% step %}
**Reboot the server**

Reboot server if planned.
{% endstep %}

{% step %}
**Stop services and back up databases**

Stop Command Centre services and back up the `CCFTCentral` and `CCFTEvents` databases.
{% endstep %}

{% step %}
**Enable enhanced logging**

Enable enhanced logging (see [Logging Configuration](#logging-configuration-for-upgrade-troubleshooting)).
{% endstep %}

{% step %}
**Run FTSupport**

Run the FTSupport tool and store the output with the backups.
{% endstep %}

{% step %}
**Uninstall customisations**

Uninstall any customisations if present.
{% endstep %}

{% step %}
**Install the next Command Centre version**

Run the Command Centre installer for the next required version step.
{% endstep %}

{% step %}
**Install customisations**

Install any customisations required.
{% endstep %}

{% step %}
**Start and validate services**

Start services; validate operator login and baseline functionality.
{% endstep %}

{% step %}
**Validate controller upgrade and operation**

Upgrade a small set of controllers to validate controller upgrade and operation.
{% endstep %}

{% step %}
**Complete UAT**

Complete UAT, including integrations testing and workstation upgrades.
{% endstep %}

{% step %}
**Repeat for intermediate versions**

Repeat for each intermediate version step until the target version is achieved.
{% endstep %}

{% step %}
**Document findings**

Document findings, issues, and remediation actions; notify Gallagher Technical Support where needed.
{% endstep %}
{% endstepper %}

#### Production upgrade procedure

{% stepper %}
{% step %}
**Confirm test success and publish the change plan**

Confirm test upgrade success and timings; publish the production change plan and outage window.
{% endstep %}

{% step %}
**Apply OS patches and reboot**

Apply OS patches/updates and reboot (if required) prior to the upgrade window.
{% endstep %}

{% step %}
**Perform standard pre-upgrade actions**

Perform [Standard Pre-Upgrade Actions](#standard-pre-upgrade-actions).
{% endstep %}

{% step %}
**Reboot the server**

Reboot server if planned.
{% endstep %}

{% step %}
**Stop third-party integration communications**

Stop third-party integration communications as required.
{% endstep %}

{% step %}
**Stop Command Centre services**

Stop Command Centre services.
{% endstep %}

{% step %}
**Back up databases**

Back up the `CCFTCentral` and `CCFTEvents` databases.
{% endstep %}

{% step %}
**Enable enhanced logging**

Enable enhanced logging (see [Logging Configuration](#logging-configuration-for-upgrade-troubleshooting)).
{% endstep %}

{% step %}
**Run FTSupport**

Run the FTSupport tool and store the output with the backups.
{% endstep %}

{% step %}
**Uninstall customisations**

Uninstall any customisations if present.
{% endstep %}

{% step %}
**Install the next Command Centre version**

Run the Command Centre installer for the next required version step.
{% endstep %}

{% step %}
**Install customisations**

Install any customisations required.
{% endstep %}

{% step %}
**Start Command Centre services**

Start Command Centre services.
{% endstep %}

{% step %}
**Validate before proceeding**

Validate services, operator logins, and core workflows; then proceed to the next required step if applicable. If validation fails, see [Roll-back Procedure](#roll-back-procedure).
{% endstep %}

{% step %}
**Deploy workstation updates**

Deploy workstation updates (ClickOnce: on first login; MSI: manual/silent deployment).
{% endstep %}

{% step %}
**Upgrade controller firmware**

Upgrade controller firmware as soon as practicable (Upgrade Manager in Configuration Client).
{% endstep %}

{% step %}
**Complete post-upgrade validation**

Run [Post-Upgrade Validation](#post-upgrade-validation), including integration tests.
{% endstep %}

{% step %}
**Disable enhanced logging**

Disable enhanced logging once stable.
{% endstep %}
{% endstepper %}

#### Roll-back procedure

Agree the roll-back decision point in the change plan before the upgrade window: a time limit or specific failure criteria, and who makes the call.

**When to roll back**

* Command Centre services will not start or stay stable, and remediation has not resolved it within the agreed time.
* Core workflows or critical integrations fail validation and cannot be fixed within the upgrade window.

**Roll-back steps**

{% stepper %}
{% step %}
**Stop Command Centre services**

Stop Command Centre services.
{% endstep %}

{% step %}
**Uninstall the new version**

Uninstall the new Command Centre version.
{% endstep %}

{% step %}
**Reinstall the previous version and customisations**

Reinstall the previous Command Centre version and build recorded before the upgrade (must match the database version).

1. This may require reinstalling an older version of SQL if the previous Command Centre version does not support the installed SQL version.
2. Once Command Centre is installed, install the same customisation versions that were installed when the backup was taken. This must be done before the databases are restored: installing a customisation records it in the database, and because the backup still records customisations as installed, the customisation installer will not run against the restored database.
   {% endstep %}

{% step %}
**Restore the databases**

Restore the `CCFTCentral` and `CCFTEvents` backups.
{% endstep %}

{% step %}
**Start Command Centre services**

Start Command Centre services.

1. You may need to apply the Recovery Code if the services do not start.
   {% endstep %}

{% step %}
**Validate the restored version**

Validate services, operator logins, and core workflows on the previous version.
{% endstep %}

{% step %}
**Restart third-party integration communications**

Restart third-party integration communications.
{% endstep %}

{% step %}
**Confirm controller status and firmware**

Confirm controllers come online, and upgrade or downgrade their firmware to match the restored Command Centre version.
{% endstep %}

{% step %}
**Restore workstation versions**

Return any workstations already upgraded to the new version to the restored version.
{% endstep %}
{% endstepper %}

Databases must be restored to the same Command Centre version and build they came from (see [Migrating to a New Server](#migrating-to-a-new-server)).

For multi-step upgrades, decide whether to roll back to the last successful intermediate version (using the database copies taken after each step) or to the starting version.

### Special cases

#### Upgrading with remote SQL

* The Windows account performing the upgrade requires temporary **sysadmin** rights on the SQL instance for the upgrade window (then **DB Owner** thereafter).
* The same account requires temporary local administrator rights on the Command Centre server.
* For systems with customisations and remote SQL: add/remove customisations using an account with temporary administrative rights on the Command Centre server and temporary sysadmin rights on SQL.

#### Customisations

Systems with customisations recorded in the database require the matching customisation version to be installed before services will start. This section is primarily for when you are moving a Command Centre install from one server to another.

**Recommended (supported) approach**

{% stepper %}
{% step %}
**Uninstall customisations**

Uninstall customisations prior to database migration/attachment.
{% endstep %}

{% step %}
**Install Command Centre**

Install Command Centre on the new server at the same build/version as the original server.
{% endstep %}

{% step %}
**Attach databases and install customisations**

Attach the migrated databases, then install the required customisations for that build.
{% endstep %}

{% step %}
**Remove customisations before upgrading**

Once stable, remove customisations again prior to upgrading, and ensure the target version has the required customisation available.
{% endstep %}
{% endstepper %}

**Alternative (not recommended)**

Install the same customisation build as exists on the original server, then attach the original databases. For migrations, this can work but is not advised due to increased risk and supportability considerations. When rolling back an upgrade, however, this is the required order (see [Roll-back Procedure](#roll-back-procedure)).

#### Migrating to a new server

{% hint style="danger" %}
**Critical limitation**

If moving databases or restoring backups to a new Command Centre host, the new server should be installed at the same Command Centre version/build as the source server. Do not attach a database to a server on a higher Command Centre version than the database originated from; this is unsupported and not recommended.
{% endhint %}

* If retaining event history across multi-step upgrades: stop services and detach both databases; copy them to a safe location after each successful version step; then reattach to continue.
* If event history is not required: a Command Centre Configuration backup from the Configuration Client is generally sufficient for migration.
* If archives are stored on a network drive, ensure the new server has access to them.

### Post-upgrade validation

* Confirm Command Centre services are running and stable (no repeated service restarts).
* Confirm operators can log in to the Client and Configuration Client on the server.
* Confirm all controllers are online and reporting expected firmware/software versions.
* Validate event flow and alarm processing; confirm there is no unexpected backlog.
* Validate workstation and kiosk functionality after deployment.
* Restart and validate all third-party integration communications and complete integration test plans.
* Disable enhanced logging and return Minidump settings to normal once stable.
* Monitor system health and logs for an agreed stabilisation period.

### Condensed production upgrade checklist

* [ ] Communicate outage window to all end users and stakeholders.
* [ ] Agree the roll-back decision point and who makes the call.
* [ ] Confirm supported upgrade path (Compatibility Matrix) and required intermediate steps.
* [ ] Complete host/OS/SQL readiness and patching.
* [ ] Run preUpgradeValidationTool; remediate findings.
* [ ] Validate Recovery Code and store securely.
* [ ] Housekeeping: clear alarms, purge pending messages on controllers (if the version supports this), remove decommissioned/queued devices.
* [ ] Reboot server if planned.
* [ ] Stop third-party integration communications.
* [ ] Stop Command Centre services.
* [ ] Perform and verify `CCFTCentral` and `CCFTEvents` backups.
* [ ] Enable Trace/Trace Performance and set Minidump to All (3).
* [ ] Run the FTSupport tool and store the output with the backups.
* [ ] Verify install media is trusted; run the Command Centre installer for each required step.
* [ ] After each step: start services, validate logins and core function, remediate issues.
* [ ] Deploy workstation/kiosk updates (ClickOnce/MSI as applicable).
* [ ] Upgrade controller firmware (Upgrade Manager in Configuration Client).
* [ ] Run UAT and integration test plans; restart third-party integration communications.
* [ ] Disable Trace/Trace Performance and set Minidump back to normal (1).
* [ ] Record final version/build numbers and close change record.

### Reference links

* [Compatibility matrix](https://help.security.gallagher.com/knowledge-hub/deployment-resources/engineering-and-design-reference/compatibility-matrix.md)
* [Plan operating system upgrade paths](https://help.security.gallagher.com/knowledge-hub/deployment-resources/engineering-and-design-reference/migrate-and-upgrade/plan-operating-system-upgrade-paths.md)
* [Upgrade SQL Server](https://help.security.gallagher.com/knowledge-hub/deployment-resources/engineering-and-design-reference/migrate-and-upgrade/upgrade-sql-server.md)
* [Migrate Command Centre to a new server](https://help.security.gallagher.com/knowledge-hub/deployment-resources/engineering-and-design-reference/migrate-and-upgrade/migrate-command-centre-to-a-new-server.md)
* [Upgrade Command Centre workstations](https://help.security.gallagher.com/knowledge-hub/deployment-resources/engineering-and-design-reference/migrate-and-upgrade/upgrade-command-centre-workstations.md)


---

# 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/deployment-resources/engineering-and-design-reference/migrate-and-upgrade/command-centre-server-upgrade-guidelines.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.
