Skip to the main content.

2 min read

Using Sysprep to deploy Windows 2003 VMs

Microsoft System Preparation Tool (Sysprep) is a great tool to use when creating a Virtual Machine environment. You can install a single VM with Windows Server 2003, configure the server the way you wish, then sysprep the server and same the VM file for further server deployments.

This tool removes all unique identifiers from a server which allows you to create clones without affecting already deploy servers. This tool removes the Security Identifier (SID), IP address, computer name, etc. This can be a huge time saver when building a test environment. You can preconfigure various images and store those in an image library for easy deployment.

In order to run Sysprep, you first need to install it. You can get a hold of Sysprep in two ways: it is on the SupportToolsDeploy.cab file on the Windows Server installation media, or you can download it from here. Once you get a hold of the Deploy.cab file, you should extract the contents to a directory on your HD, for example c:Deploy.

This directory contains several useful tools, and you should definitely read the deploy.chm file for instructions and details on the process. There are two files that are of particular importance to the process: sysprep.exe and setupmgr.exe.

For sysprep to work completely automated, it requires an answer file, called sysprep.inf. This answer file contains the “answers” to all the questions asked by the Windows installer during the setup process. The answer file can be created manually with any text editor, but fortunately there is a nice wizard-like tool that can help you generate this file. This tool is the setupmgr.exe program:

This program allows you to generate the sysprep.inf file by presenting you the options and letting you enter the default answer. In order to fully automate an installation, follow these steps on the Setup Manager:

Click Next on the Welcome screenSelect “Create new” and click “Next”Select “Sysprep setup” and click “Next”:

Select the type of system you’re going to sysprep, and click “Next”Select “Yes, fully automate the installation” and click “Next”Now you need to fill in all the information required to complete the process:

Once you complete the execution of the Setup Manager, it creates a new directory in the root of the system drive called sysprep. This directory contains all the information necessary for the Sysprep tool to execute.

Now you need to execute the Sysprep tool, sysprep.exe:

In this tool:

Click “OK” on the warning dialog that appears when running the tool.Select “Don’t reset grace period for activation”Set the “Shutdown mode” to “Shut down”Click on Reseal. That will leave the image ready for copying.Once the image is copied, you can just configure a new virtual machine with the new image, and start it up. The last portion of the Windows setup process will execute:

After a little while (<10min), the machine will reboot, and the process will be completed. You now have a brand new sysprep’d and cloned server up and running!!

Decoding the Azure Stack: Global Azure, Azure Stack Hub, and Azure Stack HCI

Decoding the Azure Stack: Global Azure, Azure Stack Hub, and Azure Stack HCI

As organizations pivot towards a hybrid cloud strategy, understanding the nuances between Global Azure, Azure Stack Hub, and Azure Stack HCI becomes...

Understanding Extended Security Update Options for Windows Server 2012

Understanding Extended Security Update Options for Windows Server 2012

Windows Server 2012/R2, a cornerstone of server operating systems, reached its end-of-life on October 10, 2023. This cessation of regular...

Navigating the Upcoming Changes to the Azure RI Exchange Policy

Navigating the Upcoming Changes to the Azure RI Exchange Policy

As cloud infrastructure becomes central to business operations, it's essential to understand the nuances of cloud resource management for...