Lewati ke konten

How to Configure IZI Boot and Disk Image

Опубликовано: · Обновлено: (1 месяц назад)· IZI Team

Konten ini belum tersedia dalam bahasa Anda.

IZI Boot stores one reference disk image — operating system, games, and client settings — on a TrueNAS network storage device and boots every PC in your club from it over iSCSI (network boot instead of a local disk). Each time a PC restarts after a session it reverts to that clean “golden” state: no viruses, no broken settings, no accidentally deleted files. The entire setup is done through the Control Center section in IZI CRM with no manual TrueNAS configuration required. The guide below covers everything from connecting the storage to the moment your first PC boots from the image.


RequirementDetails
TrueNAS on the club networkVersion 25.04 (Fangtooth) or later. Earlier versions work but WebSocket status updates require 24.10+.
TrueNAS API tokenCreate it in TrueNAS under Credentials → API Keys → Add.
Storage addressThe address the IZI cloud uses to reach the TrueNAS API. IZI reads the LAN addresses PCs connect disks to from the server itself.
TrueNAS accountThe TrueNAS web UI username and password — required on first connection.
Drive letterAny uppercase letter A–Z except C:. Must be free on every PC in the club.
PC hardwareStandard gaming PCs with a network card — no special hardware required.

Make sure your IZI role includes the IZI_BOOT_MANAGE and IZI_BOOT_CONFIG_MANAGE permissions. Without them the setup wizard buttons will not appear.

The steps below cover TrueNAS — the most common setup. For NetX, the flow is different and is described in the Connecting NetX via Cloud API section below. For GGBOOT, see the separate page Connecting GGBOOT to IZI.


Open the target club in CRM → Control Center → click Configure IZI Boot. The setup wizard opens. The first screen is IZI Boot — Storage Connection.

Fill in the fields:

FieldWhat to enter
IPExternal IP or hostname of TrueNAS — the address CRM uses to reach the API.
PortStandard TrueNAS API port (80 for HTTP, 443 for HTTPS).
API TokenToken from TrueNAS. After saving it is masked; click Change Token to replace it later.
Web UI username and passwordThe TrueNAS web UI account. Required on first connection and checked on the server itself. IZI support uses it in emergencies and to upgrade TrueNAS.
Alert channelA Telegram integration for server health notifications.
Cloudflare Access tokenOnly if the server is behind Cloudflare Access instead of a port forward.
Drive LetterThe letter that will be used to mount the game disk on each PC (for example, D or G).
TrueNAS PoolPool name. If TrueNAS has a single pool, you can leave this blank for auto-detection.
Donor Disk Size (GiB)Volume size for the donor PC. Range: 1–10 240 GiB. Allow headroom for game library growth.
Auto-Update ScheduleSchedule on which the reconciler applies a new image to idle PCs. If left blank the system uses “Always” — image rolls out as soon as each PC is free.

You do not enter the protocol (HTTP or HTTPS) or the server’s LAN addresses: IZI detects them on save.

Click Next — IZI automatically tests the connection to TrueNAS. If TrueNAS is older than 24.04, the connection is saved but the wizard does not continue: the step shows a red banner with upgrade instructions.

If the test fails, CRM shows the exact cause: wrong token (IZI_BOOT_CONN_AUTH), unreachable host (IZI_BOOT_CONN_DNS), TLS handshake failure (IZI_BOOT_CONN_TLS), or timeout (IZI_BOOT_CONN_TIMEOUT). Fix the relevant field and click Retry.


After a successful connection test, IZI checks whether TrueNAS already has disk volumes:

  • Fresh install — no existing disks found on the storage. You need to prepare a donor PC, install Windows via iSCSI, and then capture the image.
  • Migrate existing TrueNAS — IZI detects foreign disks (for example, from a previous system). IZI will offer to adopt one of them as the reference image without destroying the original.

The mode is selected automatically based on pool state. You can switch it manually if needed.


Select the PC that will act as the donor — the source of the reference image. It must be powered on. IZI provisions an empty volume of the configured size on TrueNAS and creates an iSCSI target linked to that PC’s immutable device ID. Storage objects are named with the device identifier, so renaming a PC in CRM later never affects its disk or boot target.

Next steps on the donor PC (outside CRM):

  1. Boot the PC over the network (PXE/iSCSI) — IZI connects the disk automatically via iSCSI.
  2. Install Windows on that disk normally.
  3. Configure everything that belongs in the reference image: the IZI client, games, browsers, sound, screensavers.
  4. Make sure the iSCSI connection settings are saved as persistent so the disk mounts again after each reboot.

In migration mode IZI lists the disks found on TrueNAS. Select the previous system’s main disk — it becomes the reference image. After that IZI removes previous targets and volumes nobody is connected to, including the source disk: what exactly is removed and what to save beforehand is in TrueNAS Server for IZI Boot.


When the donor is ready, go back to CRM and click Capture Reference on the Image Preparation step.

What happens at this point:

  1. IZI takes a snapshot of the donor’s disk in TrueNAS — this becomes the reference image (baseline).
  2. The image is assigned a timestamp identifier in the format YYYY-MM-DD_HH:MM:SS.
  3. The reconciler receives a task: switch all club PCs to the new baseline as soon as each one is idle — usually without a reboot.

After the capture the donor loses its special role and becomes a regular club PC that also reverts to the reference image like all the others.


The next wizard screen shows all club PCs that support Boot. Check the ones that should boot via IZI Boot; uncheck any that should not (for example, racing simulators with non-standard configurations).

Click Save — IZI records the selection and starts the provisioning process.


After saving, each selected PC installs the IZI Boot client automatically — on its next idle startup. Progress is visible in CRM: a counter shows how many PCs are online out of the total.

You do not have to wait for all PCs to finish. Click Finish Now to close the wizard. PCs that are busy or powered off will install automatically as soon as they are free.


In the PCs with Boot section each PC displays one of the following statuses:

StatusMeaning
ONLINEPC is booted from the reference image and working normally.
OFFLINEIZI Boot is not receiving a heartbeat from the PC (powered off or client not installed).
PENDINGThe reconciler has queued the PC to receive the new image.
APPLYINGThe switchover to the new image is in progress.
READYReady to reconnect to the new image.
BROKENProblem with the iSCSI connection or image. Requires investigation.

If a PC shows OUTDATED — it has not yet reconnected to the new image. The reconciler will reconnect it automatically on the first idle window, usually without a reboot: the disk simply refreshes on the fly.


To update games or system settings:

  1. Select a PC marked as capturable (capturableAsReference).
  2. Make your changes on that PC.
  3. In CRM: club → Control Center → IZI Boot section → Capture Reference.
  4. The reconciler applies the updated image to all PCs on schedule automatically.

The Capture Reference button is only available when the PC is free: no active session, no system hold, and the pause that follows a session has expired. If the PC is occupied CRM returns BOOT_DEVICE_BUSY.


To roll back a specific PC to the reference image immediately without waiting for the schedule:

  • Open the PC in the PCs with Boot section → click Apply Image.
  • IZI applies the new image without a full reboot: it swaps the TrueNAS extent and reconnects the iSCSI session on the client side, so the game disk refreshes while the PC stays running.
  • If a client session is running on that PC, CRM warns in the confirmation dialog that the session will be interrupted. A system hold on the PC postpones the apply; your own manual hold does not.

To apply to all PCs at once use Apply to All — the reconciler queues every PC for an immediate pass.


ErrorCause and fix
IZI_BOOT_DRIVE_LETTER_UNAVAILABLEThe chosen letter is in use on one or more PCs (system drive, page file, or local volume). CRM lists the conflicting machines. Choose a different letter.
IZI_BOOT_INSUFFICIENT_POOL_CAPACITYNot enough free space on TrueNAS (threshold is approximately 80% pool capacity). Free space or expand the pool.
IZI_BOOT_NAS_BEHIND_ACCESSThe club NAS is connected via Cloudflare Access and shared with the club’s own disk system. IZI Boot does not adopt foreign volumes or change shared iSCSI settings there; nothing on the NAS was changed.
IZI_BOOT_CLUB_BUSYAnother IZI Boot operation is already running for this club (image apply, reconcile). Wait for it to finish and try again.
IZI_BOOT_NOT_PROVISIONEDThe PC does not have an iSCSI volume on TrueNAS yet. Add the PC to the Boot device list and wait for the reconciler to provision it.
IZI_BOOT_UNSUPPORTED_DEVICE_TYPEThe device type does not support IZI Boot (for example, a payment terminal or printer). Only gaming PCs are supported.
IZI_BOOT_CONN_TLSTLS handshake with TrueNAS failed. Check the certificate or switch to HTTP.
IZI_BOOT_SETUP_IN_PROGRESSInitial club setup (choosing an install mode or migrating from another system) is still running — re-imaging is blocked until it finishes. Wait for setup to complete.
IZI_BOOT_TRUENAS_VERSION_UNSUPPORTEDTrueNAS is older than 24.04. The connection is saved, but IZI Boot does nothing on the server until it is upgraded. Upgrade the server — TrueNAS Versions for IZI Boot.
IZI_BOOT_WEB_CREDENTIALS_REQUIREDThe TrueNAS web UI username and password were not given on first connection. Provide them.
IZI_BOOT_WEB_CREDENTIALS_INVALIDTrueNAS rejected the web UI username and password. Check them on the server itself.
IZI_BOOT_CONN_UNREACHABLETrueNAS is not responding: the club’s server is powered off, lost internet access, or its connection tunnel dropped. Check that the server is on and online.


NetX connects to IZI through the vendor’s cloud API — no public IP, port forwarding, or password required. All you need is the club ID from the NetX panel.

  • An active club account in NetX.
  • Club ID in NetX — found in your club settings inside the NetX panel.
  • IZI permission: BOOT_CONFIG_MANAGE.

Open the target club in IZI CRM → Boot section → NetX card → Configure →.

The connection screen has one field:

FieldWhat to enter
Club ID in NetXThe identifier from the NetX panel.

You can also set an Auto-Update Schedule — the schedule on which IZI applies image updates to club PCs. If no schedule is selected, auto-update is off: PCs are updated with the Apply to all and Re-image buttons. On a schedule, IZI reboots only idle PCs whose image is out of date.

Click Save, then click Check Connection — IZI calls the NetX API and confirms that the club is reachable.

IZI finds a PC in NetX by the number in its name: “01” in IZI and “pc01” in NetX are the same computer. The reference image is captured the same way as described above: in Control Center choose “Create reference image”. After the capture, NetX spends about ten minutes preparing copies for the other PCs, and Apply to all is blocked during that time. Details are on the page Connecting NetX to IZI.

  • To update the ID, click Edit next to the field.
  • To disconnect entirely, click Delete — club PCs will stop being managed through NetX.

Pertanyaan yang sering diajukan

What is IZI Boot?

IZI Boot is an IZI module that stores a single reference disk image — OS, games, and settings — on a TrueNAS network storage device and boots every PC in the club from it over iSCSI. After each session the PC automatically reverts to that clean baseline.

What do I need before setting up IZI Boot?

A TrueNAS instance on version 24.04 or newer (25.04+ recommended) on the club's local network, a TrueNAS API token, the TrueNAS web UI username and password, the storage address, and a free drive letter (any letter except C:) for the game disk on each PC.

Which drive letter should I choose?

Any uppercase letter from A to Z except C: (reserved for the system drive). The letter must be free on every PC in the club — IZI checks for conflicts when you save the configuration and returns a list of conflicting machines if any are found.

What is a donor PC?

The donor PC is the first machine from which IZI captures the reference image. You boot it over iSCSI, install Windows, configure games and software, then click Capture Reference in IZI CRM. All other club PCs will then boot from that snapshot.

What happens after I click Capture Reference?

IZI takes a snapshot of the donor's disk in TrueNAS and saves it as the baseline image with a timestamp identifier (YYYY-MM-DD_HH:MM:SS). The reconciler — a background process — then queues every club PC to reconnect to the new image as soon as it's idle, usually without a reboot.

How do I connect NetX — do I need to enter an IP address and password?

No. NetX connects using only the club ID from the NetX panel — the IP, port, and password fields are no longer used. Find the identifier in your club's settings inside NetX, enter it in IZI CRM, and save.

Can I update the image after the initial setup?

Yes. Select any PC marked as capturable, make your changes on that machine, then click Capture Reference again from Control Center. The reconciler distributes the updated image to all club PCs automatically according to the configured schedule.

About IZI