> For the complete documentation index, see [llms.txt](https://documentation.ocsinventory-ng.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.ocsinventory-ng.org/administrator-docs/agent-setup/managing-legacy-devices.md).

# Managing legacy devices

Connect and reconcile devices that use OCS Inventory Agent 2.x.

OCS Inventory Server 3.0 supports OCS Inventory Agent 2.x through `/asset/legacy/`.

Use legacy agents when devices do not meet the 3.x agent requirements.

A default legacy [inventory template](/user-docs/asset-management/inventory-and-templates.md#template-inventory) supports the legacy inventory format. Duplicate it before adding plugin data.

### Configure the legacy endpoint

Set the legacy agent URL to:

```
http(s)://server_ip:port/asset/legacy/
```

The next inventory run reports to OCS Inventory Server 3.0.

### Configure duplicate reconciliation

The legacy endpoint uses the agent `DEVICEID` (`uuid`) by default.

Some 2.x agents regenerate this value after network changes. This can create a new asset for the same device.

Open **Configurations → General → General Configuration**. Under **Server**, select **Legacy duplicate reconciliation**.

Choose one or more fields to match incoming inventory with an existing device:

* `uuid` - Default. Preserves previous behavior.
* `name`
* `serial`
* `srcmac`

All selected fields must match. The matching logic uses `AND`.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://documentation.ocsinventory-ng.org/administrator-docs/agent-setup/managing-legacy-devices.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.