IT automation / Dell and HP
Computer Provisioning.
BIOS configuration and the start of Windows installation.
How it works
Computer identification
I prepared automation that runs from WinPE before Windows installation. It recognises a supported Dell or HP computer, configures the agreed BIOS settings, resumes after a restart, verifies the result, and hands the remaining work to the installer. The entire process has its own state and a register of prepared devices.
History and scope of the work
A repeatable task before installation
The starting point was an existing WinPE image and the need to organise the computer-provisioning stage. I added a layer that runs before the existing installation workflow. It identifies the device, checks the required capabilities, and guides each step. This reduces repeated manual configuration while retaining information about what was done on a specific computer.
Dell and HP: separate interfaces, one process
For Dell, I prepared support through Dell Command Configure, and for HP through the BIOS WMI interface. The automation matches the supported storage-controller setting to the firmware and configures AHCI mode and a BIOS administrator password. I separated the manufacturers’ interfaces from the shared process logic, allowing additional models to be supported without copying the entire workflow.
One restart and resumption from a saved stage
I built a state machine that stores the current stage on the USB drive. After accepting the changes, the computer restarts once and returns to the same environment through a one-time UEFI setting. The second run reads the configuration result, password state, and disk availability. The installer starts only after this verification.
A register of prepared devices
The automation records the result for a specific computer identity, together with the model, BIOS version, rule-set version, and number of attempts. A later run can use the shortened path only when the record still matches that device and its configuration. A new BIOS or rule-set version triggers another verification. I also prepared compatibility with the older marker for a completed process.
The password does not become part of the report
I prepared masked password entry and passed it in memory to the appropriate configuration layer. The device register stores the status of the action, not the secret. I separated diagnostics from the data used to perform the operation. An error ends the controlled process without automatically looping through further attempts, keeping the result clear for the person provisioning the computer.
From source files to a boot image
The work covered manufacturer scripts, resumption logic, supporting UEFI tools, and the construction and verification of a separate WIM image. I preserved the existing installation workflow and prepared a procedure for checking the configuration, restart, and subsequent launch on a specific model. Image validation and a trial on a physical computer complete successive stages of the same process.
What this work makes possible
Repeatable computer provisioning gained one organised process: identification, configuration, resumption, verification, and installation. The register makes it possible to return to the result for a given device.
The scope covers supported Dell and HP computers. I verify compatibility with additional models and BIOS versions in separate pilots.