The new Windows Imaging and Configuration Designer (WICD) is part of the Windows 10 ADK. It will be updated/enhanced with next releases of ADK.
WICD is described on MSDN as a tool that can do the following tasks:
View all of the configurable settings and policies for a Windows 10 image or provisioning package
Create Windows provisioning answer files
Add third-party drivers, apps, or other assets to an answer file
Create variants and specify the settings that apply to each variant
Build and flash a Windows image
Build a provisioning package
The source of this information is https://msdn.microsoft.com/en-us/library/windows/hardware/dn916113(v=vs.85).aspx.
Not only does it have the possibility to create configuration packages, but it is also able to switch the SKU of your Windows 10 installation. This was previously not possible. You still cannot move to Long-Term Servicing Branch (LTSB) via this mechanism, as this is a completely different build. At this stage of the process, you cannot downgrade. Currently, only an upgrade from Pro to Enterprise is possible (except for the Education SKU, which allows an upgrade from Home to Education).
The WICD can be used to create packages that implement any mobile device management (MDM)-based setting. Alternatively, you can run external scripts to set most MDM settings.
For some actions, such as pre-provisioning Windows 10 Mobile or switching to Windows 10 Mobile Enterprise, WICD is the only available tool to the enterprise.
WICD has a wide range of functionality in addition to script support. All in all, it sounds like a very mighty and powerful tool. However, it is currently not directly supported inside the MDT 2013 Update 2 GUI; this is subject to change in future releases. You can integrate a command line as a workaround, but this has a major drawback.
Currently, there is no way to fully automate or silently install the provisioning package. You can sign the
ppkg to remove some prompts, but not in all circumstances. You also need to embed it in an image so that it gets installed during the OOBE process to get no prompts. However, this takes away a lot of flexibility.
It has been our field experience that certain functions WICD can perform or try will break the MDT deployment process. Therefore, it should be tested and care should be taken while including this tool in your work (at the time of writing).
Some issues found at the time of writing (1511 release) include the following:
Changing the SKU inducts a non-interruptible reboot that will break the MDT task sequence engine.
Currently, you can only set what is shown through the UI. It is not possible to enter extra OMA-URI-based CSP policies.
Removal of preinstalled applications does not work properly at this time.
Most policies configured are MDM-related, so some options are only available in this toolset for customization.
With all these required workarounds, caveats, and limitations, we decided to move WICD here for supplementary information purposes. This tool is likely to be improved in future releases of the ADK. Also, future releases of MDT will likely support WICD directly in the deployment workbench, so keep an eye out for release notes changes and expansion of the tool's capabilities.