<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Sysprep on Thoughts and Ramblings by Mike</title><link>https://mikedent.io/tags/sysprep/</link><description>Recent content in Sysprep on Thoughts and Ramblings by Mike</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Mike Dent</copyright><lastBuildDate>Tue, 28 Apr 2026 09:00:00 -0400</lastBuildDate><atom:link href="https://mikedent.io/tags/sysprep/index.xml" rel="self" type="application/rss+xml"/><item><title>Guest Customization for Windows in Prism Central 7.5</title><link>https://mikedent.io/post/2026/4/prism-central-guest-customization-windows/</link><pubDate>Tue, 28 Apr 2026 09:00:00 -0400</pubDate><guid>https://mikedent.io/post/2026/4/prism-central-guest-customization-windows/</guid><description>
&lt;p&gt;If you have ever cloned a Windows VM on Nutanix and watched five identical machines come up with the same hostname, the same SID, and a domain join you have to redo by hand, you already know why guest customization matters. For years my workflow involved hand-rolling an unattend XML file for each new template, version controlling them, and then attaching the right one at clone time. It worked. It was also one of those things I would dread refreshing whenever a new Windows release dropped or a customer asked for a slightly different deployment profile.&lt;/p&gt;</description></item></channel></rss>