> 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/upgrade-command-centre-workstations.md).

# Upgrade Command Centre workstations

Upgrade ClickOnce and MSI Command Centre workstations after upgrading the server.

{% hint style="info" %}
**Prerequisites:** Upgrade the server first. See [Upgrading - Command Centre Procedure](broken://pages/u2ajwbbzJhLtFkCTLDSt).
{% endhint %}

Upgrade workstations **only after the server has upgraded**.

### Workstation agnostic

From **v8.10** and up, the workstation build version does not need to match the server build version. A server can go from 8.10.1092 to 8.10.1284 without touching the workstations. New builds may still carry bug fixes worth taking.

### ClickOnce installs

These are the easiest to upgrade. Start the Command Centre Client or the Configuration Client and ClickOnce runs the upgrade.

Some customisations write the information they need into the deployment folder. Check the release note for instructions.

### MSI installs

The MSI install is needed when:

* ClickOnce is not an option for the site, for example there is no file sharing across the network.
* A customisation is required on the workstation.
* Logging for fault finding is required.

The MSI installer is on the server at `C:\Program Files (x86)\Gallagher\Command Centre\Workstation`. Copy the contents of that folder to the workstation and run it there.


---

# 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/upgrade-command-centre-workstations.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.