> 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/configure/server-configuration/server-changing-the-command-centre-ser.md).

# Changing the Command Centre server name

## This page answers

* How do you change the server name, IP, or controller IP configuration after Command Centre is installed?
* Which registry keys and config files hold the server name?
* What is the limit on the server name length?

> 🧑‍🔧 **Installer note:** if you are setting up a new server, it is always highly recommended that you set the final server name and IP address of the server **before** installing Command Centre.

A site may need to change the Command Centre server's name, its IP configuration, or the controllers' IP configuration after Command Centre has been installed and running. To avoid having to visit each controller and DIP-switch-2 reset them to clear their IP configuration, use the method below instead.

***

## Changing the server name (server)

After the server name has been changed but **prior to rebooting**, update the Command Centre registry settings:

1. Run **Regedit**.
2. Navigate to and click on the relevant key (depends on the installed Command Centre version):

   ```
   HKEY_LOCAL_MACHINE\SOFTWARE\CARDAX\Command Centre FT
   ```

   or

   ```
   HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\CARDAX\Command Centre FT
   ```

   or

   ```
   HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Gallagher\Command Centre
   ```
3. Modify each key that specifically lists the server name. Depending on the version, these may include:

   1. `DatabaseServerMachine`

   2. `EventDatabaseServer`

   3. `ServerMachine`

   4. `ServerUrl`

   > **Note:** keys 1 and 2 will likely just refer to the local SQL instance on the server itself and will not need changing (typically `.\CARDAXFT` or `.\GALLAGHER`).
4. **Reboot the server.**

***

## Changing the server name (workstations)

### Command Centre Client (server and workstations)

1. Browse to `C:\Program Files (x86)\Gallagher\Command Centre\Client`.
2. Open `CommandCentreClient.exe.config` in a text editor.
3. Find this section:

   ```xml
   <appSettings>
       <add key="ServerUri" value="opc.tcp://[ServerName]:4840/UA/CommandCentre"/>
   ```
4. Change `[ServerName]` to the new server's identity (or IP address).

### Configuration Client (server and workstations)

1. Browse to `C:\Program Files (x86)\Gallagher\Command Centre\ConfigClient`.
2. Open `CCFT.exe.config` in a text editor.
3. Find this section:

   ```xml
   </configSections>
   <settings>
       <add key="ServerUrl" value="wss://[ServerName]:8905"/>
   ```
4. Change `[ServerName]` to the new server's identity (or IP address).

Re-run the Click Once Builder and redeploy the Visitor Management Kiosk and workstations.

***

## If running 7.80 or earlier

* Update the registry on all remote Command Centre workstations.
* If running Premier / Command Centre Client and a HOST name was specified for the connection, update the `CommandCentreClient.exe.config` file.
* You may also need to run the ClientSetup `ClickOnceBuilder.exe` to update the server's details.

***

> ⚠️ **The server name cannot exceed 15 characters.** See [Microsoft's naming conventions for computers, domains, sites, and OUs](https://learn.microsoft.com/en-us/troubleshoot/windows-server/identity/naming-conventions-for-computer-domain-site-ou) for more information.

***

🔗 **Related**

* [Controller Listen Ports - Command Centre 8.50 and above](/knowledge-hub/products/cc-software/configure/server-configuration/controller-listen-ports-command-centre.md). Pushing updated server-address info to controllers after a server change.


---

# 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/configure/server-configuration/server-changing-the-command-centre-ser.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.