Boot media
Getting the technician USB that boots machines into ImageForge.
USB settings
Rufus quick reference
| Setting | Use |
|---|---|
| Boot selection | ImageForge boot ISO |
| Partition scheme | GPT |
| Target system | UEFI (non-CSM) |
| Write mode | ISO image mode |
Before handing the USB to a technician
Download and write the USB
- Download the current ImageForge boot ISO from the Downloads page. The ISO is the same for everyone — a boot stick is useless without an activated Forge and a technician access code, so the license does the gatekeeping, not the download.
- Write it to a USB stick with Rufus: ISO image mode, GPT partition scheme, target UEFI (non-CSM). Any 2 GB+ stick works; the stick also carries session logs back from the field, so bigger doesn't hurt.
- Boot the machine from the stick (one-time boot menu: Dell F12, HP F9, Lenovo F12). The client brings up networking, finds your Forge, and asks for a technician access code.
The standard ISO ships with a broad driver library — NIC and storage drivers covering current and older hardware generations — and the client can additionally borrow network drivers from a machine's own Windows install when something exotic shows up.
Machines and Forge on different networks
The client discovers the Forge by LAN broadcast. Across VLANs or strict firewalls, technicians simply type the Forge's address when prompted. For repeat deployments across VLANs, keep the Forge address and TLS fingerprint on the bench sheet or request pinned site media from ImageForge support.
Site-specific media packages
Most sites never need site-specific media. The standard ISO can discover the Forge automatically or accept the Forge address at the prompt. Use a site-specific media package when you want one or more of these settings preloaded:
| Setting | Effect |
|---|---|
| Forge address | Skips LAN discovery and connects to the named Forge |
| TLS fingerprint | Pins the media to one Forge identity for air-gapped or strict networks |
| WinPE drivers | Adds required NIC/storage drivers for hardware the standard ISO does not cover |
Contact support with the Forge address, TLS fingerprint, and any required driver packs. They will provide a media package or updated ISO for your site.
Known firmware traps
- Vendor recovery hijack: if a machine boots into Dell SupportAssist / HP Sure Recover instead of the USB, the firmware never booted the stick. Use the one-time boot menu and pick the UEFI entry for the stick.
- Old, unpatched firmware may not trust the current Microsoft boot manager under Secure Boot. Apply firmware/OS updates, or disable Secure Boot for the session and note it.
- Legacy Option ROMs should stay disabled — legacy PXE ROMs can leave NICs in a state PE drivers cannot take over.