Deployment on Proxmox VE and Windows Server Core Installation
Creating the optimized virtual machine on Proxmox, injecting VirtIO paravirtualized drivers, and initial Server Core installation.
This initial module details the systems engineering steps required to provision an optimized virtual machine on Proxmox VE, install the Windows Server 2022 Core operating system, and correctly inject VirtIO paravirtualized storage and network drivers.
1. Optimized VM Configuration in Proxmox VE
Sección titulada «1. Configuración Optimizada de la VM en Proxmox VE»To ensure maximum print server performance and reduce CPU overhead, it is essential to structure the virtual machine using VirtIO (KVM Paravirtualized Drivers):
- General: Assign a unique identifier and hostname (e.g.,
w-server-2022). - OS (Operating System): Select the original Windows Server 2022 ISO. Set type as "Microsoft Windows" and version as "11/2022".
- System:
- Bios: OVMF (UEFI) (Recommended for modern GPT partitioning schemes).
- SCSI Controller: VirtIO SCSI Single (Ensures independent IO queues and TRIM support).
- QEMU Guest Agent:
Activado(Essential for allowing safe shutdowns and interacting with the network system from the Proxmox panel).
- Disks:
- Bus/Device: SCSI (with the previously selected VirtIO single SCSI controller).
- Cache: Write back (Optimizes write speed using host RAM).
- IO Thread:
Activado.
- CPU / Memory: Minimum 2 vCores and 4 GB of RAM (Server Core has a minimum consumption of just 1.2 GB at idle).
- Network: Model VirtIO (paravirtualized).
Critical Device Step
Before booting the installation for the first time, add a second virtual CD/DVD drive to the machine and mount the ISO with the official drivers downloaded from Proxmox: virtio-win.iso.
2. Operating System Installation Process
Sección titulada «2. Proceso de Instalación del Sistema Operativo»A. SCSI Disk Driver Injection
Sección titulada «A. Inyección de Controladores de Disco SCSI»Since VirtIO SCSI drivers are not natively integrated into the basic Microsoft installation ISO, the hard drive will not appear in the Windows installation wizard by default:
- In the disk partitioning window, click “Load Driver”.
- Click Browse and navigate to the second CD drive (
virtio-win). - Navigate to the path:
amd64>2k22. - Select and install the driver: Red Hat VirtIO SCSI pass-through controller. The virtual disk will immediately appear available for partitioning and installation.
B. Solution for Offline Disk Lockout (SAN Policy)
Sección titulada «B. Solución al Bloqueo de Disco Offline (Política SAN)»In certain hypervisor configurations, the injected hard drive may report as offline due to restrictive Windows storage policies (Storage Area Network - SAN).
If the installer indicates that the disk is not online, press the key combination <kbd>Shift + F10</kbd> to raise the rescue command console and execute:
diskpartlist diskselect disk 0attributes disk clear readonlyonline diskexit3. Post-Installation Driver and Network Configuration
Sección titulada «3. Configuración Post-Instalación de Drivers y Red»After booting the server for the first time, Windows Server Core will start in a pure black command console. There will be no enabled network interface because the VirtIO network adapter requires manual drivers.
A. Network Driver Installation (PowerShell)
Sección titulada «A. Instalación del Controlador de Red (PowerShell)»- Identify the letter assigned to the VirtIO CD drive (e.g.,
D:orE:) by running in the console:Ventana de terminal Get-Volume - Run the system control driver utility (
pnputil) to force the installation of the paravirtualized network driver (NetKVM):Ventana de terminal :: Reemplaza D: por la letra real de tu lectora virtual detectadapnputil /add-driver "D:\NetKVM\2k22\amd64\netkvm.inf" /install
B. Static IP and Hostname Assignment
Sección titulada «B. Asignación de IP Estática y Nombre de Host»The Command Prompt in Server Core includes an excellent interactive menu-driven configuration utility called sconfig:
sconfigRun the interactive menu to perform the following mandatory network actions:
- Option 2 (Computer Name): Structuredly change the hostname to
w-server-2022and restart the server. - Option 8 (Network Configuration): Select the NetKVM network adapter and assign a static IP address within your segment (e.g.,
192.168.10.10), along with the subnet mask, gateway, and corporate DNS.
4. Installing Print Roles on Server Core
Sección titulada «4. Instalación de Roles de Impresión en Server Core»To enable the local printer queuing and sharing engine, spin up the native print system role by running in PowerShell:
Install-WindowsFeature Print-Services -IncludeManagementToolsRestart-ComputerThe system will restart to compile the new lightweight print services.

