> 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/task-sequences/task-sequence-templates/rhel-workstation.md).

# RHEL Workstation

{% hint style="info" %}
This is only supported in DeployR Enterprise. Applies to: DeployR 1.3 (with the latest updates) and later.
{% endhint %}

The **RHEL Workstation** template installs Red Hat Enterprise Linux with the Workstation environment, then installs the latest updates. It contains two steps:

* [**Install Red Hat Enterprise Linux**](/deployr/reference/step-definitions/install-red-hat-enterprise-linux.md)
* [**Install Linux updates**](/deployr/reference/step-definitions/install-linux-updates.md)

After creating a task sequence from this template, edit the **Install Red Hat Enterprise Linux** step and specify at least the **Installation tree URL**: the web server folder that holds the extracted RHEL ISO. To install packages from the Red Hat CDN, also specify the Red Hat organization ID and activation key, or store the key as the `RHSMActivationKey` secret. Configure the `AdminPassword` secret for the password of the user account that is created.

{% hint style="warning" %}
In this template, **Ignore TLS certificate errors** is turned on, so the installer does not verify the web server's certificate. If your web server's certificate is trusted by the RHEL boot image, turn this option off.
{% endhint %}

Like the other Linux templates, this task sequence must run from a [Linux boot image](/deployr/deployment-methods/generate-linux-boot-images.md). It does not work from Windows PE.


---

# 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/task-sequences/task-sequence-templates/rhel-workstation.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.