> 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/introduction-to-command-centre/utilities.md).

# Utilities

The following additional utilities are available with the Command Centre system.

### DCOM Setup Utility

This utility is used to change or repair DCOM (Distributed Component Object Model) settings for Command Centre. Refer to the *DCOM Setup Utility Release Note* in the `'Utilities\DCOMSetupUtility'` directory of the Command Centre installation files for further detail.

### Import/Export Utility

This provides the functionality for the import and export of Cardholder details, and the import of schedules. It allows sites to link the Command Centre system to external systems, (e.g. Human Resources databases or Student Enrolment systems), without the need to re-key Cardholder information.

An *Import/Export Utility User Guide* ( **Import\_User Guide.chm** ) is provided in the `'Utilities\Import Export'` directory of the Command Centre installation files, which provides instructions on how to perform Cardholder and Schedule imports.


---

# 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/introduction-to-command-centre/utilities.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.
