Sysprep Windows 7 Machine Start to Finish
This is the old version, please see the new Sysprep a Windows 7 Machine – Start to Finish V2.
Last Updated on 07.04.11
This is a step by step guide on Sysprepping a Windows 7 machine from start to finish. I cannot take full credit on this because my first article had so many helpful comments and discussions that this is simply a combination of all the good advice written into a working guide. (I would especially like to thank George for his input on Cscript for auto activation and Nathan for input on Sysprep Audit Mode). This will guide you through the following:
- Audit Mode
- Building the unattend.xml file in WSIM
- copyprofile=true command to copy the default profile (no manual copy)
- Prompt for a computer name
- Enable Administrator account
- Administrator account logs in first time automatically
- Activate windows automatically with Cscript;
- Successfully copy over taskbar icons;
- Delete unattend.xml file automatically upon completion of re-image.
Here is a list of what you will need:
- WAIK RTM : KB3AIK_EN.iso Version 3.0 (Read our Tutorial).
- Supplement for WAIK SP1 : waik_supplement_en-us.iso (Read our Tutorial).
- Windows Vista or Windows 7 Machine to build the XML file on
- ISO or DVD of Windows 7 Installation (x32 or x64)
- WinPE Boot Environment : theITBros WinPE 3.1 BootLoader
First we are going to walk through building the unattend.xml file (answer file) and then we will walk through the actual Windows 7 imaging process.
PART 1 – XML FILE CREATION
Step 1
If you have a Windows 7 installation DVD, insert it now. Or if you have an ISO of 7, go ahead and extract it to a folder on your desktop. (I recommend 7-zip).
Step 2
Launch Windows System Image Manager. Your start menu should look like the image below:
Step 3
Under the “Windows Image” header, right click and select new image.
Step 4
You will now want to browse to the .CLG file in your Windows 7 installation (I am using Windows 7 Enterprise x64 in my example). It is located in the sources folder. See Image below. You can select either the .clg file or the install.wim. Both will have the same result.
Step 5
Now we need to create a new answer file. Go to the file menu and select “Create New Answer File.” Right after creating one, go ahead and simply go to file menu and select “Save Answer File.” This will give your XML file a name and save location. I chose to name mine unattend.xml. Now you see we have two category folders, Components and Packages. Under the Components folder you see that we have 7 options:
- 1 windowsPE
- 2 offlineServicing
- 3 generalize
- 4 specialize
- 5 auditSystem
- 6 auditUser
- 7 oobeSystem
Step 6
These are very important as these are the steps in which the unattend.xml file is sequenced.
The next part is a little confusing. You are going to add components, from under the “Windows Image” section on the bottom left hand side to the passes on your Answer File. To add a component, you can right click on them and select “add to # pass”. There are many different options you can add, but they have to be done in a certain order and pass otherwise your sysprep might fail. I am simply going to use the one I created as the example.
Here is more information about adding options under the passes:
1 windowsPE
Nothing required in my example.
2 offlineServicing
Nothing required in my example.
3 generalize
amd64_Microsoft-Windows-Security-SPP_6.1.7600.16385_neutral
Set 1 for SkipRearm to allow up to 8 rearms
4 specialize
amd64_Microsoft-Windows-Deployment_6.1.7600.16385_neutral
Order: 1
path: net user administrator /active:yes
WillReboot: Never
RunSynchronousCommand[Order="1"]
RunSynchronous
amd64_Microsoft-Windows-Security-SPP-UX_6.1.7600.16385_neutral
SkipAutoActivation: true
amd64_Microsoft-Windows-Shell-Setup_6.1.7600.16385_neutral
Computer Name: Leave blank (we will deal with this at the end)
CopyProfile: true
Registered Organization: Microsoft (you must leave this in this section)
Registered Owner: AutoBVT (you must leave this in this section)
ShowWindowsLive: false
TimeZone: Pacific Standard Time
(Please view TimeZone settings here -> http://technet.microsoft.com/en-us/library/cc749073%28WS.10%29.aspx)
You can delete other sub-header components if you don’t need them.
5 auditSystem
Nothing required in my example.
6 auditUser
Nothing required in my example.
7 oobeSystem
amd64_Microsoft-Windows-International-Core_6.1.7600.16385_neutral
InputLocale: en-us
SystemLocale: en-us
UILanguage: en-us
UserLocale: en-us
amd64_Microsoft-Windows-Shell-Setup_6.1.7600.16385_neutral
RegisteredOrganization: Your Company Name
RegisteredOwner: Your Name
AutoLogon
Password: Administrator Password
Enabled: true
LogonCount: 5
Username: administrator
FirstLogonCommands
CommandLine: cscript /b c:\windows\system32\slmgr.vbs /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX (windows 7 license key)
Order 1
RequiresUserInput: false
CommandLine: cscript /b c:\windows\system32\slmgr.vbs /ato
Order 2
RequiresUserInput: false
SynchronousCommand[Order="1"]
SynchronousCommand[Order="2"]
OOBE
HideEULAPage: true
NetworkLocation: Home
ProtectYourPC: 1
UserAccounts
Password: Administrator Password
Action: AddListItem
Description: Local Administrator
DisplayName: Administrator
Group: Administrators
Name: Administrator
LocalAccount[Name="Administrator"]
AdministratorPassword: Administrator Password
LocalAccounts
If you have questions, look at my image above to see full layout of components, it should help.
Step 7
K, now go ahead and save your answer file as unattend.xml.
Step 8
If you want the sysprep to prompt for a computer name you need to remove a line from your XML file. Open up your XML file you saved with notepad and remove the following line:

PART 2 – IMAGING PROCESS / RUNNING SYSPREP
Step 9
Install Windows 7 (Enterprise) from CD or USB flash drive, when you arrive at the welcome screen and it asks you to create a username, hit ctrl+shift+f3.
This will reboot your machine and put your windows build in ‘audit’ mode.
Step 10
On reboot, you’ll automatically be logged in under the built-in Administrator account. A sysprep GUI box will appear, but you can close it and NOW begin to customize your profile.
Step 11
Install any software/drivers, make any profile customizations, etc.
If you need to reboot, the computer will boot you back into the Administrator account. You will be stuck in this audit mode until you run sysprep with the /oobe parameter. After doing so, sysprep will delete/clean up the Administrator account, but if you have copyprofile=true in your unattended answer file, it will copy the customized Admin account to the default profile before deleting it.
Step 12
On the PC you are going to be running sysprep on, you need to create a folder called scripts in this directory: %WINDIR%\Setup\. Now you are going to create a CMD file within the %WINDIR%\Setup\Scripts directory. Right click and make a new text file called SetupComplete.txt. Remove the .txt extension and replace that with .cmd. You now have a SetupComplete.cmd file which windows will read the first time it boots up from the sysprep. We need to place a script inside the CMD file. Edit the cmd file with notepad and insert this line: del /Q /F c:\windows\system32\sysprep\unattend.xml. This script will delete your unattend.xml file after it has been used. The unattend.xml file is also copied to the C:\Windows\Panther directory, so you will want to add a second line to the CMD file, del /Q /F c:\windows\panther\unattend.xml. If you have passwords or cd keys stored in that xml file you don’t have to worry about it being left on the computer.
UPDATE AS OF JUNE 16TH: Read my Taskbar Icons Tutorial before continuing.
Step 13
Once you have everything configured correctly, Copy or move your unattend.xml file to : C:\windows\system32\sysprep. Now to run sysprep, navigate to that sysprep folder, hold SHIFT and right click and select “Open New Command Windows Here”. Next, input the following commands:
sysprep /generalize /oobe /shutdown /unattend:unattend.xml
Step 14
Turn the computer back on and boot to WinPE 3.1 environment (USB stick or CD/DVD). You can use my theITBros WinPE3.1 BootLoader to boot up from USB or CD and capture your image. Capture image and save image to network location.
A Dell 960 or GX755 is a good standard for capturing when you want a generic image for use with multiple systems. Might require injecting additional drivers for 3rd party brands, HP, etc. Most should work though right out of the box.
Step 15
On reboot, Windows will run out of the box, as the /oobe is intended. As long as you put your cd key into the unattend.xml file, windows will be activated automatically in the background, you will be automatically logged into the administrator account, and the unattend.xml file is deleted. You are now ready to use the computer or join it to the domain. Enjoy!
References
I also recommend reading this article, “Windows 7 Sysprep – Tips & tricks.”
Incoming search terms:
- sysprep
- how to sysprep windows 7
- Sysprep for Windows 7
- windows 7 sysprep guide
- sysprep win7
- win7 sysprep
- it bros sysprep
- sysprep win 7
- it bros sysprep windows 7
- where is sysprep in windows 7




Pingback: Taskbar Icons with Windows 7 Sysprep - Windows Walkthroughs
Pingback: Sysprep a Windows 7 Machine
Pingback: Install WAIK supplement for Windows 7 SP1 - The IT Bros - We Know So You Don't Have To
Pingback: Windows 7 Imaging train wreck - Altirigos
Pingback: Windows 7 - minisetup equivilant?
Pingback: [WDS] WDS Unattended answer files
Pingback: Automate Windows 7 Activation - Altirigos
Pingback: A Collection of Resources | IT LIVES!
Pingback: 3 Tips To Speed Up Workstation Deployment | smartertools
Pingback: 3 Tips To Speed Up Workstation Deployment « SmarterTools' Insights
Pingback: MDT Sticky...? MDT
Pingback: Deploying Windows 7 SP1 64 Bit: Station Will Not Join Domain
Pingback: Sysprep Windows 7 and Deployment « Noble Paladin
Pingback: IT Musings » Blog Archive » Windows 7 Sysprep
Pingback: theITBros.com PR4 Wordpress Blog, 143 Unique Articles, Facebook, Forum, Twitter | www.flippafriends.com
Pingback: Windows 7 and mandatory profile | Peter Luk's Blog
Pingback: Windows 7 disk backup and clone for deployment to multiple systems - Admins Goodies
Pingback: Universal Windows 7 Image?? - TechExams.net IT Certification Forums
Pingback: DISM, WIM SIM topics - TechExams.net IT Certification Forums
Pingback: Microsoft Sysprep: What does Sysprep really do? | SysAdminCircus
Pingback: Building an App-V Lab Part 1: base image creation – packageology
Pingback: Windows 7 Sysprep « cobracommunications
Pingback: Win8 CP migration to Z77 Ivy Bridge. - Page 2 - Windows 8 Forums
Pingback: Software Pack for New Computers - Computer Forums
Pingback: SCCM Links « vanwelt
Pingback: Windows 7 Imaging.
Pingback: WDS - Prompt to Enter Computer name (Using WDS unnatend.xml selected on the server)
Pingback: Windows 7 Boot Problems after deploying with Imagex
Pingback: TheITBros.com - The Figures of 2012 - The IT Bros