> For the complete documentation index, see [llms.txt](https://documentation.2pintsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.2pintsoftware.com/deployr/1.2/reference/step-definitions/apply-igel-image.md).

# Apply IGEL image

{% hint style="info" %}
This is only supported in DeployR Enterprise.
{% endhint %}

The **Apply IGEL image** step will deploy the IGEL operating system to a device.  See <https://www.igel.com> for more information.

<figure><img src="https://content.gitbook.com/content/ur9yOUrYi6pb5j4W4O2R/blobs/BPZF5yebMiEGLbvw4aX0/image.png" alt=""><figcaption></figcaption></figure>

To configure this step, select an operating system image content item containing the IGEL image file (.bin file) downloaded from <https://www.igel.com/software-downloads/igel-os-12-secure-endpoint/>, located in the "OS 12 Base System Deployment Tool for SCCM" folder.  Extract the .bin file from the downloaded .zip file and upload that as a single-file content item.

Note that this step is presently designed to run from a Windows PE boot image.  Support for deploying an IGEL image from a Linux boot image will be available in the future.

See the [IGEL 12](/deployr/1.2/reference/task-sequence-templates/igel-12.md) task sequence template for an example of a full task sequence to deploy the IGEL OS.

{% hint style="info" %}
Note:  Additional functionality related to IGEL (e.g. configuration files, licenses, etc.) is not yet available.
{% endhint %}


---

# 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://documentation.2pintsoftware.com/deployr/1.2/reference/step-definitions/apply-igel-image.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.