Living Table of Contents
- MDT Tutorial: Prologue & Requirements
- MDT Tutorial Part 1: Installation
- MDT Tutorial Part 2: Initial Configuration
- MDT Tutorial Part 3: Imaging
- MDT Tutorial Part 4: CustomSettings.ini
- MDT Tutorial Part 5: Bootstrap.ini
- MDT Tutorial Part 6: Customizing Boot Media
- MDT Tutorial Part 7: Customizing Base MDT Template & ADK WinPE Template WIM
- MDT Tutorial Part 8: Unattend.xml
- MDT Tutorial Part 9: Logging
- MDT Tutorial Part 10: CustomSettings.ini Validation Testing & Troubleshooting Part 1
- MDT Tutorial Part 11: Troubleshooting Part 2: Windows could not parse or process unattend answer file [C:\windows\Panther\unattend.xml] for pass [specialize]. The answer file is invalid.
- MDT Tutorial Part 11: Troubleshooting Part 3: Windows could not parse or process unattend answer file [C:\windows\Panther\unattend.xml] for pass [specialize]. The answer file is invalid.
- MDT Tutorial Part 11: Troubleshooting Part 4: Task Sequence Variable is Being Overwritten
- MDT Tutorial Part 11: Troubleshooting Part 5: Invalid DeploymentType value “” specified. The deployment will not proceed.
- MDT Tutorial Part 11: Troubleshooting Part 6: Unable to mount the WIM, so the update process cannot continue
- MDT Tutorial Part 11: Troubleshooting Part 7: Non-Fatal OSD Errors & Warnings
- View Unattend.xml
- Generate Catalog
- Edit Unattend.xml
The unattend.xml lives in subdirectory named after your Task Sequence ID that sits in the Control directory of your Deployment Share. For example, if your Task Sequence ID is BC151164ENT then you can find the unattend.xml in either:
You can edit it using your favorite text editor, but I recommend using the Windows System Image Manager (SIM).
- Edit your Task Sequence
- Go to the OS Info tab
- Click the Edit Unattend.xml button
- Go make a pizza
Doing the above will require you to generate a catalog file for the WIM you imported. Fortunately this process happens automatically.
Unfortunately this process can take a while depending on your configuration.
Once the generation is complete, you’re free to make changes to your Unattend.xml.
Also, you may want to pre-generate catalogs in a separate SIM session since it takes a while:
Typically my first step is to run the Validation check to see what the SIM isn’t happy about.
Double click on any results to be taken right to that setting to remediate any issues.
- For the first four in the screenshot above, I simply revert the change by secondary mouse-clicking on the setting and selecting that option.
- For the NetworkLocation warning, I typically leave it as-is & ignore warning. Even though it’s officially deprecated, it still seems to work but for how long is anyone’s guess.
Since we’re already in amd64_Microsoft-Windows-Shell-Setup__neutral/OOBE, why don’t we set
Make any other necessary changes, verify the answer file, save and exit.
You can do a lot in the unattend.xml but since I’m prone to forgetting 🙂 I try to add just the bare minimum and put the rest in a Task Sequence; It’s much easier to manage/maintain that way but there are legitimate reasons to put something in the unattend. Do what works for you.
Good Providence to you!