Hi
Just running through some threads and seen your query BroWolf. It is a shame that it is now 2012 and your original post was 2009. However, I have experience with both technologies, and I would like to point to out that they may be similar in ways, but definitely one is much easier to use. I am a fan of WDS, mainly due to the fact of how it rolls out images. It is just a simple F12 keypress and pxe boot to the network, then choose if you want to capture and image or roll out an image, after this the answer files take care of the rest, right up to the CTRL ALT DELETE screen. Marvellous deployment tool, names the machines, joins them to the domain, activates windows etc....
With my experiences with MDT however there is far more work having to be done on the ground and alot of wizards to go through ( which can be dubbed in the bootstrap.ini and config.ini). I have yet to find a way to boot to the deployment share other than USB or CD, which is a pain.
The WDS has a driver pool as does MDT. Your original question about having to inject drivers into the boot.wim is easily rectified using WDS. I had similar problems with various models of machine and eventually figured out how to do this, rather quite easily. You do not need to use DISM or any of the WAIK tools to do this. There is a wizard in the WDS console. If you right click on your boot image there is an option to add driver package. All you have to do is get the drivers you need and extract them to folder, and open the wizard and point to the driver folder and voila the boot.wim has the drivers needed injected into it. No more network errors at boot time!!
Hope this helps!! Even though it may be 3 years later )
