Guide · Office PCs
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.
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.
| Ordinary PC | Network-booted PC | Virtual desktop (VDI) | |
|---|---|---|---|
| Programs run on | The PC | The PC (its own CPU, memory, graphics) | A server |
| System disk lives on | The PC's drive | Central storage | Central storage |
| What crosses the network | Nothing at boot | Disk reads and writes | The screen, keyboard, mouse and audio |
| Managed centrally | Little, unless you add imaging tools | System disks, shared images, recovery points | The whole desktop session |
| The trade-off | Every disk is separate work | PCs need the storage network to start and run | Server 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.

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.
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.
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.
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.
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.
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.
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.
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.
No. A PC that runs from a network disk needs the network and the storage while it runs.
Yes. You build the Windows template from your own licensed ISO; Nodekeeper does not supply Windows.
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.
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.
Manage websites, office PCs and servers from one panel on your own hardware.