> 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/important-issues.md).

# Important Issues

### Introduction

When configuring a multi-server system, it is important to be aware of the following issues:

#### Setup

* Connecting Command Centre Servers to the Internet is not recommended as this would introduce potential security risks.
* All servers in a multi-server system need to be configured to get replication functioning, and they must all have their time-clocks synchronised.
* Crypt Seeds must be the same on all servers in order for cardholder's PINs to work correctly at all locations.
* The **Minimum User Code Length** (on the **User Codes and PINs** tab of the Server Properties) should be set to a higher value on all servers in a multi-server system.
* If your site has Morpho Biometric Readers installed, each server needs to have a Morpho Biometric Type set up manually, otherwise cardholders with a Biometric Type from a remote server will **not** be replicated on the local server.
* From a security standpoint, all servers in a multi-server system are considered as a single system with no trust boundary between the individual servers.

#### Divisions

* Every Division in the multi-server system will be permanently linked to the server it is created on and cannot span across other servers, (i.e. it cannot be assigned to any server other than the one it is created on).
* Items other than cardholders created on one server cannot be assigned to a Division not associated with its 'Home' server.
* A cardholder created on one server **can** be assigned to a Division on a different server in a Multi-server environment.

#### Operators

* In a multi-server system there is a separate "system operator" for each server and they cannot be renamed. This makes it difficult to identify what activities have been performed by each system operator, (e.g. in an Activity Report). Therefore, once you have used the "system operator" to initially set up operators access in a multi-server system, it is recommended that you do not use the "system operator' again.

  You cannot logon as a remote "system" account, (i.e. if the local system account is disabled, the logon will not try to use a remote system account even if it is enabled).

  You cannot disable remote system accounts. You must logon locally to the server in order to disable the system account.

  Refer to [Disabling the System Operator](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/cardholders/disabling-the-system-operator.md) for further detail.
* Configuration conflicts, (e.g. duplicate Card Numbers are used) may occur. If this happens, a configuration conflict alarm will be raised, prompting an operator to resolve the conflict manually.
* Password restrictions (set on the **Operator Defaults** tab of the Server Properties) are only applied at the server where a password is created. This means that unless password restrictions are set up identically on all servers, a non-compliant password can be used to log onto a workstation connected to any server other than the server the password was created on. For this reason, it may be advisable to set password restrictions up to be the same on all servers in the system.
* When an operator is logged onto a remote server, (e.g. monitoring remote alarms), they will show as a "Remote" session on the **Operator Sessions** tab of the Server Properties.
* Sites need to be aware that any sensitive information created and stored local to one particular server will be accessible by anyone with access to any server in the multi-server system.
* Operator lockout state does not get replicated to remote servers in a multi-server environment.

#### Limitations

* In a multi-server system that uses Visitor Management (a licensable feature), visit data does not get replicated between servers. Therefore, the Evacuation Report cannot report on remote visitors.
* It is the intention to enhance OPC in future releases so that it can function with either a single server or multiple server events. However, currently OPC Bridge, OPC CCTV and OPC Contact ID will work only using a single server within a Multi-Server environment. Each server will allow multiple OPC operators, and events will be obtained for individual servers only.
* In a multi-server system that has Morpho Biometric Readers installed, biometric inactivity is managed by each server independently, using the Morpho Biometric Type configuration unique to each server.
* You cannot connect two servers in a multi-server system if they have been created from the same template.


---

# 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/important-issues.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.
