Microsoft Windows installation can be automated by the use of answer files. In previous editions, there was a Unattend.txt. These days the answer files are all xml based so you will need to author an Unattend.xml file.
MDT takes the headache out of this because it generates an answer file each time you create a new task sequence. You can customise this answer file using Windows System Image Manager
Windows System Image Manager (Windows SIM) creates and edits the Setup answer files. Each answer file is configured to a specific WIM image. Windows SIM will generate an index of the image into a catalog file with a .clg file extension. This shows what components exist in the associated wim file so you can configure the image specific settings. (Note: An x64 machine cannot generate an x86 catalog file.)
To make sense of Windows answer files, you will need an understanding of deployment Configuration Passes. Configuration Passes describe each of the phases that Windows takes when performing an installation. Not all passes are performed during a setup some Configuration Passes will only run after a Sysprep operation. You could also create an unattend.xml to configure the WindowsPE environment.
To edit an answer file
Right-Click the Task Sequence and select properties.
Select the OS Info tab and click the Edit Unattend.xml button.
From there you are in Windows SIM and can edit the Unattend.xml file. Many settings in the file are overwritten by MDT during a deployment by using the propertys in the customsettings.ini. I would check to see if there is a setting first before making a change. I have blogged extensively on this topic here. Another great reference is the Unattended Windows Setup Reference on Technet.