> 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-hardware/controllers/controller-6000/configure/controller-6000-faqs-upgrading-factory.md).

# FAQs - Upgrading Factory WinCE Controller 6000s

Upgrade factory Controller 6000 units from Windows CE to Linux and resolve migration questions.

Frequently asked questions about upgrading factory WinCE Controller 6000s.

***

## Frequently Asked Questions

### Q1. Why does the Controller upgrade to v8.10 before migrating to Linux OS?

Factory Controllers go through a **two-step migration process**. First, they get upgraded to v8.10 Controller software where they download necessary files for Linux migration.

***

### Q2. Why do I have to revalidate the certificate after a Controller restarts following the use of Dip Switch 2?

When Dip Switch 2 is ON, the Controller will drop its configuration which includes the **pinned certificate**. When the Controller connects to the server after the restart, the certificate will not match the server, causing the Controller to remain offline and generate an **'Authentication of \[Controller] failed - invalid certificate'** alarm in Command Centre. Therefore a **'Revalidate certificate'** override is required to bring the Controller online after a restart with Dip Switch 2 ON.

See [Revalidate Certificate](/knowledge-hub/products/cc-hardware/controllers/controller-6000/configure/controller-6000-revalidate-certificate.md).

***

### Q3. Why do Controllers restart after a time zone change?

Time Zone changes do not dynamically update in all Linux OS driver modules, thereby requiring a Controller restart to take effect across the entire system.

***

## Factory firmware shipping versions

To make it easier for sites to bring controllers online to supported versions of Command Centre, Gallagher has released controllers from the factory with later firmware versions:

| Date                | What ships from factory                 |
| ------------------- | --------------------------------------- |
| From 30 June 2022   | 6000 controllers ship with **Linux OS** |
| From 30 June 2022   | Firmware **v8.20** installed on 6000s   |
| From 18 August 2023 | Firmware **v8.90** installed on 6000s   |

***

🔗 **Related**

* [Upgrading, Downgrading, Defaulting and Compatibility](/knowledge-hub/products/cc-hardware/controllers/controller-6000/configure/controller-6000-upgrading-downgrading-defaulting-compatibility.md). The full firmware compatibility matrix.
* [Upgrading WinCE to Linux](/knowledge-hub/products/cc-hardware/controllers/controller-6000/configure/controller-6000-upgrading-wince-to-linux.md). The migration procedure.
* [Revalidate Certificate](/knowledge-hub/products/cc-hardware/controllers/controller-6000/configure/controller-6000-revalidate-certificate.md). The certificate override referenced in Q2.


---

# 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-hardware/controllers/controller-6000/configure/controller-6000-faqs-upgrading-factory.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.