> 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/reference/step-definitions/install-red-hat-enterprise-linux.md). # Install Red Hat Enterprise Linux {% hint style="info" %} This is only supported in DeployR Enterprise. Applies to: DeployR 1.3 (with the latest updates) and later. {% endhint %} The **Install Red Hat Enterprise Linux** step performs an unattended installation of Red Hat Enterprise Linux (RHEL) with Kickstart. The installer (Anaconda) boots from an installation tree published on a web server, so unlike the Ubuntu ISO step, the ISO is not downloaded into a RAMdisk. Only the kernel and initrd are downloaded to the device. Run this step from a [Linux boot image](/deployr/deployment-methods/generate-linux-boot-images.md). It does not work from Windows PE. The [RHEL Workstation](/deployr/task-sequences/task-sequence-templates/rhel-workstation.md) template contains this step. ### Preparing the installation tree Extract the contents of a RHEL boot ISO (or a full DVD ISO) to a folder on a web server that the devices can reach, for example `https://web.contoso.com/rhel/10.2`. The folder must contain `images/pxeboot` (the kernel and initrd) and `images/install.img`. A boot ISO contains no packages, so the packages come from one of these places, in this order: 1. The **Package repository URL**, if specified (for example a mirrored DVD tree or a local repository). 2. The Red Hat CDN, when Red Hat subscription details are specified. The device is registered during the installation, which entitles it to install from the CDN. 3. The installation tree itself. This only works if a full DVD tree was published there. ### Options | Option | Description | | ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Installation tree URL | URL of the extracted RHEL ISO content on a web server. | | Package repository URL | Optional URL of the tree to install packages from. Leave blank to use the Red Hat CDN (when subscription details are specified) or the installation tree. | | AppStream repository URL | Optional AppStream repository URL. Only needed when the package repository has no `.treeinfo` file that adds AppStream automatically. | | Ignore TLS certificate errors | Do not verify the TLS certificate of the installation tree or package repository. Use this when the web server's certificate is not trusted by the RHEL boot image yet, for example one issued by an internal PKI. It only affects the installation, not the installed system. Default: `false`. | | Red Hat organization ID | Organization ID used to register the device during installation. Required to install from the Red Hat CDN. | | Red Hat activation key | Activation key used to register the device. If a DeployR secret named `RHSMActivationKey` exists, the secret is used instead. | | Connect to Red Hat Lightspeed | Enrolls the device in Red Hat Lightspeed (Insights) during registration. Default: `false`. | | Environment to install | **Workstation** or **Server with GUI**. A graphical environment is required because DeployR continues the task sequence from a GDM desktop session. Default: **Workstation**. | | Storage layout | `lvm`, `plain`, `btrfs`, or `thinp`. Default: `lvm`. | | User account to create | Local user account to create. It has sudo access. Default: `rhel`. | | LUKS disk encryption passphrase | If specified, the disk is encrypted with LUKS, and RHEL prompts for this passphrase at startup. | ### Passwords and secrets The password for the user account can be stored as a DeployR secret named `AdminPassword`. If the secret is not configured, the `AdminPassword` task sequence variable is used. Make sure one of them is set. Storing the Red Hat activation key as the `RHSMActivationKey` secret keeps it out of the task sequence. See [Set-Secret | Get-Secret](/deployr/automation-and-powershell/scripting-for-osd/set-secret-or-get-secret.md). ### After the installation When Anaconda finishes, the device restarts into RHEL, signs in to a GDM session automatically, and continues the task sequence. Add later steps, such as **Install Linux updates**, after this step. --- # 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/reference/step-definitions/install-red-hat-enterprise-linux.md?ask=&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.