How To Make An Unattend. Sysprep File. Sysprep is very useful in preparing an image for cloning imaging by stripping all specialization from the installation like drives, SID, PNP enumeration, name and more. During the next reboot PNP is initiated and the Out Of Box Experience is run this is similar to a preloaded laptop or computer from the factory starting up for the first time. When you are cloningimaging machines in mass it is extremely handy to automate as much as possible. Using the Windows AIK Automated Installation Kit specifically a tool called Windows SIM System Image Manager you can automate the entire process. The unattend. xml file is used along with sysprep to automate the image specialization and OOBE after it is cloned and rebooted. The following process will automate the sysprep so next reboot it will only ask for computer name. Some assumptions during this article are you are creating an EnglishUS install, you are using a KMS server and your timezone is EDT. Step 1. Download and install the latest WAIK from http downloads. WAIK should support Windows 7 and 2. R2 check the date. Step 2. Get your media that you have installed with and mount it in the DVD ROM or via and ISO mounting utility if it is only and ISO. You will need to allow Windows SIM to access the install. Step 3. Start Windows SIM and right click on Select a Windows Image or Catalog and find the install. In this tutorial I used x. Step 4. Now we need an answer file, so right click on Create or open an answer file and select New Answer FileStep 5. Creating An Answer File For Unattended Installation Windows 7' title='Creating An Answer File For Unattended Installation Windows 7' />Hello. I am trying to write silent installation script for my company software. But that software is only in exe file format. I tries these above option but its not. On the left hand side open the Components folder and find Microsoft Windows International Core, right click and select Add Settings to Pass 7 oobe. System. It will be added to the answer file in the center. Step 6. Fill in the settings for Input. Locale thru User. Locale in the properties pane I used en US for English language and United States locale. The en US is defined in the RFC4. ISO 6. 39 1 code for known languages and the ISO 3. Deploying-Windows-7-Using-Windows-Deployment-Services-Snap-6.jpg' alt='Creating An Answer File For Unattended Installation Windows 7' title='Creating An Answer File For Unattended Installation Windows 7' />Microsoft has an article of supported RFC4. LCID reference http msdn. PROT. 1. 02. 9. aspx. Step 7. On the left hand side under the Components folder and find Microsoft Windows Shell Setup6. Add Settings to Pass 7 oobe. System. It will be added to the answer file in the center. Click on the Shell Setup in the answer file section and fill in the Time. Zone under properties. A list of these time zones can be found here http technet. WS. 1. 02. 9. aspx. Step 8. Open the Microsoft Windows Shell Setup folder in the answer file and find OOBE and click on it. In the properties page set Hide. EULAPage to true and Network Location to Work, Public or Home. The Protect. Your. PC property can be set to 1 for recommended protection, 2 for updates only and 3 for automatic protection to be disabled. These all related to the Windows Update protection. WS. 1. 02. 9. aspx. Step 9. We need to setup the first administrator account since Windows 7s administrator account is disabled by default. Further down under Microsoft Windows Shell Setup click on User. Accounts then right click on Local. Creating An Answer File For Unattended Installation Windows 7' title='Creating An Answer File For Unattended Installation Windows 7' />In this article will show you how to use PowerShell and Windows System Preparation Tool to sysprep Windows 10 machine booting in Audit mode. In this post we will see the steps to capture windows 7 using SCCM 2012 R2. This post is different from the one which shows the steps to. Accounts and select Insert New Local. Account. Step 1. In the properties of the local account on the right side fill out Description, Display. Name and Name. The Group must be administrators, so that you can locally administrate the computer i. Step 1. 1. Click on Password under the Local. AccountNameusername and in the properties pane set the password for the account. The password will be saved in the XML file however it will be encrypted the encryption used is unspecified in Microsofts documentation. Step 1. 2. On the left hand side under the Components folder and find Microsoft Windows Shell Setup6. Add Settings to Pass 4 specialize. It will be added to the answer file in the center respectively under 4 Specialize. Click on the Shell Setup in the answer file section and fill in the Product. Key with the default KMS key found here http technet. These product keys will not activate via Microsoft retail, instead they are dummy keys for a Key Management Server to activate. The product key I used was for Windows 7 Enterprise 3. PXH 7. Y6. KF 2. VJC9 XBBR8 HVTHH. Setting this will skip the activation question during setup, but make sure you have a KMS server running. Also make sure you have met the 2. KMS will not activate any of the clients. Step 1. 3. Right click on the answer file and choose Close Answer File when prompted save it as unattend. Step 1. 4. Copy the unattend. C windowssystem. The startprep. I find it is best consistency so the next time you do this you have the command at hand. You could just type the command into a CMD prompt. Step 1. 5. Run the startprep. Create an image of the workstation using your favorite image software and distribute the image to other workstations. When they restart the unattend. System. lt component nameMicrosoft Windows International Core processor. Architectureamd. Key. Token3. 1bf. Scopenon. Sx. S xmlns wcmhttp schemas. WMIConfig2. 00. 2State xmlns xsihttp www. XMLSchema instance. Input. Locale en USlt Input. Locale. lt System. Locale en USlt System. Locale. lt UILanguage en USlt UILanguage. UILanguage. Fallback en USlt UILanguage. Fallback. lt User. Locale en USlt User. Locale. lt component. Microsoft Windows Shell Setup processor. Architectureamd. Key. Token3. 1bf. Scopenon. Sx. S xmlns wcmhttp schemas. WMIConfig2. 00. 2State xmlns xsihttp www. XMLSchema instance. Hide. EULAPage truelt Hide. EULAPage. lt Network. Location Worklt Network. Location. lt Protect. Your. PC 1lt Protect. Your. PC. lt User. Accounts. lt Local. Accounts. lt Local. Account wcm actionadd. Password. lt Value c. ABh. AHMAcw. B3. AG8. Acg. Bk. AFAAYQBz. AHMAdw. Bv. AHIAZAAlt Value. Plain. Text falselt Plain. Text. lt Password. Description First Admin Userlt Description. Display. Name Userlt Display. Name. lt Group administratorslt Group. Name Userlt Name. Local. Account. Local. Accounts. User. Accounts. Time. Zone Eastern Standard Timelt Time. Zone. lt component. Microsoft Windows Shell Setup processor. Architectureamd. Key. Token3. 1bf. Scopenon. Sx. S xmlns wcmhttp schemas. WMIConfig2. 00. 2State xmlns xsihttp www. XMLSchema instance. Product. Key 3. PXH 7. Y6. KF 2. VJC9 XBBR8 HVTHHlt Product. Key. lt component. Image cpi sourcewim h sourcesinstall. Windows 7 ENTERPRISE xmlns cpiurn schemas microsoft com cpi. Tags Image, Sysprep, Windows. This entry was posted. Thursday, January 6th, 2. Windows 7. You can follow any responses to this entry through the RSS 2. Both comments and pings are currently closed. Windows Deployment Services, WAIK Windows 7 Part 34. We are back again and in todays article we will continue our efforts in automating our Windows 7 deployment via Windows Deployment Services utilising the WAIK tool and the creation of our XML Answer files. In Part 2 of this series we focused on the creation of the WDSUnattend. Windows Pre Execution Boot for our WDS clients and took care of the partitioning of our disks. If you missed part 2 of this series, you can access it here. Today we continue our efforts in utilising the Windows System Image Manager WSIM to create our Image. Unattend. xml which will be specifically designed to automate the Out of Box Experience OOBE of our Windows 7 Enterprise install. In our last article I introduced WSIM and the steps required to create an answer file. I also went into some detail regarding the 7 distinct sections that make up an answer file that reflect the 7 possible stages in the deployment of your operating system, in our case Windows 7. As you recall these stages are referred to as Passes and you may not necessarily need to utilise every single pass in an XML Answer File. Our WDSUnattend. Part 2 primarily focused on the windows. PE pass however our Image. Unattend. xml that we are creating in this article will utilise the specialize and oobe. System passes.   So lets beginLaunch WSIM and select File New Answer File. The first area that we will focus on is the specialize pass which we will provide details for the automation of the joining of the machine to the domain. The minimum components and passes required for our Image. Unattend. xml are listed as follows Component. Configuration pass. Microsoft Windows Shell Setupspecialize. Microsoft Windows Unattended. JoinIdentificationspecialize. Microsoft Windows International Coreoobe. System. 4Microsoft Windows Shell Setupoobe. System. 5Microsoft Windows Shell SetupOOBEoobe. System. 6Microsoft Windows Shell SetupUser. Accountsoobe. System. Microsoft Windows Shell SetupUser. AccountsAdministratoroobe. System. 8Microsoft Windows Shell SetupUser. AccountsDomain. Accountsoobe. System. 9Microsoft Windows Shell SetupUser. AccountsLocal. Accountsoobe. System. As a refresher, I will go through the process of adding our first component Microsoft Windows Shell Setup to our Answer File Pane and its required settings. Recall that I went through this process in some detail in part 2 of this series. Right click on the required component and select Add Setting to Pass. This will then appear in the Answer File pane as follows We will make the following changes to the properties of the Microsoft Windows Shell Setup component as per the below screen capture. You will notice that in the Computer. Name section I have specified as I am letting WDS do the naming under the AD DS tab of the properties of the WDS server. In the below screen capture, I have specified a Client Naming Policy under the properties of our WDS server. The following format GK0. GK0. 01, GK0. 02, GK0. I have listed the rest of the settings in text form for the components listed in the table above. These are as follows 4 specialize. Microsoft Windows Shell Setup. Computer. Name egistered. Organization lt Name Registered. Owner lt Name 4 specialize. Microsoft Windows. Unattended. JoinIdentification. Debug. Join false. Join. Domain lt Domain Name Unsecure. Join true. 7oobe. System. Microsoft Windows International Core. Input. Locale en Au or en USSystem. Locale en Au or en USUILanguage en Au or en USUser. Locale en Au or en US7oobe. System. Microsoft Windows Shell Setup. Registered. Organization lt Name Registered. Owner lt Name Show. Windows. Live false. Time. Zone lt AU Eastern Standard Time 7oobe. System. Microsoft Windows Shell SetupOOBEHide. EULAPage true. Hide. Wireless. Setup. In. OOBE true. Network. Location Work. Protect. Your. PC 1. Skip. Machine. OOBE true This setting has now been deprecatedSkip. User. OOBE true This setting has now been deprecated7oobe. System. Microsoft Windows Shell SetupUser. AccountsAdministrator. Password. Value 7oobe. System. Microsoft Windows Shell SetupUser. AccountsDomain. Account. List. Action Add. List. Item. Domain lt Domain Name 7oobe. System. Microsoft Windows Shell SetupUser. AccountsDomain. Account. ListDomain. Account. Action Add. List. Item. Group Administrators. Name Domain Admins. System. Microsoft Windows Shell SetupUser. AccountsDomain. Account. ListLocal. AccountsLocal. Account. Action Add. List. Item. Display. Name lt Name of Local Admin Account e. Help. Desk. Group Administrators. Name Help. Desk. System. Microsoft Windows Shell SetupUser. AccountsDomain. Account. ListLocal. AccountsLocal. AccountPassword. Value In summary, the oobe. System settings above Windows Out of Box Experience automates the initial configuration tasks that end users normally encounter when installing Windows 7 or Windows Vista. The above settings are the required minimum settings to fully automate the Windows 7 Enterprise install image, however you can add other components such as setting a default theme Microsoft Windows Shell SetupThemes. The complete Unattended Windows Setup Reference can be found in the WAIK help area and on the Microsoft Tech. Net Site here. Once you have completed adding any further settings to your Image. Unattend. xml file you will need to validate your settings and then save the file as Image. Unattend. xml. We will now navigate to your WDS server and launch the Windows Deployment Services Management Console. Expand Servers and then your Server Name and  click on Install Images. Our Windows 7 Install Image should be listed as per the below screen capture. Recall that this was added in Part 1 of this series when we first configured our WDS Server. Right Click on our Image and select properties. Under the General Tab, click on select file and browse for the Image. Unattend. xml file that we saved earlier. We have now applied our WDSUnattend. WDS Pre Execution Boot part 2 of this series and our Image. Unattend. xml which automates the OOBE of our Windows 7 install image. Now is a good time to review your WDS Server settings within the Windows Deployment Services Management console by right clicking on the server and selecting properties. Under the AD DS tab you can specify your Client Naming Policy and specify your Computer Account Location. Also ensure that your WDSUnattend. Install Usb Hdd Ps2 Slim. Client tab Unattend file settings area. We are now ready to rock and roll and attempt to deploy our first Windows 7 Image via PXE boot. When your machine is starting up press the relevant Function key combination to access the network PXE boot which should then detect your WDS Server and then press F1. Windows PE Boot Image. Once the boot. wim has completed loading, you will receive the below screen capture, allowing you to select your Windows 7 Install Image. If you have multiple Install Images they will also be listed here. Click Next. Thats it  Your installation will now continue without any user input as this is taken care of by our Image. Unattend. xml file.