> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/platform/technical-previews/collector-for-igel.md).

# Collector for IGEL OS

{% hint style="warning" %}
This Technical Preview is made available to customers free of charge for their evaluation and feedback; in general availability the functionalities of the preview may be subject to additional cost and/or licensing. As such, the Technical Preview, the documentation, and any updates are provided for limited evaluation only and on an 'as-is' and 'as-available' basis without warranty of any kind.
{% endhint %}

{% hint style="warning" %}
This documentation references external sources. Nexthink does not have control over the accuracy of third-party documentation, nor any external updates or changes that might create inconsistencies with the information presented on this page. Please report any errors or inconsistencies to [Nexthink Support](https://support.nexthink.com/).
{% endhint %}

Collector for IGEL OS brings your IGEL thin clients into Nexthink alongside your Windows and macOS devices. It reports hardware and operating system inventory and device performance, so you can monitor and troubleshoot your entire device estate from one place.

Collector for IGEL OS runs on IGEL OS 12.5.0 or later. Install it as an IGEL app from the IGEL App Portal and manage it with the IGEL Universal Management Suite (UMS).

## Joining the technical preview

To participate in this technical preview, contact your Nexthink Customer Success Manager.

## Customer benefits

* **One view of all your devices.** IGEL thin clients appear in the same inventory and use the same data model as Windows and macOS devices. Filter, query, and build dashboards across all of them.
* **Accurate thin client inventory.** Keep track of models, serial numbers, CPUs, memory, disks, monitors, GPUs, and operating system versions across your thin client fleet.
* **Early problem detection.** Track CPU, memory, storage, and graphics usage over time to find overloaded or failing devices before employees report them.
* **Lifecycle and update visibility.** See when the operating system of each device was last updated and when the device last restarted.
* **Deployment with IGEL tools.** Install and configure Collector through UMS profiles, without a separate deployment tool.

## Data reported by Collector for IGEL OS

Collector for IGEL OS reports device inventory and device performance data.

### Device inventory

Collector checks the device inventory every 5 minutes and reports any changes. It also sends a full inventory every 6 hours.

<table data-search="false"><thead><tr><th>Category</th><th>Data reported</th></tr></thead><tbody><tr><td>Device identity</td><td>Device name, hardware UUID, serial numbers, manufacturer, model, and device type</td></tr><tr><td>Operating system</td><td>Name, version, platform, architecture, and the date of the last system update</td></tr><tr><td>Processors</td><td>CPU model, base frequency, number of cores, and number of logical processors</td></tr><tr><td>Memory</td><td>Installed memory</td></tr><tr><td>Storage</td><td>Disks (type, capacity, and whether the disk is bootable) and volumes (capacity and usage)</td></tr><tr><td>Displays</td><td>Connected monitors (vendor, resolution, diagonal size, and serial number)</td></tr><tr><td>Graphics</td><td>GPU name and video memory (video memory for AMD GPUs only)</td></tr><tr><td>Collector</td><td>Collector version, tags, and the first seen and last seen dates in Nexthink</td></tr><tr><td>Restarts</td><td>Date and time of the last full boot, and the number of days since then</td></tr></tbody></table>

### Device performance

Collector samples device performance every 30 seconds and reports the results in 5-minute intervals.

| Category            | Data reported                                                                                          |
| ------------------- | ------------------------------------------------------------------------------------------------------ |
| CPU                 | Usage, normalized usage, queue length, and interrupt usage                                             |
| Memory              | Used, free, and cached memory, plus swap size and swap rate                                            |
| Storage             | System and non-system drive capacity, free space, and usage, plus read and write operations per second |
| Disk responsiveness | Disk read latency, write latency, and queue length                                                     |
| Graphics            | GPU name and usage                                                                                     |
| Restarts            | Full boot events                                                                                       |

{% hint style="warning" %}
Some inventory fields depend on the data the device exposes. For example, monitor details come from the EDID data of the display, so monitors without EDID data do not appear in the inventory.
{% endhint %}

## Limitations

Collector for IGEL OS is designed for thin client use cases and does not provide full parity with Collector for Windows. The following features are not available on IGEL OS devices:

* **Data**: Collector does not report users, executions, applications and packages, services, or Windows-specific data such as crashes, hard resets, boot duration, and memory commit metrics.
* **Remote actions**: Collector cannot run remote actions on IGEL OS devices.
* **Campaigns**: IGEL OS devices do not receive campaigns.
* **Collector management**: Collector update scheduling and profile management are not available.

## Technical preview prerequisites

Before installing Collector for IGEL OS, make sure you have the following:

* IGEL OS 12.5.0 or later on the devices
* Access to the IGEL UMS Web App and to the [IGEL App Portal](https://app.igel.com/nexthink_collector)
* The customer key from the `Customer Key.txt` file in the welcome email from Nexthink
* The fully qualified domain name (FQDN) or IP address of your Nexthink instance
* The TCP port that Collector uses to connect to your Nexthink instance, `443` by default
* Network access from the devices to your Nexthink instance on that port

{% hint style="info" %}
Nexthink might remove support for an IGEL OS version around the same time IGEL drops support for it. After that, Nexthink no longer provides fixes or updates for that version.
{% endhint %}

## Installing and configuring Collector for IGEL OS

Import the Collector app from the IGEL App Portal, then deploy it to your devices through a UMS profile.

{% hint style="warning" %}
Set all three Collector parameters in the profile before you assign it to devices. Without a Collector address and a customer key, Collector cannot connect to your Nexthink instance.
{% endhint %}

1. In the UMS Web App, select **App Portal**.
2. Select **Nexthink Collector**.
3. Click **Import**.
4. Accept the End User License Agreement (EULA) and wait for the import to finish.
5. Select **Configuration > Profiles > Create new** *profile*.
6. Select **OS 12** and enter a name for the profile.
7. Click **Select Apps** and select **Nexthink Collector**.
8. Go to **Nexthink Collector > Configuration** and set the following parameters:
   * **Collector address**: the FQDN or IP address of your Nexthink instance
   * **Collector port**: the TCP port of your Nexthink instance, `443` by default
   * **Customer Key**: the customer key from your `Customer Key.txt` file
9. Save the profile.
10. Assign the profile to your devices or directories.

UMS automatically assigns the app version from the profile to the devices. The devices restart to complete the installation, and Collector starts automatically.

To change the Collector settings later, edit the profile. Collector restarts on the device and applies the new values.

## Related topics

* [Understanding Collector](/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/deploying-nexthink-in-non-vdi-environment/installing-collector/collector-overview.md)
* [Software requirements](/platform/configuring_nexthink/before-you-begin/technical-requirements/software-requirements.md)
* [IGEL: Import IGEL OS apps from the IGEL App Portal](https://kb.igel.com/en/universal-management-suite/current/how-to-import-igel-os-apps-from-the-igel-app-portal)
* [IGEL: Create and assign profiles in the IGEL UMS Web App](https://kb.igel.com/en/universal-management-suite/current/how-to-create-and-assign-profiles-in-the-igel-ums-)


---

# 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://docs.nexthink.com/platform/technical-previews/collector-for-igel.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.