> 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/product-advisories/historical-notices/obsolescence-notice-windows-ce-obsoles.md).

# Windows CE obsolescence for Controller 6000

Review Windows CE Controller 6000 obsolescence and Linux migration options.

Microsoft announced that from **28 February 2022, Windows CE licenses will no longer be available to purchase**.

## Background

Controller 6000s were originally developed with **Windows CE** as the embedded operating system. They have since been updated to **Linux Embedded**, supported for all sites running **Command Centre v8.20 and above**.

Sites running **Command Centre v8.10 and below require Windows CE and do not support controllers issued with Linux**. At the time of the notice, Controller 6000s were issued with Windows CE installed, and sites on v8.20 and above performed a controller upgrade to migrate to Linux.

Gallagher invested in **advance purchases of Windows CE licenses to last until 30 June 2022**, after which Controller 6000s are issued with Linux and a **"Powered by Linux" label** is added for easy identification.

## What you need to know

* **Sites on Command Centre v8.20 and above:** no action required. After 30 June 2022, deploying new Linux-based Controller 6000s is faster and easier, with no Windows CE upgrade step.
* **Sites on Command Centre v8.10 and below** have two options:
  1. Upgrade to Command Centre v8.20 or above, which supports Linux controllers. Upgrades are available with Gallagher Care Plan.
  2. Purchase sufficient advance stock of **Windows CE controllers** to meet repair and expansion needs until they can upgrade.

From 18 November 2021 this message was communicated to customers.

From: Toby Hutchings, Senior Product Manager - Devices.

## Original notices

{% file src="/files/70hTf0DR0IFYI3Tu11cR" %}
Windows CE obsolescence Controller 6000, Channel, 4 November 2021
{% endfile %}

{% file src="/files/4wSonAj2nm0mQKWS0PfE" %}
Windows CE obsolescence Controller 6000, Channel, January reminder, 28 January 2022
{% endfile %}

{% file src="/files/squ3102JmOpUceISxkdh" %}
Windows CE Obsolescence FAQ flyer
{% endfile %}

***

🔗 **Related**

* [WinCE Controller 6000 Obsolescence](/knowledge-hub/products/product-advisories/historical-notices/wince-controller-6000-obsolescence.md). The companion advisory page and its final customer reminder.
* [Controller 6000 - FAQs - Upgrading Factory WinCE Controller 6000s](/knowledge-hub/products/cc-hardware/controllers/controller-6000/configure/controller-6000-faqs-upgrading-factory.md). How to upgrade a factory Windows CE controller.
* [Product Advisories](/knowledge-hub/products/product-advisories.md). The full register of obsolescence, security, and deprecation notices.


---

# 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/product-advisories/historical-notices/obsolescence-notice-windows-ce-obsoles.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.