• Home  / 
  • Research
  •  /  Beyond unsupported – Deploying Windows 10 preview (including drivers) with ConfigMgr 2012 R2

Beyond unsupported – Deploying Windows 10 preview (including drivers) with ConfigMgr 2012 R2

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   

image
The smsts.log file, showing driver injection failure

 

Step-by-step guide

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.

 image
The needed files, copied to the MDT 2013 package.

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

 image
The additional actions in the task sequence.

Driver injection is now successful for Windows Technical Preview deployments

About the author

Johan Arwidmark

9
Leave a Reply

avatar
9 Comment threads
0 Thread replies
0 Followers
 
Most reacted comment
Hottest comment thread
4 Comment authors
samohtrelhejfetterAdminQuell75 Recent comment authors
  Subscribe  
newest oldest most voted
Notify of
samohtrelhe
Guest
samohtrelhe

Hi jfetterAfter fighting with SCCM over so many issues, image building being one, Windows updates another, I've followed Johans advise on this matter as has so many! By building reference images with MDT it is possible to do a complete Windows Update of the reference image during build, from our default WSUS, and from a specific folder on that WSUS. sccmdeploy.dk/?p=428 . Also MDT is ROCK solid installing updates opposite SCCM. 1. In SCCM, every time a dual booting update comes in, OR you get too many updates stacked up (+100) the TS will brake. That is a fact. 2.… Read more »

samohtrelhe
Guest
samohtrelhe

Hi jfetterAfter fighting with SCCM over so many issues, image building being one, Windows updates another, I've followed Johans advise on this matter as has so many! By building reference images with MDT it is possible to do a complete Windows Update of the reference image during build, from our default WSUS, and from a specific folder on that WSUS. sccmdeploy.dk/?p=428 . Also MDT is ROCK solid installing updates opposite SCCM. 1. In SCCM, every time a dual booting update comes in, OR you get too many updates stacked up (+100) the TS will brake. That is a fact. 2.… Read more »

jfetter
Guest
jfetter

Hello Johan, I have read it and I absolutely agree with almost all of it, in fact I appreciate all the tips and tricks you publish. But in the case of enterprise engineers who are very familiar with SCCM, I don't think MDT 2013 is necessarily faster or easier. By the time most engineers get proficient in SCCM, they understand running as System, user interaction with SCCM Packages (Programs), chained dependencies and all the little tips and trick that come along with that. So when venturing into OSD, this means they can now rely on all of their existing software… Read more »

jfetter
Guest
jfetter

With all due respect, I do not think that's really a rule. The fact you CAN capture a Windows 10 image using the MDT 2013 doesn't mean you are supposed to. I fully expect MS to update SCCM 2012 R2 to be able to do what it does now, deploy and yes, capture (when necessary) OS images, even for Windows 10. The MDT is simply a variant of what's integrated into SCCM, it uses the same technology…

jfetter
Guest
jfetter

Sadly the OSD capture tool fails with Windows 10 Preview, so while you can build and deploy based on the vendor WIM, you can't yet customize and capture your own custom images…

Quell75
Guest
Quell75

Johan

Would you happen to know if this method would work with ConfigMgr 2012 SP1 CU5?

Thanks


>