{"id":25014,"date":"2026-10-19T08:36:26","date_gmt":"2026-10-19T08:36:26","guid":{"rendered":"https:\/\/atalnetworks.com\/?p=25014"},"modified":"2026-10-19T08:36:26","modified_gmt":"2026-10-19T08:36:26","slug":"install-os-bare-metal-ipmi","status":"publish","type":"post","link":"https:\/\/atalnetworks.com\/ar\/install-os-bare-metal-ipmi\/","title":{"rendered":"How to Install an OS on a Bare Metal Server via IPMI\/iKVM"},"content":{"rendered":"

To install an OS on a bare metal server remotely, open its management console, attach a verified installer ISO as virtual media, and select that media for the next boot. Complete the installation on the intended disk, detach the ISO when finished, then check disk boot, networking, and remote login.<\/span><\/p>\n

The process does not require a working operating system or SSH connection. It does require a working management controller, suitable access permissions, and support for remote console and virtual media.<\/span><\/p>\n

We use Ubuntu Server as the installation example below. Dell iDRAC, Supermicro BMC, and HPE iLO use different controls, so match the instructions to your controller and firmware. This is a documentation-based guide, not a report of an Atal Networks hardware test.<\/span><\/p>\n

Before you begin:<\/b> Installing an OS or changing RAID configuration can erase data. Confirm the server identity, target disks, maintenance window, and recoverable backups before making changes.<\/span><\/p>\n

Check Access, Backups, and Installation Requirements<\/span><\/h2>\n

A successful installation starts with two separate sets of details: management access and the network configuration for the new OS. Keep them separate throughout the procedure.<\/span><\/p>\n

Record the Server and Management Details<\/span><\/h3>\n

Collect the following information from your provider or server administrator:<\/span><\/p>\n

 <\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Requirement<\/b><\/th>\nDetails to confirm<\/b><\/th>\n<\/tr>\n<\/thead>\n
Server identity<\/span><\/td>\nAsset ID, serial number, or another reliable identifier<\/span><\/td>\n<\/tr>\n
Management controller<\/span><\/td>\nModel, firmware version, and management address<\/span><\/td>\n<\/tr>\n
Access route<\/span><\/td>\nPrivate management network, VPN, or approved gateway<\/span><\/td>\n<\/tr>\n
Permissions<\/span><\/td>\nRemote console, virtual media, and required power controls<\/span><\/td>\n<\/tr>\n
Feature access<\/span><\/td>\nAny license needed for console or ISO mounting<\/span><\/td>\n<\/tr>\n
Storage<\/span><\/td>\nTarget disk or RAID logical volume and existing data<\/span><\/td>\n<\/tr>\n
Installation media<\/span><\/td>\nSupported OS release, architecture, and verified ISO<\/span><\/td>\n<\/tr>\n
Host network<\/span><\/td>\nNIC, IP address, prefix, gateway, DNS, and VLAN if required<\/span><\/td>\n<\/tr>\n
Recovery<\/span><\/td>\nBackup location, restore procedure, and support contact<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Use assigned credentials. Do not assume a factory-default username or password applies to your server.<\/span><\/p>\n

If the management page shows an unexpected certificate warning, confirm the address and certificate details with the provider. Do not accept every warning without checking which system you reached.<\/span><\/p>\n

Prepare the OS Image and Drivers<\/span><\/h3>\n

Download the installation image from the OS publisher or an authorized mirror. Choose an image for your server’s processor architecture and supported hardware.<\/span><\/p>\n

For an Intel or AMD x86-64 server, this normally means an amd64 or x86_64 image. An ARM server needs a compatible ARM image. A virtual-machine disk image is not necessarily a bootable installation ISO.<\/span><\/p>\n

Check storage-controller and network-driver support before starting. Windows Server may require an additional driver during installation. A minimal or network installer may also need access to package repositories before it can finish.<\/span><\/p>\n

Confirm What Will Be Erased<\/span><\/h3>\n

Identify the intended OS disk by its model, capacity, serial number, or RAID logical-volume details. Device names such as <\/span>\/dev\/sda<\/span> can change and should not be your only reference.<\/span><\/p>\n

If the server holds application data on separate disks, record which disks must remain untouched. Stop if the installer shows a different layout from the one you expected.<\/span><\/p>\n

RAID is not a backup. Creating, deleting, or initializing an array can destroy data before the OS installer starts.<\/span><\/p>\n

Understand IPMI, iKVM, and Virtual Media<\/span><\/h2>\n

These terms refer to related but different functions:<\/span><\/p>\n

 <\/p>\n\n\n\n\n\n\n\n\n\n
Term<\/b><\/th>\nMeaning in this guide<\/b><\/th>\n<\/tr>\n<\/thead>\n
BMC<\/span><\/td>\nBaseboard management controller that provides management functions outside the host OS<\/span><\/td>\n<\/tr>\n
IPMI<\/span><\/td>\nA management interface used for functions such as hardware status and power control<\/span><\/td>\n<\/tr>\n
iKVM or remote console<\/span><\/td>\nRemote keyboard, video, and mouse access to the server<\/span><\/td>\n<\/tr>\n
Virtual media<\/span><\/td>\nA controller feature that presents a remote image or drive to the server<\/span><\/td>\n<\/tr>\n
iDRAC \/ iLO<\/span><\/td>\nDell and HPE management platforms with model-dependent features<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Here, KVM means keyboard, video, and mouse. It does not mean Linux KVM virtualization.<\/span><\/p>\n

The BMC can remain accessible while the host OS is stopped, provided its own power and network requirements are met. This lets you view firmware screens, start an installer, or inspect a boot failure.<\/span><\/p>\n

However, IPMI support alone does not guarantee graphical-console access or ISO mounting. Check the actual controller features, permissions, and licenses.<\/span><\/p>\n

Choose the Console and ISO-Mounting Method<\/span><\/h2>\n

Dell iDRAC, Supermicro BMC, and HPE iLO<\/span><\/h3>\n

Look for the functions below. Exact labels vary by model and firmware.<\/span><\/p>\n

 <\/p>\n\n\n\n\n\n\n\n
Platform<\/b><\/th>\nConsole function<\/b><\/th>\nMedia function<\/b><\/th>\n<\/tr>\n<\/thead>\n
Dell iDRAC<\/span><\/td>\nVirtual Console<\/span><\/td>\nVirtual Media, often with Map CD\/DVD<\/span><\/td>\n<\/tr>\n
Supermicro BMC<\/span><\/td>\nRemote Control or iKVM<\/span><\/td>\nVirtual Media, Virtual Storage, or image-mount controls<\/span><\/td>\n<\/tr>\n
HPE iLO<\/span><\/td>\nRemote Console<\/span><\/td>\nVirtual Media or virtual-drive controls<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Dell’s virtual-media guide<\/span><\/a> describes the supported workflow and license requirements for the listed iDRAC generations. <\/span>Supermicro’s license documentation<\/span><\/a> identifies HTML5 virtual media among its management-suite features. HPE documents its own <\/span>HTML5 virtual-drive installation procedure<\/span><\/a>.<\/span><\/p>\n

A working console with no ISO-mount option may indicate a permission or license issue. Check that before changing firmware or trying another installer.<\/span><\/p>\n

Local ISO or Controller-Mounted Image<\/span><\/h3>\n

With a local ISO, your workstation supplies the image through the supported console or media client. Keep the required session open, prevent the workstation from sleeping, and maintain its network connection.<\/span><\/p>\n

Some controllers can mount an image from a network source. In that case, the BMC must reach the source using a supported protocol. A URL that works on your laptop may be inaccessible from the management network.<\/span><\/p>\n

Use a provider-approved source and access method. Do not enable old file-sharing protocols across your normal network just to satisfy a legacy controller. Ask for a supported alternative or an isolated arrangement.<\/span><\/p>\n

Install the OS Through IPMI\/iKVM<\/span><\/h2>\n

Step 1: Open the Console and Confirm the Server<\/span><\/h3>\n

Connect through the approved management route and sign in to the controller. Check the server’s asset identifier before opening power controls.<\/span><\/p>\n

Launch the remote console. Use a supported HTML5 viewer where available. Older hardware may require a vendor client or JNLP application. Follow its supported-client instructions instead of weakening browser or Java security settings across your workstation.<\/span><\/p>\n

You should see the server’s current display, such as a firmware screen, login prompt, or boot error. A powered-off host may show no video until it starts.<\/span><\/p>\n

Check before continuing:<\/b> You can identify the correct server and use the console. Do not restart a different machine because its login page looks familiar.<\/span><\/p>\n

Step 2: Verify and Attach the Installer ISO<\/span><\/h3>\n

Verify the downloaded ISO against trusted publisher information. On a Linux workstation, calculate its SHA-256 hash with:<\/span><\/p>\n

sha256sum \/path\/to\/installer.iso<\/span><\/p>\n

On Windows PowerShell, use:<\/span><\/p>\n

Get-FileHash -Algorithm SHA256 -Path ‘C:\\ISO\\installer.iso’<\/span><\/p>\n

Replace the example path with your file location. Compare the complete result with the publisher’s checksum for that exact image.<\/span><\/p>\n

A hash checks whether two files match. It does not establish authenticity if both the ISO and expected hash came from an untrusted source. Where provided, follow the publisher’s signed-checksum process, such as <\/span>Ubuntu’s image-verification instructions<\/span><\/a>.<\/span><\/p>\n

In the console or management interface:<\/span><\/p>\n

    \n
  1. Open the virtual-media controls.<\/span><\/li>\n
  2. Select the CD\/DVD or ISO option.<\/span><\/li>\n
  3. Choose the verified local image or supported remote source.<\/span><\/li>\n
  4. Select the action that connects or maps the image.<\/span><\/li>\n
  5. Confirm that the device status shows connected or mounted.<\/span><\/li>\n<\/ol>\n

    Selecting a filename is not always enough. Some interfaces require a separate connection action.<\/span><\/p>\n

    Expected result:<\/b> The controller reports an attached virtual device. Keep any required media session open.<\/span><\/p>\n

    Step 3: Check Boot Mode and Storage Configuration<\/span><\/h3>\n

    Confirm the intended firmware boot mode before installation. UEFI and legacy BIOS installations use different boot arrangements. Boot the installer in the mode you intend to use afterward.<\/span><\/p>\n

    Do not disable Secure Boot by default. Check whether the chosen OS, installer, and required drivers support the server’s settings. Change those settings only for a documented compatibility need.<\/span><\/p>\n

    Next, confirm how storage should appear:<\/span><\/p>\n