Like the MDT 2013 Lite Touch post from yesterday, here is the same info but for ConfigMgr 2012 R2. In this post you find step-by-step guidance on how to deploy the Windows 10 preview, including driver injection support, with ConfigMgr 2012 R2 (integrated with MDT 2013 of course).
I also encourage you to read Niall Brady's guide on the topic: How can I deploy Windows 10 Enterprise using System Center 2012 R2 Configuration Manager.
If you don't do the setup explained in this post, ConfigMgr 2012 R2 will fail with the following errors when trying to inject drivers during deployment of Windows 10 preview.
Dism failed with return code 50
Failed to add driver to driver store. Code 0x80070032
Failed to provision driver. Code 0x80070032
First, this is not supported so don't blame me if something is not working.
Second, to make ConfigMgr 2012 R2 (integrated with MDT 2013) work with Windows 10 preview image, including driver injection, you need to make sure WinPE 5.0 is updated with the new dism.exe and sub-components required to do offline servicing (otherwise driver injection fails). The trick is to simply have the the task sequence copy the right servicing stack to the WinPE 5.0 boot image, when deploying Windows 10 operating systems.
On your file share you use for your MDT 2013 package source files, copy the dism.exe and DISM folder from a x64 WTP boot.wim file to MDT 2013 package, in my case CM01SourcesMDTMDT 2013Toolsx64. The dism.exe file and DISM folder are found in the X:WindowsSystem32 on your boot image (once booted), or E:MountWindowsSystem32 if you just mounted the boot.wim.
After copying the files, add two run command line actions to your Windows Technical Preview task sequence (and only this task sequence).
Copy WTP dism.exe
cmd /c copy %deployroot%tools%architecture%dism.exe x:windowssystem32 /y
Copy WTP DISM subsystem
cmd /c copy %deployroot%tools%architecture%dism* x:windowssystem32dism /y
Driver injection is now successful for Windows Technical Preview deployments