How to Create a Windows Server Template in VMware - Manual
Create a reusable Windows Server 2022 template in VMware by hand, covering the VM settings that matter for images such as thin disk provisioning and driver cleanup before sealing.
Windows Server Template creation for Home Lab
To create a template, first we need to provision the virtual machine on which we will install Windows Server 2022. Here are a few things to consider when doing so:
Config parameters
1. Disk type
Thin Disk ( this is the default)
Since this is for Home Lab, we have chosen the ThinDisk type. selecting Thin Disk consumes the actual written data as my Laptop’s Disk Space. You can choose the appropriate type
2. SCSI Controller
LSI Logic
vCPU and Memory allocation:
It is recommended to provision your template with the minimum requirements. That way we ensure new VMs are not oversized when the resources aren’t tuned. 2GB of RAM and 2 vCPUs (2 sockets x 1 core) is usually the recommended choice for mixed workload setups.
2vCPU
2GB RAM
LAN segement as Network
Watch the video on How to create a Windows Server template in VMware workstation
What makes a template reusable
Provisioning the VM is the easy part. The thing that makes a template reusable rather than just “a VM I cloned once” is what happens before you convert it:
- VMware Tools / open-vm-tools — install them so the guest reports its IP, responds to graceful shutdown, and exposes paravirtualised devices. Without them, clones boot with degraded performance and no IP reporting.
- Thin provisioning — chosen above because it only consumes space for written data, which matters on a home-lab disk. The trade-off is that a long-running template with a thin disk can fragment; for a short-lived lab image it is the right default.
- Sysprep / sealing — the critical step. Before converting to a template, run Sysprep (
C:\Windows\System32\Sysprep\sysprep.exe /generalize /oobe /shutdown) so each clone gets a fresh SID, computer name and OOBE run on first boot. Skip this and every clone looks identical to the domain — duplicate SIDs, name collisions, and a broken domain join. - Cleanup — remove install media, clear event logs, delete temporary files, and disconnect the ISO. A template that boots with a mounted ISO attached will fail to deploy cleanly later.
- Convert, don’t clone — once sealed, convert the VM to a template in the vSphere/Workstation inventory rather than keeping it as a runnable VM. That protects the golden image from being started and drifted.
After the template exists
From there the usual next steps are: deploy a VM from the template to confirm it boots and joins the domain, snapshot it before patching, and keep one known-good version so a bad update never costs you the whole image.
This is our own notes from a VMware home-lab build; not affiliated with VMware or Microsoft.