The unattend.exe utility adds device-driver specific information to the Microsoft Windows unattended installation answer file for a deployment scenario. Show
The ServerGuide Scripting Toolkit uses the unattend.exe utility to dynamically add server-specific device-driver information to the answer file for an unattended installation. The device drivers on the IBM ServerGuide Setup and Installation CD are already configured for use with this utility. Two versions of the utility come with the ServerGuide Scripting Toolkit:
The unattend.exe utility processes three types of device drivers:
The unattend command adds the device-driver information to the answer file in one or more locations, depending on the type of device driver: Text modeText mode device-driver information is added to the [MassStorageDevices] and [OemBootFiles] sections. Entries are not duplicated, and existing entries are not changed.Hardware abstraction layer (HAL)HAL device-driver information is assigned to the ComputerType keyword in the [Unattended] section. Any value previously assigned to this keyword is overwritten. Plug and PlayThe OemPnPDriversPath keyword in the [Unattended] section is set to the path to the PnP device driver directory. Any value previously assigned to this keyword is overwritten.ExecutableThe executable device-driver information is added to the [GUIRunOnce] section. Existing entries are not changed.Path to the $oem$ directoryThe OemFilesPath keyword in the [Unattended] section is set to the path to the $oem$ directory. Any value previously assigned to this keyword is overwritten.For text mode device drivers, the unattend.exe utility uses the information in the hwdetect.ini file and the txtsetup.oem file (located in the \$oem$\textmode directory of the target server) to add the text mode device driver information to the answer file. This utility also adds the Microsoft retail text mode device drivers using information specified in the txtsetup.sif file from the i386 directory of the Windows operating-system installation source files. For plug-and-play and executable device drivers, the unattend.exe utility uses information from the hwdetect.ini file (the output of the hwdetect.exe utility) and the drvinfo.ini file in each device-driver directory in the target server to determine the device drivers to add to the answer file. Device drivers that are not supported on the target server are deleted from the device drivers directory. UsageThe unattend.exe utility has the following command-line syntax:
Return codesThe unattend.exe utility returns the following values to indicate status:
ExamplesThe following examples illustrate how to use the unattend.exe utility.
How do I create an answer file for unattended installation?Create and modify an answer file. Step 1: Create a catalog file. Start Windows System Image Manager. ... . Step 2: Create an answer file. Click File > New Answer File. ... . Step 3: Add new answer file settings. Add OEM info: ... . Step 4: Save the answer file. ... . Step 5: Create a script.. What tool would you use to create or edit answer files used for unattended installations?C. Windows System Image Manager (SIM) is used to create unattended answer files in Windows Server 2016. It uses a GUI-based interface to set up and configure the most common options that are used within an answer file.
What tool would you use to create or edit answer files used for unattended installations of Windows 10?Anyone can write an answer file manually. Microsoft offers the Windows System Image Manager (SIM) console available through the Windows Assessment and Deployment Kit (ADK) to make it easier to create the file to install Windows 10 unattended.
What kind of file is used to configure an unattended installation?An unattended installation is the traditional method of deploying a Windows operating system. Unattended installations use an answer file named Unattend. xml, which contains user input to various GUI dialog boxes that appear during the installation process.
|