ImageForge guides

ImageForge Docs

Clear guides for setup, your first deployment, everyday imaging, and troubleshooting.

ImageForge helps you save one prepared Windows setup and deploy it to other PCs. These guides walk you through installation, a boot USB, your first capture and deployment, optional network boot, and ongoing maintenance.

1. Install server 2. Create boot USB Run your first job

IMAGEFORGE::CONSOLE

dashboard images drivers profiles access

ImageForge-Lablicensed

18images

2.4 TBlibrary

12/15seats

Capturelab-win11 from HP ProDesk

Deployfront-office to Latitude 7420

Servicewin11-base updated overnight

Docs include console-oriented screenshots and checklists so admins and technicians know what to expect.

Technician media

See the technician experience

Click the preview and press Enter to walk through a sample ImageForge job from boot to restart.

IMAGEFORGE PE CLIENT preview

IMAGEFORGE technician boot client preview loading...

WinPE client readyClick terminal and press Enter to start

Start with your job today

1. Install the serverInstaller, license, storage, access codes, TLS fingerprint, and optional network boot. 2. Create the standard USBChoose the x64 default or an Advanced exception, then write the ISO with Rufus. 3. Optional: enable network bootUse the installer choice, confirm the interface, and look for listening. 4. Run a first jobA step-by-step checklist with clear success criteria for your first test. Save a clone or deployment imageChoose the purpose, run preflight checks, and validate the captured WIM. Reimage a machineSafe wipe confirmation, hash verification, driver injection, and profile application. Plan concurrent jobsEstimate wave time, understand shared limits, and measure the right capture/deploy count for your Forge. Fix a problemUse logs and diagnostics to solve network, startup, storage, and long-running job issues.

How the system fits together

1. PrepareSet up one clean Windows source machine.

2. BootStart the PC with the ImageForge USB or optional network boot.

3. SaveAdd the prepared Windows setup to your image library.

4. ReimageChoose the image and let ImageForge apply the right drivers and settings.

5. ReviewConfirm the result and check the job history.

Technicians use the bootable ImageForge workspace while the server keeps images, storage, licenses, access codes, drivers, settings, network boot, and job history together.

What each role needs

Role	Primary docs	Proof they should collect
Forge admin	Install server, Storage & backup	License status, free space, backup zip, access code list
Bench technician	Create boot USB, Capture, Deploy	Diagnostics screen, capture/deploy result, boot result
Network/admin contact	Network requirements, Network boot	Open ports, VLAN notes, PXE interface and media status
Test owner	Run a first job, Downloads & resources	Pass/fail decision, blockers, logs, screenshots, next steps

Safety model

Access — the console requires an admin password, and technician access codes are protected and shown only once.

Trusted connections — boot media verifies the approved ImageForge server before sending technician credentials.

Destructive work — deploy only runs from WinPE and requires the technician to type ERASE for the selected target disk.

Resource shortcuts

DownloadsEvery current release download and its checksum in one place. Admin quick referencesConsole locations for install ID, TLS fingerprint, access, PXE, logs, and audit export. Name template previewTry profile tokens before using them in a deployment profile. Storage plannerEstimate store size before capture day. Concurrent-job plannerCompare a measured single job with a parallel imaging wave.