> 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/creating-a-remote-server.md).

# Creating a Remote Server

### Introduction

This procedure describes how to add a remote server to a multi-server system. Typically, an operator will set up a connection between an existing server and the new server (referred to as Server 1 and Server 2 in this procedure), and the system will ensure that the information about the new server is distributed to any other servers in the system.

**Notes:**

* The connection can be configured in either direction so Server 1 could be either the new server or the existing server.
* Remote Server items can only be created if your system is licensed for multi-server, and each server in a multi-server system must have compatible license files.

***

### Before you begin

Before you begin this procedure ensure:

* you know the name and password of an operator on the other system with sufficient privileges to create a Remote Server.
* the remote server is running.
* you are logged on as an operator with the "Advanced User" privilege.

  **Note:** While the "Advanced User" privilege is required to create remote servers, to edit the properties of remote servers you only need the "Edit Site" privilege.

***

### Configuration

<details>

<summary>1. Create a 'Remote Server' for Server 2 on Server 1</summary>

1. On Server 1, click **Configure** from the menu bar, then **Services & Workstations**.

   The **Services and Workstations** List Window opens (in [grid view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/grid-view.md)).
2. **Right click** and select **New\...Remote Server**.

   By default the **General** tab displays.
3. Complete the fields as required.

   For further detail see [General tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/general-tab.md).
4. Click the **Event Response** tab, and configure as required.

   For further detail see [Event Response tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/event-response-tab.md).
5. Click the **Alarm Instructions** tab, and configure as required.

   For further detail see [Alarm Instructions tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/alarm-instructions-tab.md).
6. Click the **Setup** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-38e53ad6ef1939d547146c02f5b1b5fee8573edf%2Fremoteserver_setuptab.png?alt=media)
7. Enter the host name or IP address of the remote server in the **Host Name** field.

   (Limit = 255 characters)

   **Note:**

   The host name can be specified in any form that can be resolved by the operating system, (e.g. host name, fully qualified domain name or IP address). However, the host name should be entered in a form that can be resolved by other servers as they will need to connect to the new server.
8. Is the remote server listening on the default port?

   <table><thead><tr><th width="72">If...</th><th>then...</th></tr></thead><tbody><tr><td>yes</td><td>go to Step 9.</td></tr><tr><td>no</td><td><p>you may need to specify the port number as well, in the <strong>Port</strong> field.</p><p>(Limit = 5 digits; Range = 1 to 65535)</p></td></tr></tbody></table>
9. Alter the **Timeout** period if required. (Limit = 2 digits; Range = 1 to 99)

   **Note:** The Timeout period should not be set to anything too large as it is used by other parts of the multi-server system and could slow down multi-server functionality.
10. The **Set as Parent Server** checkbox only applies to 'Star' structure multi-server systems, where one of the remote servers is the parent server, (i.e. all the other remote servers only communicate with the parent server).

    **Note:** The 'Star' structure multi-server is a licensed feature. The **Set as Parent Server** checkbox will be disabled if your site is not licensed for the 'Star' structure.

    Is your multi-server system a 'Star' structure?

    <table><thead><tr><th width="202">If...</th><th>then...</th></tr></thead><tbody><tr><td>no,</td><td>go to Step 11.</td></tr><tr><td>yes, and this server is to be the Parent server,</td><td><ol><li><p>Check the <strong>Set as Parent Server</strong> checkbox.</p><p>The message <em>"Setting this as the Parent Server will disable communication with all other servers. Do you wish to continue?"</em> displays.</p></li><li><p>Click the <strong>Yes</strong> button.</p><p>The Aggregation fields become disabled.</p></li><li>Go to Step 13.</li></ol></td></tr></tbody></table>
11. To receive all cardholder location changes from this remote server, check the **Receive all Cardholder location changes from this remote server** checkbox.

    **Notes:**

    * This is usually only used for the purpose of Evacuation Reporting. Enabling this feature will cause increased network traffic.
    * This setting is not replicated to other sites, as it is up to the operators of those other sites to decide if they wish to receive cardholder location information from the new server, and check the checkbox.
12. Do you want to enable event aggregation?

    <table><thead><tr><th width="72">If...</th><th>then...</th></tr></thead><tbody><tr><td>yes</td><td>refer to <a href="https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/multi-server-systems/event-aggregation.md">Event Aggregation</a> for the procedure.</td></tr><tr><td>no</td><td>go to Step 12.</td></tr></tbody></table>
13. To make the initial connection to the Remote Server, click the **Apply** button.

    **Note:**

    A message will display if a connection cannot be established, for any of the following reasons:

    * the Remote Server is not running.
    * the Remote Server is inaccessible because of some firewall or network configuration.
    * the Remote Server does not have a compatible license, or is not running a compatible version of Command Centre.
    * the Remote Server has already been added to the system.
    * the Remote Server's certificate was not trusted by the system. If the certificate is correct, then click the **Yes** button and the Remote Server's certificate will be added to the list of trusted certificates.

</details>

<details>

<summary>2. Create a 'Remote Server' for Server 1 on Server 2</summary>

Repeat Steps 2 - 10 from Server 2's workstation to create a Remote Server Command Centre item for Server 1.

</details>

<details>

<summary>3. Wait for Replication to complete</summary>

If the initial connection was successful, the servers will begin replicating their configuration.

**Note:** Replication can take quite a while.

1. To monitor the progress of the replication, click the **Status and Overrides** tab of the Remote Server's property pages.

   During replication, the following progress messages appear in the **Status** field:

   <table><thead><tr><th width="306">Message</th><th>Description</th></tr></thead><tbody><tr><td><em>"&#x3C;number> change(s) waiting to be replicated"</em></td><td>This is the number of changes on the remote server that have not yet been replicated to the local server. It may be greater than zero after servers are reconnected after being offline if changes were made.</td></tr><tr><td><em>"&#x3C;number> change(s) waiting to be applied"</em></td><td>This is the number of changes that have been replicated to the local server but have not yet been applied. It may be greater than zero due to temporary delays in replication, or dependencies on not yet replicated changes, etc.</td></tr></tbody></table>

</details>

<details>

<summary>4. Configure Operator Privileges</summary>

Initially, operators will only have access to the server they were created on. To give operators access to multiple servers if required, follow the steps below:

1. Create and configure an Operator Group entirely on the remote server (including divisions and privileges). Then from the local server, using the System Operator, drag the operators on to the **Operator Membership** tab of the Operator Group.

   See [Setting up Operator Groups](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/operator-groups/setting-up-operator-groups.md) for further detail.

</details>

### Result

A Remote Server has been created.

**Note:** A Remote Server item can never be deleted from the system.

***

### Deleting Remote Servers

Remote servers can be removed from a multi-server system, providing the license file contains `MultiServerRemoval=1` and the operator has the "Advanced User" privilege in the appropriate division.

In a 'Star' structure, child servers cannot delete other servers. Only parent servers can delete a child server from the system.

Refer to [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) or [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) as appropriate for the procedure.


---

# 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/creating-a-remote-server.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.
