CloudImage
Book a demo
On-site infrastructure

Site Server - local cache & Network Boot

An optional Windows box on a customer LAN that does two things: it caches CloudImage content so the first device pulls each WIM / driver / app from the cloud and every subsequent device on that LAN gets it at LAN speed, and it can network-boot devices into CloudImage with no USB. Both are a big win for ransomware-recovery scenarios where you are rebuilding many machines on a bandwidth-constrained site.

site-servers
CloudImage Site Servers page

What it is

  • A lightweight Windows service (CloudImageSiteServer) that runs as an HTTPS content proxy on port 8443 (configurable).
  • Runs on any Windows box - Server or client OS. No WDS or special roles required.
  • Lazy cache: fills as you deploy - no pre-seeding needed.

How devices use it - automatic

You do not rebuild or reconfigure boot media. Any device imaging on that LAN (with normal cloud boot media) checks in with the cloud, discovers the site server, and routes content through it automatically, with fallback to the cloud if the server is absent or unreachable. Trust is anchored in the cloud (the agent pins the thumbprint the cloud vouches for); only the large content downloads route through it - the control plane stays on the cloud.

Setup

  1. Portal → Site Servers → Add Site Server. Copy the one-time enrollment token that's shown.
  2. On a Windows box on the customer LAN (give it a static LAN IP), run the installer as Administrator:
    powershell -ExecutionPolicy Bypass -File .\install.ps1 -EnrollToken "<token>"
    This installs the CloudImageSiteServer service (HTTPS :8443, self-signed cert), opens the inbound firewall port, and starts the service.
  3. Verify: the portal Site Servers row shows Last seen, version, LAN address, and thumbprint; and https://<box-ip>:8443/healthz returns status and cacheBytes.

Test it

  1. Image device #1 on that LAN. Watch cacheBytes grow on /healthz - the device pulled content from the cloud and the server cached it.
  2. Image device #2 with the same task sequence. Content comes down at LAN speed (cache hit). The deploy log shows (via site server cache: https://<ip>:8443).

Notes

  • Upgrade: re-run install.ps1 with no token. Config, cache, and TLS cert are preserved.
  • Internet still required: the first pull per content item goes cloud → site server → device. It's a cache, not an offline mirror.
  • Firewall: the installer opens TCP <port> automatically (idempotent Windows Firewall rule). If firewall cmdlets are unavailable the installer logs a warning and continues - open the port manually in that case.

Network Boot (image devices with no USB)

A Network-Boot-enabled Site Server boots devices into CloudImage WinPE straight over the local network - no USB stick, no ISO, no WDS. Ideal for mass ransomware recovery: rack up the devices, network-boot them all from the one Site Server, and image in parallel.

How it works: the Site Server answers UEFI network-boot requests on the LAN as a proxyDHCP responder - it coexists with the customer's existing DHCP and never hands out IP addresses. A booting device loads CloudImage WinPE from the Site Server's cached base image, discovers the Site Server, and pulls its per-customer config automatically - then images exactly as a USB boot would, with the same task sequences, branding, and licensing.

  • No USB, no WDS - the Site Server is the boot source. One Network-Boot Site Server per network subnet; UEFI x64 devices.
  • UEFI Secure Boot supported - CloudImage serves a Microsoft-signed boot chain, so devices with Secure Boot enabled boot without disabling it or enrolling custom firmware keys.
  • Same boot image - the CloudImage WinPE image is reused; the Site Server caches it and keeps it current automatically.

To enable: the Site Server must be on the Network-Boot build (the boot binaries are included). Then Portal → Site Servers → your server → Network Boot → pick the boot image → Enable. The status moves Enabled → Ready once the image is cached and the boot responders are live. Set the target devices to UEFI network boot and they load CloudImage automatically.

Three ways to boot a device: USB, ISO, or Network Boot. Network Boot is fastest when you're imaging many machines at one site.