Not going too deep here, just something I found the other day.
In your MDT 2013 Deploymentshare, if you go to the share’s properties, you will find the WinPE Tab and the WinPE’s features:
In here you can add components to your boot images. These components are either in C:\Program Files\Microsoft Deployment Toolkit\Templates\Distribution\Tools (like DaRT: http://www.deploymentresearch.com/Research/tabid/62/EntryId/131/Adding-DaRT-8-1-from-MDOP-2013-R2-to-ConfigMgr-2012-R2.aspx ) or in your ADK install directory here: C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs
If you take a look at the latter, you might see that there are components in there that don’t show up in that list in your MDT Deploymentshare, for example WinPE-FMAPI.cab (File Management API).
Why is that?
That list is being built off of an XML file (like MDT uses a lot of XML files), which is C:\Program Files\Microsoft Deployment Toolkit\Bin\FeatureNames.XML
That file lists all the components MDT knows how to handle (don’t know how to else say it) and also defines whether or not that component will be included or excluded in that list. Obviously, WinPE-FMAPI is excluded (don’t know why!).
If you want to have it in your GUI as a component you can add and maybe at the same time take away the possibility to add some language packs, just change the XML to this:
Restart your MDT Deployment Workbench, go back to the Deploymentshare’s properties and be happy ;-)
Have fun deploying your WinPEs!