ข้ามไปยังเนื้อหา

Game Disk Reference Image: Creation and Updates

Опубликовано: · Обновлено: (6 дней назад)· IZI Team

เนื้อหานี้ยังไม่มีในภาษาของคุณ

Game Disk Reference Image: Creation and Updates

Section titled “Game Disk Reference Image: Creation and Updates”

A reference image in IZI Boot is the game disk in a ready state: installed and tested games and configured launchers. It is stored as a separate volume on the club’s TrueNAS server. Each PC gets its own clone of the reference over the network and mounts it on the game drive letter chosen during setup. A clone takes server space only for that PC’s changes. The system disk C: stays local and is not part of the reference.

With a reference, a game update is done once — on one PC — and then spreads to the whole hall.

  • IZI Boot connected: Settings → Equipment → Game storage. How to connect it — TrueNAS server for IZI Boot.
  • A PC with IZI Boot enabled and the game disk attached.
  • Access to Hall → PCs.

Pick the PC to capture the reference from. Put it on hold: in the device command menu, Create Hold, with a duration buffer (2–4 hours) and the reason “Image creation”.

Install and update games on the game disk, check that they launch, and configure the launchers.

In the Control Center Timeline menu, choose Enable Boot mode. Each PC shows its image status (up to date or outdated), and a Boot status filter appears above the hall: “Up to date, no changes”, “Up to date, with changes”, “Outdated”, “Unknown status”.

In the source PC’s command menu, open the Boot group and choose Create reference. When it finishes, CRM reports “Reference image created from device …”.

Not every PC has this item: a PC booted from the reference cannot be the source of a new reference.

Pick another PC and, in its command menu under Boot, click Apply game image. In the “Re-image this PC now?” dialog, click Re-image: the PC is re-cloned from the reference, and local changes on its game disk are lost. If a client session is running on the PC, the dialog warns that it will be interrupted. An IZI service hold defers the apply; your manual hold does not.

Progress is shown in the Applying boot image window; you can close it and the apply continues. When the PC is back, check that games launch.

On the Boot mode bar, click Apply to all. The reconcile is queued: PCs get the new image as they free up and within the update window. PCs that are busy, off, or in service mode right now are skipped — CRM shows how many, and you repeat for them later.

Open the source PC’s hold block and click Release PC.

When new games or updates come out, repeat steps 1–5: prepare the PC, capture a new reference, test it on one PC, and apply it to all. The Outdated filter shows the PCs that have not received the new reference yet.

คำถามที่พบบ่อย

What does an IZI Boot reference image contain?

The game disk: a separate volume on the club's TrueNAS server. Each PC gets its own clone of the reference over the network and mounts it on the drive letter chosen during setup. The system disk C: stays local and is not part of the reference.

What happens to a PC with a running session if I apply the image to it?

The confirmation dialog warns that the client's session will be interrupted. Local changes on that PC's game disk are lost.

Why did Apply to all skip some PCs?

Applying runs as PCs free up and within the update window. Busy, powered-off, or service-mode PCs are skipped — apply to them again later.

Can I capture the reference from any PC?

No. In the device picker, a PC booted from the reference is marked as unavailable: to capture from it, the PC has to be provisioned in IZI Boot again.

About IZI