> 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/wince-controller-6000-obsolescence.md).

# Windows CE Controller 6000 obsolescence

Access the Windows CE Controller 6000 final reminder document.

This companion advisory page carries no prose of its own. It exists to hold the Windows CE Controller 6000 notice documents.

The advisory content is on [Obsolescence notice - Windows CE obsolescence for Controller 6000](/knowledge-hub/products/product-advisories/historical-notices/obsolescence-notice-windows-ce-obsoles.md).

{% file src="/files/aHBkKEyySk5rixx3jh3z" %}
Windows CE Obsolescence Controller 6000, Customer, final reminder
{% endfile %}

A second document attached to the source page is an internal-only advisory and is not published here.

***

🔗 **Related**

* [Obsolescence notice - Windows CE obsolescence for Controller 6000](/knowledge-hub/products/product-advisories/historical-notices/obsolescence-notice-windows-ce-obsoles.md). The full advisory text, background, and options.
* [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/wince-controller-6000-obsolescence.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.