Install Red Hat Enterprise Linux 9 on an IEI Server
This guide preserves the archived OEM procedure and its example values. Original English screens are retained; translated bitmap labels are English instructional illustrations, not captures from an official English installer. Official English replacement figures can show different example settings, noted beside each image. No operating-system installation or disk operation was performed while preparing this article.
Source scope: most OEM screens show RHEL 9.2, the Legacy partition example shows 9.0, and a completion screen shows 8.0.0. They are separate historical examples, not one continuous verified installation.
1. Boot Installation Image
1) Connect the installation drive to the server. Upon powering on, press <F11> to access the Boot Menu. The feedback shown in the red box in the image below indicates success; wait for the boot menu.

2) Select the required USB drive or optical drive (usually displayed by brand name) and press Enter.

3) After successfully booting the system, the interface below will appear.

4) Press Enter directly on the first item to start the system installation.

2. Basic Settings
1) Select Language: Chinese (Simplified) or English, then click the "Continue" button;

2) Click "Continue" to enter the Installation Summary page.

3) Select the time zone, complete the setting, then click the "Done" button.

4) Keyboard selection: Click the "+" button to add a new keyboard layout. Select the desired language, then click "Add". After adding, click the "Done" button.


5) Select Installation Source
The Verify button checks installation-media integrity. Verify the downloaded image and installation medium according to the applicable Red Hat procedure; the source permits skipping this optional installer check, but skipping it does not establish integrity.

Additional repositories are optional. Use trusted, compatible repositories for the actual RHEL release and architecture and the appropriate entitlement. Adding a repository does not by itself guarantee an updated installation. The illustrated New_Repository entry has an empty URL and is not a usable repository configuration.

3. Package Selection
1) Select a base environment and only the add-ons required for the intended workload. The OEM example chooses Server with GUI and Development Tools. A complete Development Tools group or every optional package is not mandatory for all installations. Building an out-of-tree driver may require the appropriate compiler, matching kernel headers and vendor build prerequisites; a supported precompiled driver has different requirements. Do not copy the source’s older right-click package-selection instruction if the actual RHEL 9 screen does not offer it.

Official English RHEL 9 Software Selection example: Server with GUI is selected; this version’s visible add-on list differs from the OEM RHEL 9.2 Development Tools selection. Choose only the actual needed base environment and add-ons.
4. Partition Settings
1) For automatic partitioning, identify and select the intended installation disk, then select Automatic and Done. The first OEM disk-selection image has no disk selected; it is not a ready-to-install configuration. The separate Kingston USB device is installation media, not automatically the target.

A. Manual Partitioning in UEFI Mode
Choose the partition scheme and filesystems supported by the actual firmware mode and RHEL release. The source prose says Standard Partition, a 200 MB ESP and ext4, but its RHEL 9.2 figure instead shows LVM/XFS with /home 483.29 GiB, / 70 GiB, /boot 1024 MiB, /boot/efi 600 MiB and swap 4 GiB on a 558.88 GiB disk. These are example values, not universal requirements. For UEFI provide a correctly formatted EFI System Partition mounted at /boot/efi and a supported boot layout; size it using the applicable installation guidance. Add /, /boot, swap or other mount points as needed. Review all planned creation, deletion and formatting before accepting changes. Accept Changes returns the plan to the main installer; Begin Installation starts applying it.


Official English RHEL 9.0 partition editor example: a 20 GiB virtual disk has /boot 1024 MiB, / 17 GiB and swap 2 GiB, with LVM/XFS. It replaces an OEM RHEL 9.2 558.88 GiB example with /home 483.29 GiB, / 70 GiB, /boot 1024 MiB, ESP 600 MiB and swap 4 GiB. This is an example of editing fields, not a complete UEFI partition recipe.
The Summary of Changes lists the actual planned operations, including destructive deletion/reformatting where shown. It does not establish that every installation previously contained an OS. Cancel if required data or the wrong disk is involved; protect required data before proceeding. Accept Changes alone is not proof that installation or formatting has completed.

B. Legacy boot uses a different supported boot layout. It does not use a UEFI ESP for booting, but GPT/BIOS installations can require a BIOS boot partition. Check firmware mode, partition table and bootloader requirements; merely omitting /boot/efi is not a complete recipe. The source’s 300 GiB RHEL 9.0 QEMU example is separate from its RHEL 9.2 AVAGO example.

The same official RHEL 9.0 editor illustrates the separate Legacy-boot layout discussion. The OEM source used a different 300 GiB RHEL 9.0 QEMU disk (/home 60 GiB, / 150 GiB, /var 30 GiB, /boot 2 GiB and swap 8 GiB). These are separate examples; verify the actual firmware mode, partition table and bootloader requirements.
5. Network Settings
1) Select the actual connected NIC and configure the intended hostname and addressing. DHCP requires a working link and a reachable DHCP service; enabling an unplugged port does not guarantee an address. The selected ens10f0 example is unavailable, while a later summary mentions ens4f0. They are different source states.

2) The manual IPv4 illustration uses 192.168.1.20, netmask 255.255.255.0 and gateway 192.168.1.1, with DNS blank. These are source example values; use addresses and resolvers assigned for the actual network, then verify connectivity.

6. User Settings
1) Configure root user password. Here you can set whether SSH login is allowed for the root user and whether the root user is disabled. Select based on your needs.
The historical source screenshot displays Weak and a Done-twice override warning. Preserve this as a description of that screen, not a recommendation to bypass password policy. Use an appropriate strong secret and deliberate root/SSH settings.

2) Create the intended non-root account with a compliant password. The source shows ieisystem, administrator unchecked and password required checked. Its Weak/Done-twice warning is not a recommended password policy.

7. Start Installation
1) Review the actual installation summary, selected disk, partition changes, accounts and network configuration, then choose Begin Installation only for the intended installation. Source summaries show different New York/Asia-Shanghai time-zone choices; configure the actual intended zone. The time screen has network time enabled but no valid server warning, so it does not prove successful synchronization.


8. Installation Complete
1) After the actual installer reports success, follow its reboot instructions and boot the intended installed system. The OEM completion picture explicitly says Red Hat Enterprise Linux 8.0.0 although most preceding screens say 9.2. It is retained as an older interface illustration, not evidence that a RHEL 9.2 installation completed.

2) Enter the boot interface


3) Log in using the intended non-root account. Not listed? allows entering another permitted account. The source demonstrates root login and then displays a privileged-session warning; this is not a recommendation for routine root desktop sessions or password-based root SSH.

4) Complete!

English reference and source scope
No corresponding complete English edition of this OEM QA was verified. The official references supply release-specific terminology and suitable English illustrations; they do not certify the pictured OEM hardware/driver combinations. All original sections and working image references are retained, with material source differences explained.