Guide · Office PCs

What Is Windows Network Boot? Local Compute, Centralized Disks Explained

Windows network boot starts a PC from a system disk that lives on a server instead of inside the PC. The processor, memory and graphics card of the desk-side machine still run Windows and every application. Only disk reads and writes cross the network. That is why it is sometimes called diskless Windows, and why it is not a remote desktop: nothing is streamed to the screen.

Where compute and disks sit

Picture a 40-seat training room. With ordinary PCs, every seat has its own drive, so every seat is its own small island: reinstalling, backing up and replacing a machine is hand work, one desk at a time. There are two common ways to centralize that, and they move different things.

Where programs run and where the system disk lives, for three ways of running office PCs
Ordinary PCNetwork-booted PCVirtual desktop (VDI)
Programs run onThe PCThe PC (its own CPU, memory, graphics)A server
System disk lives onThe PC's driveCentral storageCentral storage
What crosses the networkNothing at bootDisk reads and writesThe screen, keyboard, mouse and audio
Managed centrallyLittle, unless you add imaging toolsSystem disks, shared images, recovery pointsThe whole desktop session
The trade-offEvery disk is separate workPCs need the storage network to start and runServer capacity must cover every user's compute and graphics

Network boot keeps what the PCs already do well, local processing and a local graphics card, and centralizes the part that is painful to manage: the disk. If your people need a powerful local GPU, or you do not want to size servers for every user's desktop, this is the reason to look at it.

How a PC boots from the network

Boot path of a network-booted office PC The office PC loads signed boot files from the network or from boot media and asks the user to log in. A site node then connects the system disk: Windows over iSCSI, Linux directly from distributed storage. The disk lives in distributed storage as a read-only template version plus a writable disk for this PC. After boot, only disk traffic crosses the network. Office PC Runs Windows or Linux itself CPU · memory Graphics card Screen, keyboard, USB No system disk needed Site node Boot files and login Signed boot system Windows: iSCSI disk Isolated storage network Distributed storage Replicated disks Template (read-only) This PC's own disk 1 · 2 · 3 4 Linux PCs map their block disk straight from distributed storage
Boot path of a network-booted PC. Steps 1 to 4 in the diagram match the numbered list below; after step 4, only disk traffic crosses the network. On a narrow screen, scroll the diagram sideways.
  1. The PC starts from the network (PXE) or from boot media such as a USB stick or an ISO. Either way it loads an iPXE build signed by Nodekeeper.
  2. iPXE loads Nodekeeper's boot system. Each boot file is fetched together with its signature and checked.
  3. The user logs in. The boot system recognizes the registered PC and asks for the user's cloud PC password, plus a one-time code if two-factor authentication is on. The password is verified with SRP-6a, so the password itself is never sent.
  4. The system disk is connected. A Windows PC boots its disk over iSCSI from a site node, with credentials generated for that session. A Linux PC maps its block disk directly from distributed storage.
  5. The operating system starts. From here the PC's own CPU, memory and graphics card run everything. The network carries disk reads and writes.
Boot screen of an office PC after the signed boot files have loaded, waiting at the login prompt; addresses and hardware identifiers redacted
An office PC at step 3: the signed boot files have loaded, the computer is recognized from its registration, and it waits for the user's login.

What the PC and the network need

  • Hardware: x86_64 PCs, BIOS or UEFI, with a network card that can PXE-boot (or a boot USB). Secure Boot must be off.
  • Systems: Windows 10 and 11 (24H2), built from your own licensed ISO; Linux templates for Debian 13 and Ubuntu 24.04. GPU drivers are yours to supply.
  • Windows network cards: each network card model needs a one-time warm-up before a Windows PC can boot from it.
  • Network: a wired network between the PCs and the site node, with the storage traffic on an isolated network. iSCSI data is not encrypted on the wire, so keep it off general-purpose networks.

When network boot fits, and when it does not

It fits

  • Training rooms, labs, call centers and shared workstations with many similar PCs.
  • Offices where reinstalling, replacing or recovering a PC costs a technician's time.
  • Teams that need local graphics performance and do not want to size servers for every desktop.
  • Sites with a dependable wired network to the storage.

It does not fit

  • Laptops that leave the network. There is no offline mode: a PC that cannot reach its storage cannot run.
  • PCs that must run with Secure Boot enforced.
  • Places where the network to the storage is unreliable or shared with heavy traffic.
  • People who need a desktop reachable from anywhere. That is what remote desktop or VDI is for.

Across locations

Network boot works across a wide-area link, so a PC at one location can start from storage kept at another. Every disk read and write crosses that link, so its latency and bandwidth set how the PC feels. For a site with many PCs, put the site node and storage close to the desks; for a small remote office, size the link for the disk traffic.

Three decisions that matter most

1. How the disk reaches the PC

Give storage traffic its own wired network or VLAN, and decide where the site node sits. For Windows, the site node serves the system disk over iSCSI, and Nodekeeper's Windows iSCSI service can take over automatically if a node fails, which reduces hands-on recovery. Linux PCs reach distributed storage directly.

2. How the images are organized

Do not give every PC its own full copy of Windows. Keep one shared, read-only template version and give each PC its own writable disk on top of it. Updates and user data land on that PC's disk only. The next guide goes through this with a capacity example: shared OS images and writable clones.

3. How people get back to work after a problem

Decide before the pilot, not after the first failure. Recovery points let you roll a PC's disk back after a bad update or a mistake. Full cloud-PC disk backups protect against losing the storage cluster itself. If a PC's hardware fails, the user can log in on another compatible PC and the disk follows them. Unsaved work on the old machine is lost, so this is a new login on other hardware, not a transparent hand-over.

How Nodekeeper shortens the work

Network boot is easy to describe and tedious to run by hand: boot files, signatures, iSCSI targets, image templates, per-PC disks, quotas, recovery points. Nodekeeper puts these in one panel, next to your websites and virtual machines.

  1. Build a template from your own Windows ISO, or from a Debian or Ubuntu template, and publish it as a version.
  2. Register each PC. Nodekeeper recognizes it by its network card and hardware ID.
  3. Create a cloud PC from the template for each user. Each PC gets its own writable disk, with disk size and storage quota under your control.
  4. Users start their PCs from the network and sign in with their own cloud PC password.
  5. Take recovery points on a schedule, roll a PC back when needed, and back up whole cloud-PC disks.
  6. Give each team the access its role needs: every permission can be assigned per user group.

Network boot is part of the Business plan. Plans are licensed per node, meaning each machine that runs Nodekeeper. Under today's licensing model, the office PCs that boot from the cluster do not run Nodekeeper and are not counted as nodes.

Questions people ask

Is this the same as VDI or a remote desktop?

No. In VDI the desktop runs on a server and you see it through a display protocol. With network boot the desktop runs on the PC in front of you; only the system disk is somewhere else.

What happens to a user's work if the PC breaks?

The system disk is not in the PC, so a failed local drive does not take the system with it, and the user can sign in on another compatible PC. Work that was not yet written to the disk is lost. Replicas protect against disk failure and are not a backup, which is why recovery points and full-disk backups exist.

Can people work offline?

No. A PC that runs from a network disk needs the network and the storage while it runs.

Do I need a Windows licence?

Yes. You build the Windows template from your own licensed ISO; Nodekeeper does not supply Windows.

Plan a network-booted office

See how the boot path, shared images, recovery points and full-disk backups fit together on the office PC page, or start a trial on your own hardware.

Start Business Trial

30-day trial of Business: monthly subscription, first month $0, card required, once per account, up to 3 nodes. Cancel before day 30 and you are not charged; after that, Business renews at $29 per node per month.

Related

N Nodekeeper

Manage websites, office PCs and servers from one panel on your own hardware.

Support
[email protected] WhatsApp: +817093066006

© 2026 Nodekeeper. All rights reserved.