Install Windows from a custom ISO

ServersCamp VMs can boot straight from an installer ISO instead of an OS template. This is how you run Windows Server: the catalog carries Windows Server 2025, you bring your own license, and the whole installation happens in the browser console.

What the wizard enforces

  • Sustained profile only. Windows is not offered on Burst classes.
  • At least 2 vCPU / 4 GB RAM and a 50 GB or larger disk.
  • A minimum disk class: the wizard hides classes too slow for a comfortable Windows install.

The wizard applies all of this automatically when you pick the Windows image; you cannot select an invalid combination.

Step 1: create the VM from the ISO

  1. Go to Virtual Machines → Create VM and switch the source to Install from ISO
  2. Pick Windows Server 2025 as the boot image
  3. Pick hardware, size and disk within the enforced minimums
  4. Select your network and click Create

The VM boots from the installer ISO. A second CD drive with the virtio driver package is attached automatically: you will need it during setup, because Windows ships without drivers for high-performance virtual hardware.

Step 2: install through the web console

  1. Open the VM's Console tab and click Open Console
  2. Walk through Windows Setup until the disk selection screen. The list will be empty: that is expected
  3. Click Load driver → Browse, open the virtio CD drive and pick the storage controller driver for your Windows version. The disk appears
  4. Continue the installation normally and set the Administrator password
  5. After first login, install the remaining drivers from the same virtio CD (run the bundled installer): network, memory ballooning and the guest agent in one pass

Step 3: detach the ISO and open RDP

  1. On the VM details page, eject the installer ISO so the VM boots from disk from now on
  2. Enable Remote Desktop inside Windows
  3. Allow inbound TCP 3389 in the VM's security group (Security Groups tab)
  4. Connect with any RDP client to the VM's public IPv4
Licensing: Windows Server images are bring-your-own-license. ServersCamp provides the infrastructure; activation and licensing are between you and Microsoft.

What's next?