For example, in Windows 7 you could use Sysprep to remove computer-specific and operating system-specific installation data from Windows 7, configure Windows 7 to boot in audit mode, configure Windows 7 to boot to the Windows Welcome screen, or reset Windows Product Activation (WPA) on the system up to three times.
Active4 years, 9 months ago
I have been working with the Windows Automated Installation toolkit and FOG lately, and have made several over the past month or so. Something I've noticed when running sysprep after setting up an image is that the unattend file is processed before other sysprep tasks run.
My question is this: where is the unattend file stored on disk after you install Windows? If I can modify/add this file after installation has already completed, it would save us time in having to recreate installation media with unattend.xml at the root of the installation source every time we make a change to the answer file.
To work around this we are currently using an installation USB but some systems refuse to work properly when installing from USB, and it is a hassle to burn a new DVD every time we get a model that doesn't play nicely with a USB-based Windows installer.
Bender the GreatestBender the Greatest44111 gold badge77 silver badges1414 bronze badges
1 Answer
The various locations where an answer file can be or is located during different stages of Windows Setup are listed here:
WinOutreach2WinOutreach2
Not the answer you're looking for? Browse other questions tagged windows-7windowssysprepwaik or ask your own question.
![Location Location](/uploads/1/2/6/0/126084758/623624473.png)
The System Preparation Tool (Sysprep), is meant for System Administrators and OEMs, to automate the deployment of Windows operating system. Once you have performed the initial setup steps on a single computer, you can run the Sysprep tool to prepare the sample computer for cloning and automate the deployment on other computers. It can be found in the WindowsSystem32sysprep folder.
System Preparation Tool – Sysprep
You can use Sysprep along with other deployment tools to install Windows operating systems onto new hardware. It prepares a computer for disk imaging or delivery to a customer by configuring the computer to create a new computer security identifier (SID) when the computer is restarted. In addition, the Sysprep tool cleans up user-specific and computer-specific settings and data that must not be copied to a destination computer.
This video demonstrates how to capture a custom Windows system image using the System Preparation Tool (Sysprep) to generalize the installed image and ImageX to capture the contents of the generalized system image for re-deployment to other computers – including different hardware types.
You can get more information about SysPrep at TechNet.
Do note that KB828287 explicitly mentions that Microsoft does not support the following Sysprep scenarios:
- To create images of an installation that has been upgraded. Microsoft however supports the use of Sysprep to create images of an installation that has been updated with a service pack.
- To run Sysprep, on a a computer that has been running in production for extended period of time, then create a new image or clone from the computer. Sysprep is designed to prepare new installations of Windows for imaging.
- To run sysprep after imaging or cloning production computer for the purpose of changing the SID and computername to join the domain and make the computer unique.
- To install an operating system from an image if the image was created by using a computer that has a different or incompatible Hardware Abstraction Layer (HAL). This limitation applies only to Windows XP and to Windows Server 2003. Starting with Windows Vista, Sysprep includes a Hardware Abstraction Layer (HAL) independent version in the “out of box” installation.
- To create a new image of a system that was originally created by using a custom OEM installation image or by using OEM installation media. Microsoft only supports such an image if the image was created by the OEM manufacturer.
- Microsoft also does not support the use of Sysprep to install an operating system from an image if the image was created by using a computer whose motherboard has a different manufacturer, or if the image was created by using a computer with the same configuration but from a different manufacturer.
- If another user profile has been copied over the default user profile, Microsoft does not support the use of Sysprep to create a new image of the installation.
- Microsoft does not support using Sysprep to install an operating system from an image if the image was created by using a computer that has a different processor.
Windows 7 Sysprep Guide
You can easily identify a Windows installation which has been created with the Sysprep Tool.
![Windows 7 Sysprep Location Windows 7 Sysprep Location](/uploads/1/2/6/0/126084758/497409719.png)
Sysprep Windows 7 Image
- Check for a CloneTag value in the registry. Sysprep places the CloneTag value in the HKEY_LOCAL_MACHINESystemSetup key, noting the date and time the image was prepared for duplication.
- Look in the HKEY_LOCAL_MACHINESystemSetup registry key for a cmdline that reads “Setup –newsetup -mini.” This places GUI-mode Setup in the Mini-wizard phase.
- Check for an OemDuplicatorString value. This used by Original Equipment Manufacturers (OEMs) to place a tag on systems they create. This is added using an answer file (Sysprep.inf) for the Mini-Setup Wizard.
- Check for the existence of Setupcl.exe. This is the file that changes the Security IDs (SIDs) on the system. Look in the %SystemRoot%System32 folder for this file.
If you need more information on how to identify when the System Preparation Tool for Windows NT 4.0 is used on a computer visit KB180962. See this post to Resolve issues when you clone Windows 8 installation media using Sysprep tool.
Want to read about Windows Image Boot (WIMBoot)?
TIP: Download this tool to quickly find & fix Windows errors automatically
Related Posts: