Server 2012 R2 and DISM v10

[Injector]

ok so i'm clearly missing something here, I have ConfigMgr 2012 R2 SP1 running on Server 2012 R2, I installed ADK 10 after "removing" ADK 8.1 U (I quoted because i copied the whole 8 folder and restored it after the official uninstall so i could still use USMT)

 

I took the W10 boot images and added them to ConfigMgr, now I happen to know what the wim PE images off the ADK don't come with any packages so in order for OSD to work ConfigMgr adds OCs upon distribution, for example this screenshot below is adding scripting, SecureStartup, WDS, and WMI

 

However i know that DISM 6.3 which is what comes by default with Server 2012 R2 cannot modify Windows 10 images as it complains about upper level image or something or other. which is why the ADK installs DISM v10, in the screenshot below:

 

On the left is DISM from start -> run -> CMD

On the righ is DISM from ADK

 

 

Now to the bread and butter of this post, even though SCCM has accepted the boot images and told me they were successfully imported when I do get-packages against it there is no packages, nor is there any drivers loaded.How are these images supposed to work when the server can't modify them? After i asked myself that question i went to look in the DISM log and noticed that it is version 10 that is being ran however after i mounted the image the server uses i noticed that none of the packages were loaded.

 

 

 

So what I'm I missing here? the server said the images were imported fine however i'm sure that without scripting and WMI they're not going to work. Do i need to load those OC packages manually into the wim?