<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Template on Notities</title><link>https://19cc27e0.backup-website.pages.dev/en/tags/template/</link><description>Recent content in Template on Notities</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 15 Jul 2026 23:50:02 +0200</lastBuildDate><atom:link href="https://19cc27e0.backup-website.pages.dev/en/tags/template/index.xml" rel="self" type="application/rss+xml"/><item><title>Proxmox Lab — Windows Server 2022 Template Preparation</title><link>https://19cc27e0.backup-website.pages.dev/en/blog/2026-proxmox-windows-server-2022-template-preparation/</link><pubDate>Tue, 31 Mar 2026 10:00:00 +0100</pubDate><guid>https://19cc27e0.backup-website.pages.dev/en/blog/2026-proxmox-windows-server-2022-template-preparation/</guid><description>&lt;p&gt;This guide covers the complete process of preparing a freshly installed Windows Server 2022 VM as a reusable Proxmox template. All future VMs (CA server, member servers, etc.) are cloned from this template, saving significant time and ensuring a consistent baseline across the entire lab.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;📄 &lt;strong&gt;Download the full guide with screenshots:&lt;/strong&gt;
&lt;a href="https://19cc27e0.backup-website.pages.dev/documents/WS2022-in-Proxmox-Template-Preparation-Guide.docx"&gt;WS2022-in-Proxmox-Template-Preparation-Guide.docx&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;hr&gt;
&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;p&gt;The full process consists of these steps:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Install VirtIO guest drivers&lt;/li&gt;
&lt;li&gt;Run Windows Update — fully patch the OS&lt;/li&gt;
&lt;li&gt;Apply performance tweaks&lt;/li&gt;
&lt;li&gt;Basic housekeeping — timezone, RDP, IE Enhanced Security&lt;/li&gt;
&lt;li&gt;Sysprep — generalize and shut down&lt;/li&gt;
&lt;li&gt;Convert to template in Proxmox&lt;/li&gt;
&lt;/ol&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Warning:&lt;/strong&gt; Never boot the VM after Sysprep. If you do, the generalization is consumed and the template must be rebuilt from scratch.&lt;/p&gt;</description></item></channel></rss>