iDRAC Commander
A server cannot explain a blank screen.
A server appeared to be stuck during installation. The real problem was a firmware prompt waiting for someone to press a key. We built iDRAC Commander to make that screen visible and the surrounding hardware controls scriptable.
- 5hardware control surfaces
Console screenshot, power, boot, virtual media and BIOS configuration.
- T320 / iDRAC 7hardware used for the installation recipe
The headless install recipe was used on a Dell T320; a July 18, 2026 engineering account also records a console capture.
- Image validationa capture must be a picture
The screenshot path checks PNG/JPEG signatures rather than trusting an HTTP success code.
- InspectCapture the server's actual console screen.
- ConfigureSet BIOS attributes and the next boot device.
- Supply mediaAttach installation media through the controller.
- Restart and observeControl power and inspect the next boot.
The problem
Powering a machine on is easy to automate. Knowing why it did not boot is harder. An out-of-band management controller may be reachable while the server itself is waiting at a warning that ordinary remote access cannot show.
Interactive console applets put a human back into the loop for every investigation. A fleet spanning older and newer management controllers adds another difference to learn each time.
Who it’s for
For operators maintaining Dell servers without a person at the keyboard, especially during bare-metal installs and recovery when the operating system is not yet reachable.
What we built
We built a command-line tool for live console screenshots, power control, boot selection, virtual installation media and BIOS attributes. It gives an operator both visibility and a way to change the settings that blocked an unattended boot.
We used the headless installation recipe on a Dell T320 with iDRAC 7. Controller-generation differences matter, so the interface also separates the routes used by iDRAC 8 and 9.
How it works
For screenshots, the tool tries the modern management API and falls back to the older controller's authenticated console-preview flow. It checks the returned bytes for an actual image before accepting a capture. A successful HTTP response containing an error page does not become a screenshot.
Power, boot, media and firmware configuration use the management controller independently of the installed OS. A BIOS change can remove the prompt that stopped unattended boot, while virtual media supplies the installer for the next start.
What was hard
Different controller generations expose different routes to the same outcome. We handle those differences behind a small set of operator actions. The boot fix also has to respect firmware timing: a queued BIOS change applies during a reboot, so the current screen and the configured next boot can briefly describe different states.