# Windows Server 2022 Standard Evaluation

Validated private CloudStack KVM template remediated and promoted on 2026-08-12. This is an Evaluation image; no product key is included.

## Artifact

- File: `windows-server-2022-evaluation.qcow2`
- Format: standalone, uncompressed sparse QCOW2
- Architecture: x86_64
- Virtual disk: 50 GiB (53687091200 bytes)
- Exported file: 11739267072 bytes
- SHA-256: `1192a70fa46194f14e17261ec9376322e5b46eedcbdb6ff9c27b0493a87e8d07`
- Mirror URL: https://cloud-mirrors.noc.sh/windows-server-2022-evaluation/windows-server-2022-evaluation.qcow2
- Final CloudStack template UUID: `cd91d395-c9c2-4980-92e1-66079ed72003`
- Retained source ISO UUID: `31cfae98-13ff-4fa0-93c8-96effe94f1e2`

## CloudStack registration

Register privately with:

- Hypervisor: KVM
- Format: QCOW2
- OS type: Windows Server 2022 (64-bit)
- HVM: Yes
- Password enabled: Yes
- SSH key enabled: No
- Public / Featured: No
- `keyboard=us`
- `kvm.guest.os.machine.type=pc-i440fx-8.0`
- `rootdisksize=50`
- `UEFI=LEGACY`

In this CloudStack 4.22 environment, `UEFI=LEGACY` is the value that reproduced the validated pflash/OVMF boot of this Windows Server 2022 image. The effective guest CPU remains `qemu64`. Do not copy the Windows Server 2025 host-model/legacy-BIOS profile onto this template without a separate rebuild and acceptance test.

## Verification

```bash
sha256sum windows-server-2022-evaluation.qcow2
qemu-img check windows-server-2022-evaluation.qcow2
qemu-img info windows-server-2022-evaluation.qcow2
```

Expected SHA-256:

```text
1192a70fa46194f14e17261ec9376322e5b46eedcbdb6ff9c27b0493a87e8d07  windows-server-2022-evaluation.qcow2
```

Deploy a fresh Pro VM with an explicit password and do not interact with the console during first boot. Wait for OOBE and the delayed CloudStack password service. Validate QEMU Guest Agent, exact Administrator credential, RDP, WinRM disabled, reboot persistence, and absence of both Unattend files and `SetupComplete.cmd`.

The 2026-08-12 acceptance and canonical-import smoke tests passed. The remediation added only a self-deleting `SetupComplete.cmd` that removes `C:\Windows\Panther\Unattend.xml` and `C:\Windows\System32\Sysprep\Unattend.xml` after OOBE; no Windows components were removed.