image-forge.net

Run a first job

A first real-world ImageForge test that proves the workflow without turning into a mass deployment.

Recommended first test

Keep the first test small and focused.

Use one ImageForge server, one prepared PC, one spare PC that is safe to erase, one technician code, and one image. Add more hardware models only after the first capture and deployment work.

1ImageForge server
1source image
1+spare PCs
ACTIVITY
dashboard activity images machines
first test resultsexportable
Capture oklab-win11
Deploy okDell Latitude 7420
Inventoryserial, model, MAC recorded
Finish the test by reviewing diagnostics, the image library, job history, inventory, and logs.

Your first deployment, step by step

You can do this test yourself. If you joined the first-testers program, I can help with setup; request personal onboarding. No purchase is required.

  1. Choose a small test. Use a prepared source PC and a spare target PC whose disk you can erase. Back up anything you need from the target. Start with USB on one network.
  2. Install the Forge server. Set the console admin password, then open License → Start trial. The 14 days start here. The trial allows one Forge and one technician seat and needs internet initially and at least every 72 hours.
  3. Create the boot USB. Choose x64 for Intel/AMD or ARM64 for an ARM PC. Create a technician access code in the console.
  4. Prepare the source in Windows. Run ImageForge Capture Readiness from the matching USB as Administrator. Resolve every blocker before capture. Follow the capture guide for Sysprep preparation; stop and ask for help if the Windows image state is unclear.
  5. Capture. Boot the prepared source from USB, connect to your Forge, and capture the image. Confirm it appears in the image library.
  6. Deploy to the spare target. Boot it from USB, select the image, and verify the exact target disk before confirming its erasure. Add model-specific drivers or a deployment profile if your test needs them.
  7. Boot Windows and check the result. Confirm Windows starts and the devices you need work. If you used naming or domain-join settings, verify their results too. A completed transfer alone is not a successful deployment.
  8. Tell me how it went. Reply to your onboarding email or send feedback: PC models, setup time, capture/deploy/boot results, confusing steps, and what would stop you using it. Send logs only if needed, after checking them for sensitive details.

Your images and settings remain on your server after the trial ends; capture and deployment require a valid license to continue.

For a team evaluation

These responsibilities can all belong to one person during a small test.

RoleResponsibility
Test ownerDefines success criteria and decides whether ImageForge moves forward
Forge adminInstalls the server and manages license, storage, access, optional network boot, backup, and support evidence
Bench technicianBoots machines, runs diagnostics, capture, deploy, and collects logs
Network/admin contactConfirms firewall, VLAN, DHCP, storage, and PXE details if used
RecorderCaptures screenshots, timings, blocker notes, and the final outcome

Before-you-start checklist

Keep the media choice obvious. Use the x64 ISO for Intel and AMD PCs and the ARM64 ISO for Snapdragon and other ARM PCs. PXE uses the network-boot bundle, not an ISO.

Before the test window starts

Runbook

  1. Start ImageForge. Install ImageForge normally, then open https://localhost:8967. Set the admin password, activate the license, create a technician code, and confirm storage. If you are testing network boot, turn it on and confirm the console says it is ready.
  2. Boot the source machine. Use the Rufus-written USB, or the verified network-boot bundle when PXE is part of the test. Sign in with the technician code and run diagnostics/readiness first. Record the media choice, model, serial, MAC, volumes, Forge reachability, and TLS identity method/status.
  3. Capture the source. Use a clear image name such as lab-win11-2026-08. Record the capture method, BitLocker/Sysprep warnings, duration, image size, checksum, and any warnings.
  4. Prepare driver packs or profiles if needed. Upload driver ZIPs, scope model rules, and create a deployment profile only if those are part of the success criteria.
  5. Deploy to the spare PC. Run diagnostics first, choose the image and settings, confirm the target disk, type ERASE, and wait for ImageForge to verify and apply the image, add drivers and settings, and prepare Windows to start.
  6. Verify Windows and console evidence. Confirm first boot, hostname/profile effects, driver behavior, activity feed, inventory, storage state, and uploaded session logs.
  7. Decide the outcome. Mark pass, conditional pass, blocked, or fail. Record blockers, fixes, safe public hardware claims, and what should wait for more testing.

Pass criteria

PassCapture and deploy complete on the test hardware; Windows boots; job history and logs explain what happened.
Conditional passThe workflow works with setup fixes such as adding WinPE drivers or opening a firewall rule.
BlockedA hardware, network, storage, boot media, or permission issue prevents a fair test. Fix and retest.
FailThe agreed workflow cannot complete after blockers are resolved and evidence is collected.

Evidence bundle

Collect enough proof for someone who was not in the room.

Closeout questions

Related docs

Install serverStand up the Forge, create technician access, and choose optional network boot. Create boot USBChoose an official qualified ISO and write it with Rufus. CaptureUnderstand preflight, direct capture, and image hygiene. DeployUnderstand wipe safety, hash verification, drivers, and profiles. TroubleshootingUse logs and diagnostics when something goes wrong. Downloads & resourcesRelease status, admin references, ports, logs, and evidence checklist.