ImageForge Wiki

ImageForge Docs

The practical home for setup, pilot planning, technician workflows, and field troubleshooting.

ImageForge is a Windows imaging system built around one Forge server, bootable technician media, and a repeatable capture/deploy workflow. Start USB-first, add network boot when the site is ready, and keep images, drivers, profiles, storage, access, and audit evidence in one place.

Set up a Forge Run a pilot Find resources

IMAGEFORGE::CONSOLE

dashboard images drivers profiles access

Forge-Pilotlicensed

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.

Start with your job today

First Forge installInstaller, license, storage, access codes, TLS fingerprint, and firewall ports. Prepare boot mediaDownload and write the USB/ISO that technicians use for capture and deploy. Prove it on real hardwareA focused pilot runbook with roles, checklists, evidence, and pass/fail criteria. Capture a golden imagePreflight checks, direct capture, BitLocker, Sysprep, and image hygiene. Reimage a machineSafe wipe confirmation, hash verification, driver injection, and profile application. Fix a field issueRead client logs, diagnose networking, firmware boot, storage, and long quiet phases.

How the system fits together

1. PrepareSet up one clean Windows source machine.

2. BootStart ImageForge USB or PXE WinPE media.

3. CaptureStream a WIM to the Forge and hash it.

4. DeployVerify, apply, inject drivers, set identity.

5. ProveReview logs, audit, inventory, and outcomes.

Technicians work from WinPE. The Forge handles the web console, image library, storage, licensing, technician access, driver packs, deployment profiles, network boot, and audit history.

What each role needs

Role	Primary docs	Proof they should collect
Forge admin	Server setup, Storage & backup	License status, free space, backup zip, access code list
Bench technician	Boot media, 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
Pilot owner	Pilot runbook, Resource hub	Pass/fail decision, blockers, logs, screenshots, next steps

Safety model

Access — the console requires an admin password, and boot clients require technician access codes that are shown once and stored hashed.

Server trust — clients use HTTPS and pin the Forge certificate fingerprint, which works well on isolated imaging VLANs.

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

Resource shortcuts

DownloadsInstaller, boot ISO, and customer-facing guides 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.