Windows 10: Windows 10 XML file generator for unattended setup. 5 Auteur 6 avril 2017 7 Cette version inclut plusieurs programmes utiles pour. Image Manager opens,using this tool,we'll create unattended. Log file and can. Windows 7 Windows 8 Windows 8.1 Windows 10. You may choose to create the autounattend.xml file automatically by clicking 'Download File' link below, or doing it the manual. Place this file in the root of a USB drive and come back to a fresh install of Windows 10. Check out these other useful tools for Windows 10.
-->Answer files (or Unattend files) can be used to modify Windows settings in your images during Setup. You can also create settings that trigger scripts in your images that run after the first user creates their account and picks their default language.
Windows Setup will automatically search for answer files in certain locations, or you can specify an unattend file to use by using the
/unattend:
option when running Windows Setup (setup.exe).Windows settings overview
While you can set many Windows settings in audit mode, some settings can only be set by using an answer file or Windows Configuration Designer, such as adding manufacturer’s support information. A full list of answer file settings (also known as Unattend settings) is in the Unattended Windows Setup Reference.
Enterprises can control other settings by using Group Policy. For more info, see Group Policy.
Answer file settings
You can specify which configuration pass to add new settings:
- 1 windowsPE: These settings are used by the Windows Setup installation program. If you’re modifying existing images, you can usually ignore these settings.
- 4 specialize: Most settings should be added here. These settings are triggered both at the beginning of audit mode and at the beginning of OOBE. If you need to make multiple updates or test settings, generalize the device again and add another batch of settings in the Specialize Configuration pass.
- 6 auditUser: Runs as soon as you start audit mode.This is a great time to run a system test script - we'll add Microsoft-Windows-DeploymentRunAsynchronousCommand as our example. To learn more, see Add a Custom Script to Windows Setup.
- 7 oobeSystem: Use sparingly. Most of these settings run after the user completes OOBE. The exception is the Microsoft-Windows-DeploymentResealMode = Audit setting, which we’ll use to bypass OOBE and boot the PC into audit mode.If your script relies on knowing which language the user selects during OOBE, you’d add it to the oobeSystem pass.
- To learn more, see Windows Setup Configuration Passes.
Note
These settings could be lost if the user resets their PC with the built-in recovery tools. To see how to make sure these settings stay on the device during a reset, see Sample scripts: Keeping Windows settings through a recovery.
![Unattend answer file generator Unattend answer file generator](http://files.easy2boot.com/system_preview_detail_200003329-e037ee122a/XMLtoE2Bv2.0.44.jpg)
Create and modify an answer file
Step 1: Create a catalog file
- Start Windows System Image Manager.
- Click File > Select Windows Image.
- In Select a Windows Image, browse to and select the image file (D:install.wim). Next, select an edition of Windows, for example, Windows 10 Pro, and click OK. Click Yes to create the catalog file. Windows SIM creates the file based on the image file, and saves it to the same folder as the image file. This process can take several minutes.The catalog file appears in the Windows Image pane. Windows SIM lists the configurable components and packages in that image.Troubleshooting: If Windows SIM does not create the catalog file, try the following steps:
- To create a catalog file for either 32-bit or ARM-based devices, use a 32-bit device.
- Make sure the Windows base-image file (SourcesInstall.wim) is in a folder that has read-write privileges, such as a USB flash drive or on your hard drive.
Step 2: Create an answer file
- Click File > New Answer File.The new answer file appears in the Answer File pane.Note If you open an existing answer file, you might be prompted to associate the answer file with the image. Click Yes.
Step 3: Add new answer file settings
- Add OEM info:In the Windows Image pane, expand Components, right-click amd64_Microsoft-Windows-Shell-Setup_(version), and then select Add Setting to Pass 4 specialize.In the Answer File pane, select Components4 specializeamd64_Microsoft-Windows-Shell-Setup_neutralOEMInformation.In the OEMInformation Properties pane, in the Settings section, select:
- Manufacturer=
Fabrikam
- Model=
Notebook Model 1
- Logo=
C:FabrikamFabrikam.bmp
Create a 32-bit color with a maximum size of 120x120 pixels, save it asD:AnswerFilesFabrikam.bmp
file on your local PC, or use the sample from the USB-B key:D:ConfigSet$OEM$$$System32OEMFabrikam.bmp
.We'll copy the logo into the Windows image in a few steps. - Manufacturer=
- Set the device to automatically boot to audit mode:In the Windows Image pane, expand Components, right-click amd64_Microsoft-Windows-Deployment_(version), and then select Add Setting to Pass 7 oobeSystem.In the Answer File pane, select Components7 oobeSystemamd64_Microsoft-Windows-Deployment_neutralReseal.In the Reseal Properties pane, in the Settings section, select Mode=
Audit
. - Prepare a script to run after Audit mode begins.In the Windows Image pane, right-click amd64_ Microsoft-Windows-Deployment_(version) and then click Add Setting to Pass 6 auditUser.In the Answer File pane, expand Components6 auditUseramd64_Microsoft-Windows-Deployment_neutralRunAsynchronous. Right-click RunAsynchronousCommand Properties and click Insert New AsynchronousCommand.In the AsynchronousCommand Properties pane, in the Settings section, add the following values:
Path = C:FabrikamSampleCommand.cmd
Description = Sample command to run a system diagnostic check.
Order = 1
(Determines the order that commands are run, starting with 1.) - Add a registry key. In this example, we add keys for the OEM Windows Store program. Use the same process as adding a script, using
CMD /c REG ADD
.For Windows 10 Customer Systems, you may use the OEM Store ID alone or in combination with a Store Content Modifier (SCM) to identify an OEM brand for the OEM Store. By adding a SCM, you can target Customer Systems at a more granular level. For example, you may choose to target commercial devices separately from consumer devices by inserting unique SCMs for consumer and commercial brands into those devices.Add RunAsynchronousCommands for each registry key to add. (Right-click RunAsynchronousCommand Properties and click Insert New AsynchronousCommand).
See the Unattended Windows Setup Reference for a full list of configuration options.
Step 4: Save the answer file
- Save the answer file, for example: D:AnswerFilesBootToAudit-x64.xml.Note Windows SIM will not allow you to save the answer file into the mounted image folders. Step 5: Create a script
Since we specified a script to run in Step 3, let's create that script now.
- Copy the following sample script into Notepad, and save it as D:AnswerFilesSampleCommand.cmd.
Add the answer file and script to the image
Step 6: Mount an image and add the answer file
- Use DISM to mount a Windows image. To learn how to mount an image, see Mount and modify a Windows image using DISM
- Copy the answer file into the image into the WindowsPanther folder, and name it unattend.xml. The Panther folder is one of the folders where Windows searches for an answer file. Create the folder if it doesn’t exist. If there’s an existing answer file, replace it or use Windows System Image Manager to edit/combine settings if necessary.
- Unmount the image, committing the changes. For example:where C is the drive letter of the drive that contains the mounted image.This process may take several minutes.
![File File](/uploads/1/2/5/8/125864201/314133575.png)
When you apply your image, Windows will process your unattend file and will configure your settings based on what you specified in the unattend.
Learning has never been so easy!
Desktop deployment is typically performed via disk cloning applications. Sysprep can be used to prepare an operating system for disk cloning and restoration via a disk image.
Windows operating system installations include many unique elements per installation that need to be “generalized” before capturing and deploying a disk image to multiple computers. Some of these elements include:
Computer name
Security Identifier (SID)
Driver Cache
Sysprep seeks to solve these issues by allowing for the generation of new computer names, unique SIDs, and custom driver cache databases during the Sysprep process.
Security Identifier (SID)
Driver Cache
Sysprep seeks to solve these issues by allowing for the generation of new computer names, unique SIDs, and custom driver cache databases during the Sysprep process.
Administrators can use tools such as SetupMgr.exe (Windows XP) or the Windows Automated Installation Kit (Windows Vista/7/Server 2008) to generate answer files that Sysprep will process on new computer deployments.
This is a step by step guide on using sysprep to make a Windows 7 machine ready for deployment from start to finish.
24 Steps total
Step 1: Install The Windows Automated Installation Kit (AIK) for Windows 7 onto your computer.
Step 2: After installation finish start Windows System Image Manager from start menu. It will be look like this.
Step 3: Right click on “Select a Windows image or catalog file” under Windows Image and click “Select Windows image” . Point to Sourcedirectory in the Windows 7 DVD, highlight “install.wim” and click open.
Step 4: Right click on “Create or open an answer file” under Answer File and click “New Answer File…”
Step 5: 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. (If you are using 32-bit operating system components will be stating “amd64″ instead of “x86″)
Adding the components:
1- x86_Microsoft-Windows-Security-SPP_6.1.7601.17514_neutral (Right Click and select “Add Settings To Pass 3 generalize“)
2- x86_Microsoft-Windows-Deployment_6.1.7601.17514_neutral (Right Click and select “Add Settings To Pass 4 specialize“)
3- x86_Microsoft-Windows-Security-SPP-UX_6.1.7601.17514_neutral (Right Click and select “Add Settings To Pass 4 specialize“)
4- x86_Microsoft-Windows-Shell-Setup_6.1.7601.17514_neutral (Right Click and select “Add Settings To Pass 4 specialize“)
5- x86_Microsoft-Windows-International-Core_6.1.7601.17514_neutral (Right Click and select “Add Settings To Pass 7 oobeSystem“)
6- x86_Microsoft-Windows-Shell-Setup_6.1.7601.17514_neutral (Right Click and select “Add Settings To Pass 7 oobeSystem“)
After adding all the components to Answer File section it should be look like this.
1- x86_Microsoft-Windows-Security-SPP_6.1.7601.17514_neutral (Right Click and select “Add Settings To Pass 3 generalize“)
2- x86_Microsoft-Windows-Deployment_6.1.7601.17514_neutral (Right Click and select “Add Settings To Pass 4 specialize“)
3- x86_Microsoft-Windows-Security-SPP-UX_6.1.7601.17514_neutral (Right Click and select “Add Settings To Pass 4 specialize“)
4- x86_Microsoft-Windows-Shell-Setup_6.1.7601.17514_neutral (Right Click and select “Add Settings To Pass 4 specialize“)
5- x86_Microsoft-Windows-International-Core_6.1.7601.17514_neutral (Right Click and select “Add Settings To Pass 7 oobeSystem“)
6- x86_Microsoft-Windows-Shell-Setup_6.1.7601.17514_neutral (Right Click and select “Add Settings To Pass 7 oobeSystem“)
After adding all the components to Answer File section it should be look like this.
Step 6: Configuring the components: when you click on the components you would like to configure, properties will appear right hand on the screen.
Step 7: x86_Microsoft-Windows-Security-SPP_6.1.7601.17514_neutral (under 3 generalize)
SkipRearm = 1
Step 8: x86_Microsoft-Windows-Deployment_6.1.7601.17514_neutral (under 4 specialize)
1- Expand it and right click on “RunSynchronous”. Select “Insert New RunSynchronousCommand”. Highlight newly created “RunSynchronousCommand”
2- Order: 1
3- path: net user administrator /active:yes
4- WillReboot: Never
2- Order: 1
3- path: net user administrator /active:yes
4- WillReboot: Never
Step 9: x86_Microsoft-Windows-Security-SPP-UX_6.1.7601.17514_neutral (under 4 specialize)
SkipAutoActivation: true
Step 10: x86_Microsoft-Windows-Shell-Setup_6.1.7601.17514_neutral (under 4 specialize)
1- Computer Name: Leave blank (for automatic naming)
2- CopyProfile: true
3- ProductKey: type your product key
4- Registered Organization: Microsoft (you must leave this in this section)
5- Registered Owner: AutoBVT (you must leave this in this section)
6- ShowWindowsLive: false
7- TimeZone: Pacific Standard Time (for other time zones go to http://technet.microsoft.com/en-us/library/cc749073%28WS.10%29.aspx)
2- CopyProfile: true
3- ProductKey: type your product key
4- Registered Organization: Microsoft (you must leave this in this section)
5- Registered Owner: AutoBVT (you must leave this in this section)
6- ShowWindowsLive: false
7- TimeZone: Pacific Standard Time (for other time zones go to http://technet.microsoft.com/en-us/library/cc749073%28WS.10%29.aspx)
Step 11: x86_Microsoft-Windows-International-Core_6.1.7601.17514_neutral (under 7 oobeSystem)
1- InputLocale: en-us
2- SystemLocale: en-us
3- UILanguage: en-us
4- UserLocale: en-us
2- SystemLocale: en-us
3- UILanguage: en-us
4- UserLocale: en-us
Step 12: x86_Microsoft-Windows-Shell-Setup_6.1.7601.17514_neutral (under 7 oobeSystem)
1- RegisteredOrganization: Your Company Name
2- RegisteredOwner: Your Name
2- RegisteredOwner: Your Name
Step 13: xpend “x86_Microsoft-Windows-Shell-Setup_6.1.7601.17514_neutral” and highlight “AutoLogon”
1- Enabled: true
2- LogonCount: 5
3- Username: administrator
2- LogonCount: 5
3- Username: administrator
Step 14: Expend “AutoLogon” and highlight “Password”
Value: Administrator Password
Step 15: Right Click on “FirstLogonCommands” and select “Insert New SynchronousCommand” do this twice, so you will have two “SynchronousCommand” under “FirstLogonCommands”. Highlight first one.
1- CommandLine: cscript /b c:windowssystem32slmgr.vbs /ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX (windows 7 license key)
2- Order: 1
3- RequiresUserInput: false
4- Highlight second ”SynchronousCommand”
5- CommandLine: cscript /b c:windowssystem32slmgr.vbs /ato
6- Order 2
7- RequiresUserInput: false
2- Order: 1
3- RequiresUserInput: false
4- Highlight second ”SynchronousCommand”
5- CommandLine: cscript /b c:windowssystem32slmgr.vbs /ato
6- Order 2
7- RequiresUserInput: false
Step 16: Highlight “OOBE”
1- HideEULAPage: true
2- HideWirelessSetupInOOBE: true
3- NetworkLocation: Home
4- ProtectYourPC: 1
2- HideWirelessSetupInOOBE: true
3- NetworkLocation: Home
4- ProtectYourPC: 1
Step 17: Expand “UserAccounts” highlight “AdministratorPassword”
1- Value: Administrator password
2- Right click on “LocalAccounts” and select “Insert New LocalAccount”. Highlight new created “LocalAccount”
3- Description: Local Administrator
4- DisplayName: Administrator
5- Group: Administrators
6- Name: Administrator
7- Highlight “Password”
8- Value: Administrator password
2- Right click on “LocalAccounts” and select “Insert New LocalAccount”. Highlight new created “LocalAccount”
3- Description: Local Administrator
4- DisplayName: Administrator
5- Group: Administrators
6- Name: Administrator
7- Highlight “Password”
8- Value: Administrator password
Step 18: Answer file configuration is finish and your answer file should be looks like image below. Now you can save the answer file.
Step 19: Install Windows 7 from CD or USB flash drive, when you see the welcome screen and it asks you to create a username, hit CTRL+SHIFT+F3. This will reboot your machine and restart windows in built in ‘audit’ mode.
Step 20: 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 21: 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 22: 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%SetupScripts 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. Right click the SetupComplate.cmd and select edit, this will open notepad and copy the following lines and paste into the notepad:
1- del /Q /F c:windowssystem32sysprepunattend.xml. This script will delete your unattend.xml file after it has been used.
2- del /Q /F c:windowspantherunattend.xml. The unattend.xml file is also copied to the C:WindowsPanther directory, so you will want to add a second line to the CMD file, 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.
2- del /Q /F c:windowspantherunattend.xml. The unattend.xml file is also copied to the C:WindowsPanther directory, so you will want to add a second line to the CMD file, 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.
Step 23: Once you have everything configured correctly, Copy your unattend.xml file to : C:windowssystem32sysprep. In the same folder, hold SHIFT and right click and select “Open New Command Windows Here” to run sysprep. Enter the following commands to command line:
sysprep /generalize /oobe /shutdown /unattend:unattend.xml
Step 24: I’m using Clonezilla or FOG for taking an image. You can same the image on external HDD or Network resource.
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.
6 Comments
- CayenneLuke.Pettway Jul 10, 2013 at 04:18pmThanks for this, I am looking to do this soon for the computers here so that I don't spend all day restoring computers or installing new ones!
- AnaheimLogan Richards Jul 12, 2013 at 06:12pmWorked great, even when using an OEM disk, it automatically regenerated a new OEM key. This will significantly help us cut down restore/deploy time on our workstations.
- Thai PepperGUIn00b Jul 26, 2013 at 08:38pmToo bad I didn't have this when I did our WAIK deployment. I got so sick of peeling through endless pages of MSDN and TechNet articles. *shudders*
- Thai Peppera2e Jul 31, 2013 at 02:19pmVery helpful, this stuff can be confusing when you're first getting into WAIK deployment.
- Pimientojuliedaniel Jan 8, 2015 at 10:06pmThis is great and very helpful, however I don't appear to have this component in my x86 list of components for my Win7 64-bit version:x86_Microsoft-Windows-Security-SPP_6.1.7601.17514_neutralAny advice? Can I skip it and still achieve an unattended install?
- Pimientoarvetadamberg Sep 18, 2018 at 09:18amvery good tutorial for self learning, but as an additional question, when i also need it to automatically join a domain and the pc to have specific name what would i need to do?