> 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/end-of-sale-notification-for-stratus-z.md).

# Stratus ztC100i and ztC110i end of sale

Review the transition from Stratus ztC Edge 100i and 110i systems.

**Products affected:** C861730, Stratus ztC Edge 100i; C861732, Stratus ztC Edge 110i.

Stratus notified Gallagher of end of sale for the ztC Edge 100i and 110i for all regions. This is **effective immediately for all ztC100i products. The ztC110i is available until May 2022** if required.

Stratus introduced the **second generation** ztC products from 1 December 2021. Gallagher transitioned from **1 January 2022**.

The ztC200i and ztC250i offer twice the performance through:

* **Greater CPU power.** Up to 10 Intel Xeon cores for larger workloads, more thin clients, and more complex applications.
* **ECC memory.** Optimised for critical applications and data.
* **NVMe storage.** Up to 2 TB, enabling local or on-machine historians.

The part numbers **C861730** and **C861732** transitioned on 1 January 2022 to "STRATUS - ZTC EDGE 200i INC 1YR SUPPORT" and "STRATUS - ZTC EDGE 250i INC 1YR SUPPORT" respectively.

More information: [stratus.com ztC Edge](https://www.stratus.com/solutions/platforms/ztc-edge/).

***

🔗 **Related**

* [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/end-of-sale-notification-for-stratus-z.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.