> 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/configuration-client/licensable-features/multi-server-systems.md).

# Multi-Server systems

### Introduction

The Multi-Server systems feature improves the ability of Command Centre to operate effectively in a distributed environment. This “distributed environment” may include multiple sites separated by large geographical distances and connected via low bandwidth and/or intermittently available networks.

A Multi-Server User Guide is located in the `'Documentation'` directory of the Command Centre installation files, which provides further information regarding multi-server functionality.

There are two different types of Multi-Server system structures, (i.e. 'Peer-to-Peer' structure and 'Star' structure).

#### Peer-to-Peer Structure

In a Peer-to-Peer structured multi-server system, each server communicates directly with every other server in the multi-server environment, as shown:

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-50b70490cda5600c728467be24cdfbc189b1f5eb%2Fsetupdiagram_peertopeer.png?alt=media)

#### Star structure

In a Star structured multi-server system, each server only communicates with the Parent server, (e.g. Server 02 and 03 are child servers of Parent Server 01), as shown:

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-2a0d04ea1b6bfe2b1044658a7304f9b0e4c7e7d1%2Fsetupdiagram_star.png?alt=media)

***

### Licensing

Multi-server functionality is a licensable feature of Gallagher Command Centre. Each server in the Multi-server environment must have its own unique license file, (which means that license limits are applied locally on each server), containing the following entry:

`[Features]`\
`MultiServer=1`

There are two additional entries that may also be required:

<table><thead><tr><th width="523">To allow...</th><th>License entry</th></tr></thead><tbody><tr><td>the site to change multi-server structure, (i.e. from 'Peer-to-Peer' to 'Star' structure, or vice versa), the license file for each server must also contain,</td><td><code>MultiServerHierarchy=1</code></td></tr><tr><td>a parent server to delete child servers from the system, the license file for the parent server must contain,</td><td><p><code>MultiServerRemoval=1</code></p><p><strong>Note:</strong> Child servers cannot delete other servers.</p></td></tr></tbody></table>

A server will not be able to participate in a multi-server system if its License File does not grant that privilege. Licensing is used to control which other servers a server can be connected to. A server cannot be connected to other servers unless the License File has the following:

* Multi-server enabled
* The same system Serial Number
* A unique server Serial Number

License restrictions for Command Centre items only apply to the local items on the server to which the License File applies. [Remote items](https://help.security.gallagher.com/knowledge-hub/configuration-client/glossary-of-terms.md#remote-item) are not counted when determining how many instances of a Command Centre item exist for the purpose of licensing. However, this is not so with [global items](https://help.security.gallagher.com/knowledge-hub/configuration-client/glossary-of-terms.md#global-item), as demonstrated in the following example:

**Example:**

If two servers in a multi-server system both use Photo ID, each server will need to be enabled with a valid Photo ID license.

***

Select the item below that you require further detail on:

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Important Issues](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/multi-server-systems/important-issues.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Remote Command Centre items](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/multi-server-systems/remote-command-centre-items.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Creating a Remote Server](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/multi-server-systems/creating-a-remote-server.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Switching from Peer-to-Peer structure to Star structure](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/multi-server-systems/switching-from-peer-to-peer-structure-to-star-structure.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Switching from Star structure to Peer-to-Peer structure](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/multi-server-systems/switching-from-star-structure-to-peer-to-peer-structure.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Adding a new server to a Star structure](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/multi-server-systems/adding-a-new-server-to-a-star-structure.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Overriding a Remote Server](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/multi-server-systems/overriding-a-remote-server.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Event Aggregation](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/multi-server-systems/event-aggregation.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Deleting a remote server from a Peer-to-Peer structure](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/multi-server-systems/deleting-a-remote-server-from-a-peer-to-peer-structure.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Deleting a child server from a Star structure](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/multi-server-systems/deleting-a-child-server-from-a-star-structure.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/configuration-client/licensable-features/multi-server-systems.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.
