I use MDT to drive the task sequences from SCCM using UDI e.g. select domain OU to join and software to install as well as other stuff like computer description and hostname. I also build and capture my own custom wim file "old school" by building it on a VM. sysprepping it without an answer file. booting to a PE boot disk, identifying the OS partition using DISKPART followed by LIST VOLUME and then using DISM with this command:
dism /capture-image /imagefile:F:\wim.wim /capturedir:D:\ /name:"my custom wim" /compress:maximum
The above method of capturing also works well for Windows 8/8.1 and Vista (if you need to deploy vista!)
This captures the sysprepped image. This yields a wim file called wim.wim which can be deployed though SCCM the same as the default install.wim from windows DVD. its handy to include windows updates and common apps. The old argument of fat vs thin springs to mind. Personally i prefer this hybrid approach. if you want to know more about UDI check this out Learning MDT 2012’s User-Driven Installation (UDI) - Chris's Blog - Just weedin around Microsoft - Site Home - TechNet Blogs also google has a tonne of resources on the subject.
I personally never liked SCCM build and capture. I guess i'm just paranoid!
