> 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-management/bulk-changes/initiating-a-new-controller-6000-bulk-change.md).

# Initiating a new Controller 6000 Bulk Change

### Introduction

This procedure describes how to initiate a new Controller 6000 bulk change in Command Centre. To perform this procedure operator's need the "Bulk Change" operator privilege.

**Note:** It is recommended that you do **NOT** run multiple Controller bulk changes at once. This could mean that Controller bulk changes are run after hours. If this is the case, it is important that someone is on site when they are running in case there is a problem that needs addressing.

### Procedure (using the Wizard)

1. Click **Manage** from the menu bar, then **Bulk Changes**.

   The **Bulk Changes** List Window opens (in [grid view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/grid-view.md)).
2. **Right click** and select **New\...Controller 6000 Bulk Change**.

   The "Select Controllers" screen of the Controller 6000 Bulk Change Wizard displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-97af7d17e69903c865f5a10e2192aade21fd0144%2Fftc6000_wizard1.png?alt=media)

   All the Controller 6000s that require changing need to be placed onto this screen, by dragging and dropping them from the **Hardware** List Window, or the Find Tool can be used.

   **Notes:**

   * Only Controller 6000s can be dragged onto this grid.
   * Up to 20 Controllers can be changed at a time in a bulk change, therefore if the number of Controllers in the grid exceeds 20, the **Next** button will remain disabled until there are less than 20 Controllers in the grid.
3. Select those Controllers that need changing (from either the Hardware List Window or the Find Tool), and drag and drop them into this screen of the Wizard.
4. Click the **Next** button.

   The "Select Software" screen of the Controller 6000 Bulk Change Wizard displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-359e5c5c7648e9dbb88a9a10e663345361189109%2Fftc6000_wizard2.png?alt=media)

   Checking the **Controller Software** checkbox indicates that the software will be changed on the Controller(s). It will be possible to change the software to **-- None Selected --**, which will set the Controller(s) so that they do not have a specific software of that type, just as if it was chosen from the Controllers **Software** property page.
5. Check the appropriate checkbox and select the software from the drop-down list if required.
6. Click the **Next** button.

   The "Save and Start the Bulk Change" screen of the Controller 6000 Bulk Change Wizard displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-02ac2d4403cb897af067abb0ea49555cf2a987e6%2Fftc6000_wizard3.png?alt=media)

   The **Summary of Changes** section provides a summary of the changes for you to check before proceeding.
7. Do you want to save this bulk change and it's settings before running?

   <table><thead><tr><th width="60">If...</th><th>then...</th></tr></thead><tbody><tr><td>no</td><td>go to Step 9.</td></tr><tr><td>yes</td><td>type in a name and description.<br><br><strong>Note:</strong> The <strong>Name</strong> field is limited to 60 characters and the Description field is limited to 200 characters.</td></tr></tbody></table>
8. Click the **Save** button.

   This Bulk Change and its settings are saved and now displays in the **Bulk Changes** List Window.

   **Note:** The **Save As** button allows you to change an existing Bulk Change and re-save it as a new Bulk Change with a different name. If you open an existing saved Bulk Change and click the **Save As** button without changing the name, a message displays indicating that a Bulk Change with that name already exists.
9. Click the **Start** button.

   The "Applying Changes" screen of the Controller 6000 Bulk Change Wizard displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-e5130880db2788844dd819e728ce6036aba2d840%2Fftc6000_wizard4.png?alt=media)

   This screen shows the progress of the bulk change.

   While this screen displays, the bulk change will appear in the **Bulk Changes** List Window with a system-generated name. While in progress, the status of this bulk change will show as 'Active' in the **Bulk Changes** List Window, and if it completes successfully it will show as 'Successful', at which time the system will delete it.

   **Note:**

   While a Bulk Change of Controller 6000s is active, or if it fails, it will remain in the **Bulk Changes** List Window until an operator deletes it.

### Result

A Controller 6000 Bulk Change has been initiated.

**Note:** If the bulk change has previously been successfully run, then when the bulk change is opened again it will default to the **Select Software** screen.


---

# 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-management/bulk-changes/initiating-a-new-controller-6000-bulk-change.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.
