> 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/deployment-resources/support-tools-and-troubleshooting/ft-support-tool.md).

# FT Support Tool

Collect Command Centre, database, computer, and network information for Technical Support.

The FT Support Tool produces a single readable text file (`FTSupportInfo.txt`) containing SQL info, Command Centre database info (controllers, versions, customisations, certificates), computer specs (disk, memory, CPU, OS, network), the licence file contents, netstat, and server PING results. Run it first when fault-finding, and send the file to Technical Support.

{% hint style="warning" %}
If the output is missing SQL database information, the running account lacks SQL access. Re-run as Administrator. The tool does not gather server details on a workstation or non-server.
{% endhint %}

Location: install media `Utilities\FT Support Tool`. Later versions are also in `…\Command Centre\Bin`. It is also on the File Transfer Site.

* Without flags, copy `FTSupportTool.exe` to a folder on the server. Then run it. `FTSupportInfo.txt` appears.
* With a flag, Shift+right-click the folder and select **Open command or PowerShell here**. Then run `FTSupportTool /NameOfFlag`, for example `/piv`, `/changesets`, or `/pendingchangesets`.

![Running FTSupportTool.exe from a PowerShell prompt in the tool's folder](https://3862776825-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Feem9HLOjc53n2VxEz3Cq%2Fuploads%2Fvs6INABfdOlJlz8sxZoB%2FSECHUB-iut-ft-support-tool-01-run-with-flag-powershell.png?alt=media\&token=4191e649-8738-4ed2-a698-93df6a58e974)


---

# 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/deployment-resources/support-tools-and-troubleshooting/ft-support-tool.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.