I just installed MDT 2013 u1 and the Windows 10 ADK. However any boot images that are created with the Windows 10 ADK are not able to be customized in the console. The 8.1 images are, which is odd because the opposite behavior is supposed to happen. When the images are created it is using the DISM binaries and DLLs from the 10 ADK I've verified this in DISM.log and the SMSProv.log. 

This should not happen as you already mentioned. Have you already rebooted the site server after installing ADK 10?

yeah I've even gone so far as uninstalling the 10 ADK, reinstalling the 8.1 update ADK, uninstalling that again and reinstalling the 10 ADK. 

I've done the following:

Uninstall 8.1 ADK - reboot

Install 10 ADK - reboot

Install CU1 for SP1 for R2 - reboot

Un/reinstall MDT update 1

Install HF for CU1 - reboot

I only have 1 primary and a few secondaries. 

When you say "customized in the console" are you referring to adding additional "Optional Components"?
If so what components are you trying to add?

I can add HTML (WinPE-HTA), but I can't add Windows Powershell (WinPE-PowerShell).
When I add WinPE-PowerShell, I get "Failed to inject OSD binaries into mounted WIM file (often happens if unsigned drivers are inserted into x64 boot image)"

Is that what you are experiencing?

No, I don't get any of the tabs. I don't get drivers, optional components, I don't get anything. It is the behavior that is supposed to happen with the 8.1 images when the 10 ADK is installed. However I still have all those tabs on my 8.1 boot images not my Windows 10 boot images. I only have data source, data access, distribution settings, etc. There aren't tabs for optional components, drivers, anything that would allow you to manage and edit the boot image from the console. 

See http://blogs.technet.com/b/jchalfant/archive/2015/08/03/boot-image-missing-tabs-in-the-properties-dialog-after-installing-new-adk-and-updating-boot-image.aspx

I found the problem after digging through the logs. One of my SMS providers didn't want to play nice with the 10 ADK, and for some reason even though I was using the console on the primary (which has a provider on it) it kept on wanting to use the SMS provider on another machine so I didn't catch the problem in those logs. It wasn't until I decided to uninstall the provider on the other machine and reinstall the 10 ADK that it started working. The crazy thing is that I had updated the provider on that machine to R2 SP1 CU1 so it should've been using the ADK on it. Instead it was using the DISM/wimimgapi from the windows directory. 

• Edited by HSChronic 17 hours 52 minutes ago