Hacking Away – Deploying Windows 10 Build 9926 using SCCM 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 Enterprise x64 build 9926, including driver injection support, with ConfigMgr 2012 R2 (integrated with MDT 2013 of course).

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 build 9226 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 the Windows 10 build 9926 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:\windows\system32 /y

Copy WTP DISM subsystem
cmd /c copy %deployroot%\tools\%architecture%\dism*  x:\windows\system32dism /y

 image
The additional actions in the task sequence.

Driver injection is now successful for Windows Technical Preview deployments

Here is the resulting deployment, with the ConfigMgr 2012 R2 CU3 client installed.

image

Happy deployment,

/ Johan

About the author

Johan Arwidmark

0 0 votes
Article Rating
Subscribe
Notify of
guest
4 Comments
Newest
Oldest Most Voted
Inline Feedbacks
View all comments
Admin
Admin
6 years ago

oholtberget:

Sorry, haven't seen that behavior.

/ Johan

Admin
Admin
6 years ago

Hey Dietmar,

Did you create a new reference image, or did you add the default one into ConfigMgr?

/ Johan

oholtberget
oholtberget
6 years ago

Great posts about Win10TechPreviews, keep it up! We follow you with great interest 🙂 I do have a problem I hope others might have seen too though.Building a reference image with 9926 works fine, but deploying the WIM through a normal task sequence present me with a very timeconsuming issue: The "Getting ready" step takes 6 hours!Looking at the c:windowspantherUnattendGCsetupact.log is shows this: 2015-01-31 03:18:17, Info [msoobe.exe] AppReadinessService QueueSystemTasks result [hr=0x00000000]2015-01-31 03:18:17, Info [msoobe.exe] TASK: End successfully running task QueueArsSystemTasksTask2015-02-02 08:58:41, Info [msoobe.exe] Skip button was clicked2015-02-02 08:58:41, Info [msoobe.exe] Posted cache change notification for setting PRODUCTKEYSTATUS. Notice the time,… Read more »

Dietmar
Dietmar
6 years ago

Same problem here as with MDT 2013. After the first reboot to Windows 10 before the installation of ConfigMgr-Client the task sequence do not continue. Administrator account is disabled. The last build I deployed successfully with MDT and ConfigMgr. What a Pity.


>