> 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/site-installation/server-properties/controller-defaults.md).

# Controller Defaults

### Introduction

This tab enables you to configure system-wide software settings for Gallagher Controllers.

### Procedure

1. Open the **Command Centre Server Properties** window. [How?](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/opening-the-server-properties-window.md)
2. Click the **Controller Defaults** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-42722feed5ab554fc2857a460b8d3448c01b4351%2Fcontrollerdefaultsettingstab.png?alt=media)
3. The **Default Server Address** will affect the server address of all new and existing controllers on the site. The **Use a different address** field accepts either a DNS hostname or IP address.

   **Note:** If the "Default" server address is selected on a controller's Network property page, that controller will use the server address provided in the global default server address field.
4. The **WAN** section only needs configuring if a remote Controller needs to connect to the Command Centre server using WAN.

   Refer to [Add WAN Configuration to the Command Centre Server](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/hardware/creating-controllers/configurable-ports-nat-solution/add-wan-configuration-to-the-command-centre-server.md) for further detail.
5. If you want to change the controller diagnostic password, you can enter a new password in the **Diagnostic web interface password** field.

   **Notes:**

   * The password follows the password complexity requirements configured on the Server Properties **Operator Defaults** tab, excluding password history settings.
   * If the new password is one that is not allowed, (i.e. it is listed in either the **DisallowedPasswords.txt** or **ContextSpecificPasswords.txt** file), an error message will display.

     The **DisallowedPasswords.txt** and **ContextSpecificPasswords.txt** files are pre-installed with Command Centre to allow sites to control allowed passwords. For further details see [Preventing context specific passwords](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/getting-started/operator-passwords/preventing-context-specific-passwords.md).
   * Controllers need to be online to receive the new password. If they are offline they will not receive the new password until they are online again, or they are reset to the default with a Dip Switch 2 restart.
   * Operators who can edit the server properties can change the password. It is not necessary to know the previous password.
6. The **Controller Software** section allows Controller software to be set system-wide.

   The software that appears in the drop-down list will match the **Device Software** List Window.

   Select the required software version from the drop-down list.

   **Note:** The upgrade process may install new device software, and will change this property if it does.
7. Check the **Perform upgrades via USB** checkbox if you want the code for all Controller 6000s and 7000s to be upgraded via USB, (i.e code for Controller 6000s and 7000s cannot be upgraded via the LAN).

   **Note:** This is not applicable to the Controller 7000 Single Door.
8. Click **OK** to exit and save your changes.

   Click **Cancel** to exit without saving your changes.

   Click **Apply** to save your changes and stay in this window.


---

# 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/site-installation/server-properties/controller-defaults.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.
