The unattend.txt
file automates the installation of the OS so that no user input is necessary. The unattend.txt
file must match the release of Windows specified in the i386 directory. These files may vary slightly depending on the version of Windows being installed.
Caution: The Unattend.txt file should not be larger than 800 KB.
The following are some tips about creating the unattend.txt
file to be stored with the image:
AutoLogon=YES
and AutoLogonCount=1
in the [GuiUnattended]
section of this file. You must use the [GuiUnattended]
section, rather than $OEM$\cmdlines.txt
, because the HPCA agent setup uses the Windows installer to install the agent on the target device, and $OEM$\cmdlines.txt
cannot run the Windows Installer.
The AutoLogon
and AutoLogonCount
statements ensure that the agent is installed during the first user logon after the operating system is installed.
extendoempartition=1
in the [Unattended]
section of this file. This causes Windows to extend the file system and partition to include any unused space that follows the partition. If the target partition is too small, it is possible that the copy phase of the installation will work (the phase run on the reference machine). Then, when the image is deployed, the text mode phase will fail or install the OS on some other partition.If you use a large target partition, the process that zeroes unused space on the file runs for a long time.
unattend.txt
files for any necessary customizations. You can use the Publisher to publish these files to the SYSPREP class in the HPCA DB, and then you can connect them to the appropriate OS image. When the image is deployed, the customized unattend.txt
will be merged with the original file.Note: See Publishing for details about publishing files. When publishing unattend.txt
files, follow the instructions as if you were publishing a Sysprep.inf
file.