Skip to content

Connecting NetX to IZI

Published: · IZI Team

NetX is a third-party network-boot platform with its own club server. Once connected to IZI CRM, the club captures the reference image, reboots PCs and watches the image state of each PC right in CRM, without logging into the NetX panel separately.


RequirementDetails
A club in NetXA club set up in the NetX panel. Its club ID is taken from its settings.
IZI permissionsBOOT_CONFIG_MANAGE to configure the connection.
PC namesPC names in IZI and in NetX must share the same number (for example, “01” and “pc01”).

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

FieldWhat to enter
NetX club IDThe club identifier from the NetX panel.
Scheduled auto-updateOptional. The schedule on which IZI reboots PCs by itself so they pick up the new image.

IZI reaches NetX through the NetX cloud, so the club needs no public IP address, no port forwarding and no allowlisting of our address on the club server.

Click Save, then Test connection: CRM checks that the club is reachable in NetX. If the check fails, CRM shows the reason:

  • NetX did not accept the access key — contact IZI support;
  • NetX does not know a club with this ID — check the identifier in the NetX panel;
  • the NetX cloud could not reach the club’s server — check that the server is on and online;
  • a failure on the NetX side — try again later.

To change the ID, click Change. Delete disconnects the club from NetX: PCs will no longer be managed through CRM.


IZI links a PC to NetX by the number in its name: “01” in IZI and “pc01” in NetX are the same computer. A PC that is not in NetX, or whose name has no number, is not visible to IZI and cannot be managed.


  1. Prepare the donor PC: install and configure everything the image should contain.
  2. Open Control Center, choose Create reference image, then pick the PC.
  3. IZI marks the PC in NetX as the reference and reboots it. The disk is captured during the reboot.

NetX does not accept a PC as the reference if it is off, has just connected and has not reported its startup yet, has lost its network, or skipped a disk reset. In that case CRM explains why: wait a minute, or reboot the PC and try again.

After the capture, NetX spends about ten minutes preparing copies for the other PCs. During that time the Apply to all button is blocked with the hint “The vendor is still preparing the reference”: a reboot now would bring PCs back to the previous image.


Rebooting a NetX PC returns its disk to the reference, so updating the image comes down to a reboot.

  • By hand. Apply to all reboots the club’s idle PCs. Re-image on a single PC returns it to the reference and erases local changes on its disk; if a session is running on that PC, CRM warns that it will be interrupted.
  • On a schedule. If a schedule is chosen in the connection, IZI checks every ten minutes whether it is time to update and, within the allowed time, reboots only idle PCs whose image is out of date. Without a schedule, auto-update is off.

Busy PCs (a session is running) are skipped by the bulk update: they update once they become free.


On each PC’s boot marker in Control Center there is a tooltip: the image is current or outdated, the amount of accumulated changes, and the connection speed in Mbit/s.


Frequently asked questions

What do I need to connect NetX to IZI?

Just the club ID from the NetX panel. You do not need to enter a server address, port or password: IZI reaches NetX through its cloud. Open the club in CRM, go to Boot, open the NetX card, enter the ID and save.

How does IZI find the right PC in NetX?

By the number in its name. PC '01' in IZI and 'pc01' in NetX are treated as the same computer. If a name has no digits, or the numbers differ between IZI and NetX, IZI cannot manage that PC.

How do I capture a reference image from a PC?

In Control Center choose 'Create reference image' and pick the PC. IZI marks it in NetX as the reference and reboots it. The image is captured during the reboot, and then NetX spends several minutes preparing copies for the other PCs.

Why does 'Apply to all' not work right after capturing a reference?

While NetX is preparing the reference (about ten minutes), rollout is blocked: a reboot now would bring PCs back to the previous image. The button works again once the reference is ready.

Do NetX PCs update on their own?

Only if you pick a schedule in the 'Scheduled auto-update' field. Without a schedule, auto-update is off and PCs are updated with the buttons by hand. On a schedule, IZI reboots only idle PCs whose image is out of date.

About IZI