> 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/deleting-a-remote-server-from-a-peer-to-peer-structure.md).

# Deleting a remote server from a Peer-to-Peer structure

### Introduction

In a 'Peer-to-Peer' structure, a remote server can be removed from the system, providing the license file contains `MultiServerRemoval=1`, and the operator has the "Advanced User" privilege in the appropriate division.

### Procedure

1. Check all the servers are online, and the time is synced on all of them.
2. Make sure there are no pending updates of each server, and backup all the servers in the multi-server system.
3. Disconnect the network on the server to be deleted.

   **Note:** NOT disable communications.
4. Shutdown the server to be deleted.
5. From a server in the multi-server system, 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)).
6. Highlight the remote server you want to delete.
7. **Right-click** and select **Delete**.

   A warning window displays with a checklist of the actions that need to be performed prior to deleting the server.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-1651e41682c760f0f3dbb15e2d12fef7b6be0296%2Fdeleteremoteserver.png?alt=media)
8. Go through the checklist and tick each checkbox to indicate the action has been completed, and click the **Delete \<Remote Server>** button.

   **Notes:**

   * It is recommended that operators do not add, delete or modify items (including cardholders) in a multi-server environment on any servers while running the deletion process.
   * The deletion process can be monitored by opening the properties of the server which is performing the deleting function.
9. Backup all the servers in the multi-server system again.

### Result

The server is deleted and disappears from the Services and Workstations List Window.

**Note:** Sometimes it takes a few minutes depending on how many items the server has to process.

All hardware and hardware related items from the deleted server are removed, (e.g. hardware components, Access Zones, Alarm Zones, Doors), and all other items are moved to the parent server, (e.g. Cardholders, Card Types, Access Groups, Operator Groups).


---

# 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/deleting-a-remote-server-from-a-peer-to-peer-structure.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.
