Urie is right, rename the file to autounattend.xml, then it will work. What happens is windows looks for Autounattend.xml on the root of drives, then copy/rename that file into C:\Windows\Panther\unattend.xml. Another thing is missing you password parameter, if you get prompt during install, try run this to enter a blank password (untested so report back) Code: <Password> <Value></Value> <PlainText>True</PlainText> </Password> I hope you are testing in VM, no reason to be burning DVD until you have things working.
WAIK documentation is very well written. Read it twice if needed and test the xml file over and over again. EULA, network settings and more can be hidden at oobe minisetup stage after sysprepping, but I don't have WAIK or OPK installed on this PC so can't help you with details. Check waik and WSIM (Windows System Image Manager) inside waik. Everything is there. Check all the branches/strings/settings in wsim, they all have a help section that explains what they do. If tomorrow I'll have some free time, I'll build a generic working Autounattend.xml and post it here. Greets
What makes you say that? The WAIKs ImageManager is exactly the tool with which these answer files are being generated, and since it has a GUI, (which even prevents you from adding something to the wrong pass), adding the different sections is a mere matter of choose-and-click. (Plus it is safe because the ImageManager auto-checks the syntax of the file for errors before you can save it. That way a non-working answer file due to syntactical mistakes is out of the question, which means you save yourself a lot of trial and error too...)
WSIM checks the syntax, but that doesn't always guarantees you a foul proof xml and unattend installation. It's all about trial and error, and I burnt myself numerous times with non-working deployment scenarious, where the xml created with wsim was the culprit. One thing to mention is the inconsistencies and out-of date settings that no longer work with windows 7. And more. As I said, trial and error.