Provisioning Windows Server for hosting or development no longer requires a physical machine or a rushed template. There are two reliable paths — a local Hyper-V VM for development and a cloud template for production — and each has a different set of decisions around licensing, disk layout, and networking. This guide walks both. For the broader platform context, see our Windows VPS overview.
Path One: Hyper-V on Local Hardware
Hyper-V on Windows 10 or 11 Pro is the fastest route to a development server. Enable the Hyper-V feature, open the manager, and create a Generation 2 VM with a virtual switch. Two switches matter: an external switch bridges the VM to your physical NIC for network access; an internal switch keeps it isolated for testing. For development, an external switch plus a NAT rule for RDP is the usual setup.
Allocate a fixed 4 GB RAM and 2 vCPUs to start, and use a dynamically expanding VHDX initially but convert to fixed once the system is stable, because dynamic disks fragment and slow down under write-heavy workloads. Enable checkpoints before major configuration changes; they are far cheaper than reinstalls.
Path Two: Cloud Provider Templates
Cloud providers offer pre-built Windows Server images that boot in minutes. The decisions here are which edition to deploy and how to attach storage. Choose the edition matching your workload: Standard for general hosting, Datacenter when you plan to run many Hyper-V guests on the same host. Avoid the temptation of the smallest instance type for hosting — Windows Server itself needs 2 GB or more just to run comfortably before IIS.
Attach a separate data disk for application and database files rather than putting everything on the system volume. This keeps OS growth separate from data and lets you resize storage without resizing the boot disk.
Licensing: The Part That Surprises People
Windows Server licensing is per-core and per-edition. Cloud providers usually bundle the license into the hourly price; local Hyper-V requires you to own the license. If you run many guests locally, Datacenter’s unlimited virtualization rights often cost less than buying Standard per host. For a single guest, Standard is sufficient. Check that your provider’s bundled license covers the edition you deploy.
Disk Layout That Survives
Use a dedicated data volume for IIS content, SQL Server data and log files, and backups. Place SQL log files on a separate volume from data files to improve write performance. Enable BitLocker on data volumes if the host is not physically controlled, and keep the recovery key somewhere outside the server. A thought-through disk layout saves a painful migration later.
Networking Basics
Assign a static private IP, configure DNS to your domain’s nameservers or a public resolver, and open only the ports you need — 80, 443, and an alternate RDP port rather than the default 3389. On a cloud VM, also confirm the provider’s firewall reflects the same rules as Windows Firewall, because the two are separate layers. Test from outside before you announce the server is ready.
First-Boot Checklist
Rename the machine, set the time zone, install updates, enable Windows Firewall on all profiles, configure WinRM or SSH for remote management, and create a snapshot before installing applications. Record the machine name, IP, and credentials in your password manager. This fifteen-minute routine prevents most day-one problems and makes the server reproducible.
Whether you build locally with Hyper-V or deploy a cloud template, the sequence is the same: pick the edition, isolate data on its own volume, confirm the license covers it, control the network surface, and snapshot before changing anything. The Windows VPS overview covers the managed alternative if you would rather not run the hypervisor yourself.



