Downloads & resources
Downloads, admin references, field evidence, and the fastest path to the right guide.
Find a resource
1. Install serverInstall the Forge, activate the license, set storage, create access codes, and choose whether to enable network boot.
2. Create boot USBChoose the standard ISO, write it with Rufus, and keep ARM/compatibility choices under Advanced.
3. Optional: network bootUse the guided installer option, confirm listening in the console, and understand PXE limits.
4. Run a first jobPlan a first real-world test with roles, checklists, evidence, and closeout criteria.
Capture workflowTurn a prepared Windows machine into a stored, hashed Forge image.
Deploy workflowErase safely, verify the image, apply drivers, and boot into Windows.
Driver packsMatch model-specific drivers and troubleshoot WinPE networking.
Deployment profilesName machines, set locale/time zone, add local admin, domain join, and first-boot scripts.
Storage and backupMove the store, size disks, back up config, restore, and service stored images.
TroubleshootingUse session logs, diagnose discovery, firmware, storage, and long-running DISM phases.
Downloads
| Item | Use it for | Link |
|---|---|---|
| Forge Server Installer 1.2.0 | Install the ImageForge Windows service | Download installer SHA-256 |
| Boot ISO 1.2.0 — Intel & AMD PCs (x64) | Technician boot USB for x64 machines; write it with Rufus | Download x64 ISO SHA-256 |
| Boot ISO 1.2.0 — Snapdragon & ARM PCs (ARM64) | Technician boot USB for ARM64 machines; write it with Rufus | Download ARM64 ISO SHA-256 |
| Network Boot Bundle 1.2.0 | Manual or air-gapped PXE setup; one bundle covers x64 and ARM64 (this is a bundle, not a USB ISO) | Download bundle SHA-256 |
| Release checksum list | All public 1.2.0 SHA-256 values in one file | Download checksums |
| Install guide | Installer, license, storage, access, TLS fingerprint, and optional PXE | Read setup |
| Create a boot USB | Choosing the right ISO, Rufus settings, and Secure Boot notes | Read guide |
Admin quick references
Keep these locations handy during setup, pilots, and support calls.
| Need | Where to find it |
|---|---|
| Install ID | Console → license |
| TLS fingerprint | Console → access → server identity |
| Technician access codes | Console → access |
| Image store and free space | Console → storage |
| Network boot status | Console → network boot |
| Audit export | https://FORGE-HOST:8967/api/v1/events.csv |
Support may occasionally provide a site-specific media bundle or ask for a console screenshot, session log, install ID, or TLS fingerprint. ImageForge is delivered as commercial installer and media packages.
Evidence to collect
Pilot evidence bundle
Important paths and ports
| Thing | Value | Why it matters |
|---|---|---|
| Console/API | TCP 8967 | Web console and boot client API |
| Discovery | UDP 8968 | Automatic Forge discovery on the LAN |
| Direct capture | TCP 445 | One-time SMB capture share from the Forge |
| Network boot | UDP 67, UDP 4011, UDP 69, TCP 8969 | ProxyDHCP, PXE boot server, TFTP, and HTTP boot assets |
| USB session logs | \imageforge-logs\imageforge-<timestamp>.log | Full WinPE client session log |
| Forge client logs | data\clientlogs\ | Uploaded copies while the client is connected |