Connecting GGBOOT to IZI
Connecting GGBOOT to IZI
Section titled “Connecting GGBOOT to IZI”GGBOOT is a third-party network-boot platform (ggboot.ru) that supports both hybrid and diskless PC configurations. Once connected to IZI CRM, the club manages images, PC power, and GGBOOT client bindings directly from the IZI interface — without needing to log into the GGBOOT panel separately. Below is the full setup process from entering credentials to your first PC binding.
Prerequisites
Section titled “Prerequisites”| Requirement | Details |
|---|---|
| Club GGBOOT account | Email and password for the club’s organisation on ggboot.ru. One account = one organisation = one IZI club. |
| Matching mode | The club’s mode in IZI (hybrid / diskless) must match the organisation’s mode in GGBOOT before connecting. |
| IZI permissions | Administrator role with BOOT_CONFIG_MANAGE and BOOT_MANAGE permissions. |
| GGBOOT subscription | An active vendor subscription with enough PC slots. |
Step 1. Open Boot settings and select GGBOOT
Section titled “Step 1. Open Boot settings and select GGBOOT”Open the relevant club in IZI CRM → Boot section. The list shows all supported boot systems: izi-boot, CCBoot, NetX, and GGBOOT. The GGBOOT card is labelled “For diskless clubs” or “For disk-backed clubs” depending on your club’s mode. Click Set up → on the GGBOOT card.
Step 2. Save credentials
Section titled “Step 2. Save credentials”On the connection screen fill in two fields:
| Field | What to enter |
|---|---|
| Login (email) | The email address for the club’s GGBOOT account. |
| Password | The account password. When editing an existing connection, you can leave this blank to keep the saved password unchanged. |
Click Save. IZI immediately runs a live check: it signs into the account, identifies the organisation, and compares its mode against the club’s mode.
Possible errors:
| Error | Cause and fix |
|---|---|
GGBOOT_CONN_AUTH | Wrong email or password — check your credentials in the ggboot.ru panel. |
GGBOOT_EGRESS_UNAVAILABLE | GGBOOT is unreachable: timeout, refused connection, or DNS failure. Check the server’s internet access. |
GGBOOT_CONNECTION_ERROR | The vendor returned an unexpected response — try again later or contact GGBOOT support. |
GGBOOT_MODE_MISMATCH | The organisation’s mode in GGBOOT (hybrid / diskless) doesn’t match the club’s mode in IZI. Change the mode in your club settings or in the GGBOOT panel. |
After a successful save the connection block shows Connected and the Club at the vendor panel appears automatically with live data from GGBOOT.
Step 3. Review the vendor club status
Section titled “Step 3. Review the vendor club status”The Club at the vendor section displays data pulled directly from GGBOOT:
| Row | Meaning |
|---|---|
| Mode | Hybrid or Diskless — the organisation’s mode in the GGBOOT panel. |
| Server | Online / Offline — current status of the club’s GGBootServer, plus the server version. |
| Write protection | The method the vendor uses to protect disks: “GGBOOT writeback” or “Windows write filter (UWF)”. |
| Game drives | Drive letters the vendor allocates for the game volume. |
| Subscription | Number of active PC slots out of the purchased total, and the subscription expiry date. |
The Open in GGBOOT → link goes directly to the club page in the vendor panel.
IZI does not change mode, write-protection method, or drive letter settings — those are managed in the GGBOOT panel. The CRM reads them for display only.
Step 4. Bind PCs to GGBOOT clients
Section titled “Step 4. Bind PCs to GGBOOT clients”Commands (power, game drive reconnect, PE update) only reach a PC after it is bound to a GGBOOT client. A GGBOOT client is identified by MAC address and is registered on the vendor side automatically when a PC first connects to GGBootServer.
The PC ↔ GGBOOT client section lists all PCs in the club that support network boot.
To bind a PC:
- Find the PC’s row.
- In the dropdown, select the GGBOOT client (identified by the MAC address or name the vendor recorded at registration).
- Click Bind.
After binding, three action buttons appear in the PC’s row:
| Button | What it does |
|---|---|
| Reconnect game drive | Remounts the game drive on this PC. The PC sees the updated files from the vendor server. The write overlay (all changes made by players) is discarded. PC must be free. |
| Update GGBootPE | Reboots the PC into the vendor’s boot environment to update the GGBootPE component. The PC is out of service for the duration of the update. PC must be free. |
| Unbind | Removes the binding. Commands will no longer reach this PC through GGBOOT until it is bound again. |
The Reconnect game drives on all PCs button at the top of the section reconnects the game drive across the whole club in one action. PCs with an active session are skipped and counted in a skippedCount — reconnect those manually afterwards.
Step 5. Manage images
Section titled “Step 5. Manage images”The Images section lists all images registered in the club’s GGBOOT organisation. Images are created and stored on the vendor side; IZI displays the list and lets you set the default image.
The default image is what the vendor rolls out to PCs. If no default is selected, IZI warns: “Default image is not selected — there is nothing to roll out”.
To change the default image, click Make default next to the image you want.
Each image row shows the GGBootClient version bundled inside (if known). To update the client in an image, click Update client in image — the vendor performs the update in the background. The result (success or failure) is returned as a separate event and shown as a notification.
Step 6. Reference capture (hybrid mode only)
Section titled “Step 6. Reference capture (hybrid mode only)”In hybrid mode IZI supports the reference capture process using the GGBOOT super client. The super client is activated on a chosen PC, captures its state, and uploads the changes to an image on the vendor side.
The Reference capture section shows the current process status:
| Status | Meaning |
|---|---|
| Idle | No capture in progress. |
| Activating | Super client is being activated on the PC. |
| Ready to collect | Super client is running; you can finish work on the donor PC. |
| Uploading | Data is being transferred to vendor storage. |
| Applying to image | The vendor is merging the uploaded data into the image. |
| Done | Capture complete; the new image is ready to roll out. |
To finish the capture, click Upload to image: enter a comment (required — the vendor needs a description of the changes) and optionally enable Keep a backup of the previous image.
To abort without saving, click Cancel capture — the super client shuts down and no changes are written to the image.
Common errors
Section titled “Common errors”| Error | Cause |
|---|---|
GGBOOT_CLIENT_NOT_BOUND | The PC is not bound to any GGBOOT client — bind it in the PC ↔ GGBOOT client section. |
GGBOOT_CLIENT_GONE | The GGBOOT client this PC was bound to no longer exists on the vendor side. Unbind and rebind. |
GGBOOT_SUBSCRIPTION_BLOCKED | The PC exceeds the vendor subscription’s slot limit. Check active slot usage in the Club at the vendor section. |
GGBOOT_NO_DEFAULT_IMAGE | No default image selected. Assign one in the Images section. |
GGBOOT_NO_WRITE_FILTER | The GGBOOT organisation is configured to use UWF write protection, but Windows write filter is not active on the PC. Enable UWF on the machines or switch the protection method in the GGBOOT panel. |
BOOT_DEVICE_BUSY | The PC has an active session or a system process running. Wait for it to free up before sending a command. |
Related pages
Section titled “Related pages”- IZI Boot: what it is and how it works — overview of all supported boot platforms
- How to configure IZI Boot and the reference disk image — setting up the built-in IZI Boot with TrueNAS and NetX
- Disk protection — how disk protection works in IZI
- Recovering a PC after a crash — what to do when a PC won’t boot
Frequently asked questions
What is GGBOOT and how is it different from the built-in IZI Boot?
GGBOOT (ggboot.ru) is a third-party network-boot platform. Unlike the built-in IZI Boot (TrueNAS), GGBOOT manages its own server and images on the vendor's side. IZI CRM connects to your club's GGBOOT account and sends commands through it, but does not store images itself.
Which mode should I use — hybrid or diskless?
The mode is set in IZI club settings and must match the mode of the organisation in the GGBOOT panel. The mode cannot be changed once the club has PCs. If the modes differ, the connection will fail with GGBOOT_MODE_MISMATCH.
Does each club need its own GGBOOT account?
Yes. One GGBOOT account maps to one organisation, and one organisation maps to one IZI club. An account already connected to another IZI club cannot be reused.
What happens if I change the GGBOOT organisation?
If a saved connection is updated with credentials for a different organisation, all PC bindings are reset automatically. Commands will stop reaching PCs through GGBOOT until you rebind them.
How do I reconnect the game drive on all PCs at once?
In the PC ↔ GGBOOT client section, click 'Reconnect game drives on all PCs'. PCs will see the updated files from the server. Each PC's write overlay is discarded — unsaved player data will be lost.
IZI LLC (ООО «ИЗИ»), TIN 7842227686, OGRN 1257800012249, office 1, premises 3-N, lit. A, 15-17 Perekupnoy lane, Saint Petersburg, 191024, Russia, admin@izi.is · Cookie settings