> 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/products/cc-software/troubleshoot/command-centre-connection-issues/command-centre-connection-issues-works.md).

# Workstations located across a large geographic area

[Command Centre - Connection Issues](/knowledge-hub/products/cc-software/troubleshoot/command-centre-connection-issues.md) › Workstations located across a large geographic area

Some sites need a large number of workstations to connect to the server. The best arrangement depends on geographical distribution and the customer's IS application deployment policies. The customer can choose **Click-Once**, the **Workstation Installer**, or **web-based cardholder management** (v8.80 onwards).

* **Click-Once** provides automated software updates for each Windows-logged-in operator. However, it must be applied to each unique Windows login on the same PC.
* **Gallagher recommends the Workstation Installer.** Work with the IT team to apply a silent installation deployment (using the MSI and silent installer methods) for every **major** Command Centre system upgrade (for example v8.80 to v8.90). Workstation installs do not usually need upgrading if the server upgrades to a higher **minor** build.
* If the operator's only task is cardholder management, explore the **web client** (v8.80+).

***

🔗 **Related**

* [Unable to log into Command Centre Client via IPv6](/knowledge-hub/products/cc-software/troubleshoot/command-centre-connection-issues/command-centre-connection-issues-u-2.md). IPv6 connection setup.


---

# 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/products/cc-software/troubleshoot/command-centre-connection-issues/command-centre-connection-issues-works.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.