Windows Image and Configuration Designer, or WICD, is a new, exciting tool that will further enhance the customisation of the Windows platform alongside tools such as ConfigMgr and MDT. Do not think of WICD as a deployment tool.
Microsoft sum up the tool as such:
'Windows ICD is primarily designed for use by:
To be able to install WICD I'll need to grab a copy of the Windows 10 Technical Preview ADK download. Note that this version is not compatible with ConfigMgr 2012 or MDT 2013.
Run the adksetup.exe file. I'm going to install the Windows Assessment and Deployment Kit.
On this occasion I am not going to join the CEIP
Accept the licence agreement
By selecting the ICD I am forced to install other components of the ADK.
Once installed close the ADK setup.
WICD is available from the start menu.
Time to make some cool stuff. I'm going to make a change to Windows 10 by starting a new project.
I've named my project.
At this stage am I going to provision a package, a ppkg, which will contain my changes and which I can deploy to a target device.
I can target my change at all Windows versions or be granular and target specific releases. Note that targeting the specific release will open up all available customisation options for that version.
At this point I am going to click Finish.
At this point I feel as I have hit the realm of Windows System Image Manager. Lots of options but I'm not sure where I need to click! So I'm going to choose something visual and easy.
I'm going to remove the XPS Printer from Devices and Printers.
Once the customisation is complete I click the Build button.
At this stage I can introduce package versions and rankings.
I can also encrypt and sign the package.
Now I choose a location to save the package.
...and build the package.
The build process creates a bunch of files along with the .ppkg file.
The customizations.xml file stores the details I have entered in the WICD interface - similar to an unattend.xml file.
At this stage I want to make the provisioned change to my Windows 10 device. I need to double click my WICDChange.ppkg file.
I must allow the change to take place on the system.
Unfortunately it seems Windows ICD within the Technical Preview isn't playing ball at the moment. I've checked the ICD.log file and I have numerous errors when I attempt to build the provisioning package (notice I've added a few more changes into to see if any are going through - but no).
So for now those are the steps required to create a provisioning package but I can't do much with the tool. I'll keep an eye out for ADK updates and revisit this when I know I can create a ppkg file that has some positive effect.
Cheers Rob. Shame it's not working at the moment. This tool will have some cool features for OEM and customised builds. I hope the interface is made more user friendly - one of my gripes with Windows System Image Manager.
Ooo such detail, nice!