RED HAT ENTERPRISE LINUX

Installation & Kickstart

Installing RHEL Interactively and Automatically

College-Level Course Module | RHEL System Administration

Welcome to this foundational module on installing Red Hat Enterprise Linux. Every system administrator needs to know how to install the operating system - both interactively for single systems and automatically for deploying many systems consistently. You will learn two approaches: interactive installation using the Anaconda installer's graphical interface, where you make choices about language, disk partitioning, software selection, and network configuration; and Kickstart automated installation, where you provide a configuration file that answers all these questions automatically. Kickstart is essential for enterprise environments where you deploy dozens or hundreds of identical systems. Understanding both methods gives you flexibility - interactive for unique configurations, Kickstart for repeatability and scale. These are fundamental skills for RHCSA certification and real-world Linux administration.

Learning Objectives

Understand RHEL installation methods

Boot media, installation sources, and deployment options

Perform interactive installation

Navigate Anaconda installer, configure storage and packages

Create Kickstart configuration files

Automate installations with ks.cfg files

Deploy systems using Kickstart

Boot with Kickstart files from various sources

Installation Overview

RHEL Installation uses the Anaconda installer to deploy the operating system. It can run interactively with a GUI or automatically using Kickstart configuration files.

Interactive Installation

Administrator makes choices through GUI screens. Good for unique systems, learning, or when requirements are unclear.

Kickstart Installation

Configuration file provides all answers. Good for deploying many identical systems, ensuring consistency, automation.

Boot Media

→

Anaconda

→

Configure

→

Install Packages

→

Reboot

RHEL installation follows a consistent process whether interactive or automated. You boot from installation media - typically a DVD ISO or USB drive. This launches the Anaconda installer, which is RHEL's installation program. Anaconda collects configuration information - either from you interactively or from a Kickstart file. Then it partitions disks, installs packages, configures the system, and reboots into the new installation. Interactive installation is appropriate when you are installing one or a few unique systems, when you are learning RHEL, or when you do not yet know all the requirements. Kickstart installation is appropriate when you need to deploy many systems with identical or similar configurations, when you want guaranteed consistency, or when you want to automate deployment pipelines. Most enterprises use Kickstart for server deployments. Understanding both methods makes you versatile.

Installation Media

RHEL installation requires boot media and package sources. These can be the same (DVD) or separate (network boot + network repository).

Media Type	Description	Use Case
DVD ISO	Full installation image (~10GB), contains all packages	Standalone installations, no network needed
Boot ISO	Minimal boot image (~800MB), packages from network	Network installations, always get latest packages
USB Drive	DVD or Boot ISO written to USB	Physical servers, no optical drive
PXE Boot	Network boot, no local media needed	Data center deployments, automation

# Create bootable USB from ISO (Linux)
[root@workstation ~]# dd if=rhel-9.3-x86_64-dvd.iso of=/dev/sdb bs=4M status=progress
# Warning: This destroys all data on /dev/sdb!

# Verify USB device name first
[root@workstation ~]# lsblk

RHEL can be installed from various media types. The DVD ISO is the full installation image, around 10GB. It contains all packages, so you can install without network access. Good for isolated environments or when network is unreliable. The Boot ISO is much smaller, around 800MB. It contains just enough to boot and start Anaconda, but packages must come from a network source - Red Hat CDN, a local repository, or an NFS/HTTP server. Good for network installations where you always want the latest packages. USB drives are the most common physical media today since many servers lack optical drives. Write the ISO to USB using dd on Linux or tools like Rufus on Windows. Be extremely careful with dd - specifying the wrong device destroys data. PXE boot requires no local media at all. Servers boot from the network, receiving the installer over TFTP. This is the standard for data center automation but requires PXE infrastructure. For RHCSA, focus on DVD/USB installations. PXE is more advanced infrastructure.

Booting the Installer

RHEL 9.3 Installation

Install Red Hat Enterprise Linux 9.3

Test this media & install Red Hat Enterprise Linux 9.3

Troubleshooting >

Press Tab to edit options, Press e to edit the whole command

# Boot menu options:
# - Install: Start installation immediately
# - Test & Install: Verify media integrity first (recommended)
# - Troubleshooting: Rescue mode, memory test

# Press Tab to add boot options:
vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=RHEL-9-3 quiet

# Add Kickstart location:
vmlinuz ... inst.ks=http://server/ks.cfg

# Common boot options:
# inst.ks=URL          - Kickstart file location
# inst.repo=URL        - Package repository location
# inst.vnc             - Enable VNC for remote installation
# inst.text            - Text mode installation

When you boot from RHEL installation media, you see a boot menu. Install Red Hat Enterprise Linux starts the graphical installer immediately. Test this media and install first verifies the installation media has no corruption - recommended especially for burned DVDs or if you have had installation failures. Troubleshooting provides access to rescue mode and memory testing. Pressing Tab lets you edit boot options for the selected entry. This is how you add Kickstart file locations or other parameters. Press e for full editing in GRUB style. Key boot options: inst.ks specifies a Kickstart file URL. inst.repo specifies where packages come from if different from boot media. inst.vnc enables VNC so you can do graphical installation remotely. inst.text forces text mode installation for systems without graphics. The boot options are your gateway to customizing and automating the installation process. For Kickstart deployments, adding inst.ks is essential.

Anaconda Summary Screen

The Installation Summary screen is the hub of interactive installation. Configure each category, then begin installation when all items show complete.

INSTALLATION SUMMARY

LOCALIZATION

Keyboard: English (US)

Language Support: English

Time & Date: America/New_York

SOFTWARE

Installation Source ⚠

Software Selection: Server

SYSTEM

Installation Destination ⚠

Network & Host Name

USER SETTINGS

Root Password ⚠

User Creation

Begin Installation (disabled until required items configured)

After booting, the graphical Anaconda installer presents the Installation Summary screen. This hub-and-spoke design lets you configure items in any order. Items marked with warning symbols require attention before installation can proceed. The main categories are Localization for language, keyboard, and timezone; Software for installation source and package selection; System for disk configuration and networking; and User Settings for root password and user accounts. You must configure at least: Installation Destination (disk partitioning), and Root Password or create an administrator user. Other items have sensible defaults but should be reviewed. Click each item to configure it, then click Done to return to the summary. When all required items are complete, Begin Installation becomes active. This is a different model from older step-by-step installers - you can jump around and configure in whatever order makes sense.

Installation Destination

Installation Destination configures disk partitioning. You can use automatic partitioning or create custom layouts with standard partitions, LVM, or Btrfs.

# Automatic partitioning creates:
/boot      - 1 GB (ext4 or xfs)
/boot/efi  - 600 MB (UEFI systems only, vfat)
/          - Remaining space (xfs, in LVM)
swap       - Based on RAM (in LVM)

# Recommended minimum partitions:
/boot      - 1 GB minimum, outside LVM
/          - Root filesystem, 10+ GB
swap       - Equal to RAM for hibernation, or 50% RAM

# Optional separate partitions:
/home      - User data, survives reinstalls
/var       - Logs, databases, growing data
/tmp       - Temporary files, can add noexec

RHEL 9 default: Automatic partitioning uses LVM with XFS filesystems. This provides flexibility to resize volumes later.

Installation Destination is where you configure disk partitioning. Select the disk or disks to use, then choose automatic or custom partitioning. Automatic partitioning is the simplest option. Anaconda creates a reasonable layout: a boot partition, EFI system partition for UEFI systems, and LVM with root and swap logical volumes. This works well for most systems. Custom partitioning gives you full control. You can create standard partitions, LVM logical volumes, or Btrfs subvolumes. Common customizations include separate /home to preserve user data across reinstalls, separate /var for systems with large logs or databases, and specific sizes for particular workloads. For RHCSA, understand both automatic and custom partitioning. Know what partitions are required (/boot must be outside LVM for BIOS boot, /boot/efi for UEFI) and recommended practices. In production, custom partitioning is common for servers with specific storage requirements.

Software Selection

Software Selection determines which packages are installed. Choose a base environment and optional add-ons for your intended use case.

Base Environment	Description	Packages
Server with GUI	Full graphical server environment	~1400 packages
Server	Command-line server, common services	~400 packages
Minimal Install	Bare minimum for running system	~300 packages
Workstation	Desktop with development tools	~1800 packages
Custom Operating System	Only core packages, you select everything	~250 packages
Virtualization Host	KVM hypervisor and management tools	~500 packages

Best practice: Start minimal and add packages later with dnf. This reduces attack surface and installation time.

Software Selection determines the initial package set. Choose wisely - it is easier to add packages later than to remove unnecessary ones. Base environments define the system's purpose. Server with GUI is for graphical administration. Server is the standard choice for most server deployments - command-line with useful tools. Minimal Install is the smallest practical installation - good for containers, appliances, or when you want complete control. Workstation is for desktop use with development tools. Add-ons supplement the base environment. Development Tools adds compilers and build tools. System Administration Tools adds management utilities. Security Tools adds scanning and hardening tools. For production servers, Minimal Install or Server are typical. Smaller installations mean faster deployment, less disk usage, fewer updates, and smaller attack surface. You can always add packages later with dnf. For learning and RHCSA practice, Server provides a good balance of tools without overwhelming complexity.

Network Configuration

# Network & Host Name screen allows:
# - Enable/disable network interfaces
# - Configure IPv4/IPv6 (DHCP or static)
# - Set hostname

# For static IP configuration:
IPv4 Method: Manual
Address:     192.168.1.100
Netmask:     255.255.255.0  (or /24)
Gateway:     192.168.1.1
DNS:         192.168.1.1, 8.8.8.8

# Hostname examples:
server1.example.com    (FQDN recommended)
webserver01            (short name)

# Network is needed during installation for:
# - Network installation source (Boot ISO)
# - Red Hat subscription registration
# - Time synchronization
# - Kickstart file retrieval

Note: Network interfaces are disabled by default during installation. Enable and configure them here, especially for network installations or subscription registration.

The Network and Host Name screen configures networking during installation. By default, network interfaces are disabled - you must enable them if needed. For DHCP, just toggle the interface on. For static IP, click Configure and enter IP address, netmask, gateway, and DNS servers. The hostname should be set here. Use a fully qualified domain name when possible - server1.example.com rather than just server1. This helps with DNS resolution and service configuration later. Network is required during installation if you are using a network installation source (Boot ISO needs to download packages), if you want to register with Red Hat during installation, for accurate time synchronization, or if Kickstart files are on a network server. Even if not required, configuring network during installation saves post-installation work. The configuration persists to the installed system.

User Configuration

Root Password

Set the root account password. Can optionally lock root account if admin user is created.

# Strong password requirements:
# - At least 8 characters
# - Mix of cases, numbers, symbols
# - Not a dictionary word

# Options:
[ ] Lock root account
[x] Allow root SSH login

User Creation

Create a regular user account. Can grant administrator privileges (wheel group).

# User account fields:
Full name: Alice Admin
User name: alice
Password:  ********

# Options:
[x] Make administrator
    (adds to wheel group)

Security practice: Create an administrator user and optionally lock root. This provides accountability through individual logins and sudo logging.

User configuration is required before installation can proceed. You must either set a root password or create an administrator user. Root password sets the traditional superuser password. You can optionally lock the root account if you create an administrator user - this follows security best practice of not using root directly. The option to allow root SSH login controls the sshd PermitRootLogin setting. User creation adds a regular user account. Check Make this user administrator to add them to the wheel group, granting sudo privileges. In enterprise environments, creating individual administrator accounts is preferred over shared root access. Each person logs in as themselves, gains privileges with sudo, and all actions are logged with their identity. For RHCSA and lab environments, setting a root password is fine. For production, consider locked root with administrator users.

Begin Installation

Configure All

→

Begin Install

→

Package Install

→

Reboot

# Once Begin Installation is clicked:
# 1. Disk partitioning is applied (destructive!)
# 2. Filesystems are created and formatted
# 3. Packages are installed from source
# 4. Bootloader (GRUB2) is installed
# 5. Initial configuration is applied
# 6. System is ready to reboot

# Progress shows:
Installing package 234 of 456: httpd-2.4.53...
Performing post-installation setup tasks...

# After completion:
[Reboot System]

# Remove installation media before reboot!

Point of no return: Once you click Begin Installation, disk changes are applied. Existing data on selected disks will be destroyed.

When all required items are configured, Begin Installation becomes active. Clicking it starts the actual installation process - this is the point of no return for disk changes. The installer partitions and formats disks, destroying existing data. Then packages are copied and installed from your installation source. Progress is displayed with package names and counts. This takes anywhere from 10 minutes to an hour depending on package selection and media speed. After packages install, the bootloader is configured, SELinux labels are set, and other initial setup runs. When complete, a Reboot button appears. Before rebooting, remove or disconnect installation media so the system boots from the installed disk rather than restarting installation. First boot may take longer than subsequent boots as initial configuration completes. After first boot, you have a working RHEL system ready for configuration and use.

Introduction to Kickstart

Kickstart automates RHEL installation by providing answers to all installer questions in a configuration file. The system installs without human intervention.

Manual Installation

Click through screens
Make decisions interactively
Good for 1-5 systems
Each install may differ slightly

Kickstart Installation

Configuration file provides answers
Completely automated
Good for many systems
Guaranteed identical installs

Benefits: Consistency across deployments, faster installation, reduced human error, repeatable process, enables Infrastructure as Code practices.

Kickstart is Red Hat's system for automated installation. Instead of clicking through Anaconda screens, you create a text configuration file that answers all the questions. Boot the installer with a pointer to this file, and installation proceeds without human intervention. The benefits are significant. Consistency - every system installed from the same Kickstart is identical. No forgotten settings or different choices. Speed - no waiting for human input. Deploy as fast as the hardware can install. Reliability - no human errors, fat-fingered settings, or missed steps. Repeatability - deploy the same configuration a year later and get the same result. Documentation - the Kickstart file documents exactly how systems are configured. Kickstart enables Infrastructure as Code practices. Your system configuration is in version control, reviewable, and reproducible. For enterprise environments deploying many systems, Kickstart is essential.

Kickstart Structure

# Kickstart file sections:

# 1. Command Section - Installation settings
text                           # Text mode install
url --url="http://repo/rhel9" # Package source
keyboard --vckeymap=us        # Keyboard layout
lang en_US.UTF-8              # Language
timezone America/New_York     # Timezone
rootpw --iscrypted $6$...    # Root password (encrypted)

# 2. Disk Configuration
clearpart --all --initlabel   # Clear existing partitions
autopart                       # Automatic partitioning
bootloader --location=mbr     # Bootloader location

# 3. Package Section
%packages
@^minimal-environment         # Base environment
vim-enhanced                   # Individual package
-plymouth                      # Exclude package
%end

# 4. Scripts Section (optional)
%post
echo "Post-install script"
%end

Kickstart files have a specific structure. The command section comes first and contains installation settings - installation mode, package source, locale settings, passwords, and network configuration. Each command typically maps to an Anaconda screen option. The disk configuration section handles partitioning. clearpart removes existing partitions. autopart creates automatic partitioning, or you can specify exact partition layouts. bootloader configures GRUB. The packages section lists what to install. It starts with %packages and ends with %end. Use @ prefix for package groups, @^ for environment groups. Prefix with minus to exclude. The scripts section is optional but powerful. %pre runs before installation. %post runs after installation completes but before reboot - this is where you add customization like configuration files, additional users, or service setup. The order matters: commands first, then packages, then scripts. Comments start with # and are ignored.

Essential Commands

# Installation source
url --url="http://server/rhel9/BaseOS"
cdrom                          # Use attached DVD/ISO
nfs --server=nfs.example.com --dir=/exports/rhel9

# Network configuration
network --bootproto=dhcp --device=eth0 --activate
network --bootproto=static --ip=192.168.1.100 --netmask=255.255.255.0 --gateway=192.168.1.1 --nameserver=8.8.8.8 --hostname=server1.example.com

# User accounts
rootpw --plaintext redhat123  # Plain text (not recommended)
rootpw --iscrypted $6$rounds=... # Encrypted (use this)
rootpw --lock                 # Lock root account
user --name=alice --password=$6$... --iscrypted --groups=wheel

# Installation behavior
text                           # Text mode
graphical                      # GUI mode
reboot                         # Reboot after install
poweroff                       # Shut down after install
firstboot --disabled          # Skip first-boot wizard

Let me explain the essential Kickstart commands. Installation source tells where to get packages. url for HTTP/HTTPS repositories, cdrom for attached DVD, nfs for NFS shares. The URL should point to the directory containing the BaseOS repository. Network configuration can use DHCP or static addressing. Include --activate to bring up the network during installation. The hostname is set here too. User account commands set up authentication. For security, always use --iscrypted with a hashed password rather than plaintext. Generate hashes with python3 -c "import crypt; print(crypt.crypt('password'))". The user command creates regular users and can add them to groups like wheel for sudo access. Installation behavior controls the installer mode. text is faster and works without graphics. reboot automatically reboots when complete - important for unattended installation. firstboot --disabled skips the initial setup wizard on first boot.

Disk Configuration

# Clear and initialize disk
zerombr                        # Clear MBR if invalid
clearpart --all --initlabel   # Remove all partitions
clearpart --drives=sda        # Clear specific disk only

# Automatic partitioning
autopart                       # Default LVM layout
autopart --type=lvm           # Explicitly use LVM
autopart --type=plain         # Standard partitions, no LVM

# Manual partition layout
part /boot --fstype=xfs --size=1024
part /boot/efi --fstype=efi --size=600  # UEFI systems
part pv.01 --size=1 --grow    # LVM physical volume

volgroup rhel pv.01           # Volume group
logvol / --vgname=rhel --name=root --fstype=xfs --size=10240
logvol /home --vgname=rhel --name=home --fstype=xfs --size=5120
logvol swap --vgname=rhel --name=swap --size=2048

# Bootloader
bootloader --location=mbr --boot-drive=sda

Disk configuration in Kickstart ranges from simple automatic to fully custom layouts. zerombr clears invalid partition tables - useful when disks have garbage data. clearpart removes existing partitions. Use --all to remove everything or --drives to target specific disks. Always include --initlabel to create a new partition table. autopart creates an automatic layout. By default it uses LVM, but --type=plain creates standard partitions instead. This is the simplest option for straightforward deployments. For custom layouts, use part for standard partitions or LVM physical volumes. The --grow option makes a partition use remaining space. Then volgroup creates volume groups from physical volumes, and logvol creates logical volumes. Sizes are in megabytes. bootloader configures GRUB. Location is typically mbr for BIOS or the EFI system partition for UEFI. Specify --boot-drive if you have multiple disks. Custom partitioning is powerful but must be correct - a Kickstart with bad disk configuration fails immediately.

Package Selection

%packages
# Environment group (base installation)
@^minimal-environment         # Minimal install
@^server-product-environment  # Server
@^graphical-server-environment # Server with GUI

# Package groups
@development                   # Development Tools group
@system-tools                  # System administration tools
@security-tools                # Security tools

# Individual packages
vim-enhanced
tmux
git
httpd
firewalld

# Exclude packages (prefix with -)
-plymouth                      # Remove boot splash
-iwl*firmware                  # Remove wireless firmware

%end

List available groups: dnf group list --hidden shows all package groups. Environment groups use @^ prefix, regular groups use @.

The packages section specifies what software to install. It must start with %packages and end with %end. Environment groups define the base installation type. Use @^ prefix followed by the environment ID. These correspond to the Software Selection screen options - minimal-environment, server-product-environment, etc. Package groups bundle related packages. Use @ prefix followed by the group name. Development Tools, System Tools, and Security Tools are commonly added to server installations. Individual packages are listed by name without any prefix. Add whatever packages your deployment needs - web servers, databases, monitoring agents, your organization's standard tools. Exclude packages with a minus prefix. Common exclusions include plymouth (graphical boot splash not needed on servers) and wireless firmware on servers without WiFi. To find group names, run dnf group list --hidden on an existing RHEL system. The hidden flag shows all groups including those not displayed by default.

%pre and %post Scripts

%pre
# Runs BEFORE installation, limited environment
# Useful for dynamic disk selection, logging
echo "Starting installation at $(date)" > /tmp/install.log
%end

%post
# Runs AFTER installation, full system available
# Runs in chroot of installed system by default

# Configure services
systemctl enable httpd
systemctl enable firewalld

# Create files
cat > /etc/motd << EOF
Deployed via Kickstart on $(date)
EOF

# Run commands
dnf -y update
subscription-manager register --username=user --password=pass
%end

%post --nochroot
# Access installation environment, not installed system
cp /tmp/install.log /mnt/sysimage/root/
%end

Pre and post scripts extend Kickstart with custom automation. The %pre section runs before installation begins. The environment is limited - you are in the installer, not a full system. Pre scripts are useful for dynamic configuration like detecting hardware or writing logs. The %post section runs after packages are installed but before reboot. By default, it runs in a chroot of the installed system - commands execute as if the new system were running. This is where most customization happens: enabling services, creating configuration files, registering subscriptions, running updates, adding SSH keys, or any other setup. The --nochroot option for %post runs outside the chroot. Use this to copy files from the installation environment into the new system at /mnt/sysimage. You can have multiple %post sections with different options. Scripts can use any interpreter available - bash by default, but %post --interpreter=/usr/bin/python3 works too.

Creating Kickstart Files

Create Kickstart files from scratch, from the system-config-kickstart tool, or by copying and modifying the anaconda-ks.cfg from a completed installation.

# Every RHEL installation creates a Kickstart file recording what was done
[root@server ~]# cat /root/anaconda-ks.cfg
# Generated by Anaconda 34.25.0.20
# System timezone
timezone America/New_York --utc
# Root password
rootpw --iscrypted $6$...
...

# Copy and customize for future installs
[root@server ~]# cp /root/anaconda-ks.cfg /var/www/html/ks.cfg
[root@server ~]# vi /var/www/html/ks.cfg

# Validate Kickstart syntax
[root@server ~]# dnf install pykickstart
[root@server ~]# ksvalidator /var/www/html/ks.cfg
(no output means valid)

# Compare two Kickstart files
[root@server ~]# ksdiff ks1.cfg ks2.cfg

There are several ways to create Kickstart files. Starting from scratch is possible but tedious - many options to remember. The easiest method is copying anaconda-ks.cfg. Every RHEL installation creates this file in /root recording exactly what was configured. Copy it, modify as needed, and use for future installations. The system-config-kickstart graphical tool walks through options and generates a file. It is not installed by default but available in repositories. For enterprise use, start with a known-good configuration and maintain it in version control. Modify incrementally and test changes. The pykickstart package provides validation tools. ksvalidator checks syntax and reports errors - run this before deploying a new Kickstart. Better to find errors before booting systems. ksdiff compares two Kickstart files, showing differences - useful when troubleshooting why two installations differ.

Using Kickstart Files

# Boot option to specify Kickstart location
inst.ks=URL

# Kickstart from HTTP server
inst.ks=http://192.168.1.10/ks.cfg
inst.ks=http://server.example.com/kickstart/webserver.cfg

# Kickstart from NFS
inst.ks=nfs:server.example.com:/exports/ks.cfg

# Kickstart from USB or DVD
inst.ks=hd:sdb1:/ks.cfg
inst.ks=cdrom:/ks.cfg

# At boot menu, press Tab and add:
vmlinuz initrd=initrd.img inst.stage2=... inst.ks=http://server/ks.cfg

# Combine with repository location if using Boot ISO
inst.ks=http://server/ks.cfg inst.repo=http://server/rhel9/

HTTP is most common: Host Kickstart files on a web server. Easy to update, version control, and serve multiple configurations.

To use a Kickstart file, add inst.ks=URL to the kernel boot options. At the boot menu, press Tab to edit options and append the Kickstart location. HTTP is the most common method. Set up a web server, place Kickstart files in the document root, and reference by URL. This is easy to manage - update files centrally, version control them, and serve different configurations for different server roles. NFS works similarly for environments with NFS infrastructure already in place. Local media works for isolated installations - put the Kickstart file on a USB drive or include it on a custom DVD. The cdrom option looks on the installation DVD itself. If using the Boot ISO (which has no packages), you also need inst.repo to tell the installer where to get packages. With the DVD ISO, packages are on the media itself. When Kickstart is specified, Anaconda reads the file and proceeds automatically. If the Kickstart is complete, no human interaction is needed. If anything is missing, Anaconda prompts for just the missing information.

Complete Example

# Minimal web server Kickstart
text
url --url="http://repo.example.com/rhel9/BaseOS"
repo --name="AppStream" --baseurl="http://repo.example.com/rhel9/AppStream"

keyboard --vckeymap=us
lang en_US.UTF-8
timezone America/New_York --utc

network --bootproto=dhcp --device=eth0 --activate
network --hostname=webserver1.example.com

rootpw --iscrypted $6$rounds=4096$salt$hashedpassword
user --name=admin --groups=wheel --iscrypted --password=$6$...

zerombr
clearpart --all --initlabel
autopart
bootloader --location=mbr

firewall --enabled --service=ssh --service=http --service=https
selinux --enforcing
firstboot --disabled
reboot

%packages
@^minimal-environment
httpd
mod_ssl
vim-enhanced
%end

%post
systemctl enable httpd
%end

Here is a complete, practical Kickstart example for a web server. It demonstrates all the key sections working together. The installation settings specify text mode and package sources - both BaseOS and AppStream repositories are needed for RHEL 9. Locale settings cover keyboard, language, and timezone. Network uses DHCP with the hostname set separately. User configuration creates an encrypted root password and an administrator user in the wheel group. In production, generate proper password hashes. Disk configuration uses automatic partitioning - simple and effective for straightforward deployments. Security settings enable firewall with SSH and web services allowed, keep SELinux enforcing, disable firstboot wizard, and automatically reboot when done. Package selection uses minimal environment plus just the packages needed - Apache HTTP server, SSL module, and vim for editing. The post script enables httpd to start at boot. This Kickstart produces a ready-to-use web server. Boot with inst.ks pointing to this file, and you get a consistent, secure web server every time.

Key Takeaways

Interactive Install: Boot from media, configure through Anaconda GUI screens. Good for unique systems and learning.

Key Decisions: Disk partitioning (auto or custom), software selection (minimal to full), network, and user accounts.

Kickstart: Text file with all installation answers. Use inst.ks=URL at boot. Enables consistent automated deployment.

Kickstart Sources: Copy /root/anaconda-ks.cfg from existing install. Validate with ksvalidator.

LAB EXERCISES

Perform interactive RHEL installation in a VM
Use custom partitioning with separate /home
Copy and examine anaconda-ks.cfg from completed install
Create Kickstart for minimal server with specific packages
Deploy VM using Kickstart from HTTP server
Add %post script to enable services and create files

Next: Managing Software with DNF and Repositories

Let me summarize the essential installation skills. Interactive installation uses the Anaconda GUI. You boot from installation media and configure through visual screens. This is appropriate for unique systems, learning, or when requirements are unclear. Key decisions during any installation include disk partitioning - automatic for simplicity or custom for specific needs; software selection from minimal to full environments; network configuration; and user accounts with appropriate privileges. Kickstart automates installation with a text configuration file. Add inst.ks=URL to boot options and the installation proceeds without human intervention. Essential for deploying many systems consistently. Start creating Kickstarts by copying anaconda-ks.cfg from a completed installation. This captures exactly what was configured. Modify for your needs and validate with ksvalidator before deploying. Your lab exercises give hands-on practice with both methods. Install interactively first to understand the options, then create Kickstarts to automate. Practice with VMs where mistakes are easily recovered. These skills are fundamental for RHCSA and real-world administration.