WIM Witch v2.2.0 – Start Menu, Default App Association, and Reg File Support

tl;dr – New features introduced in a new tab. Let me know if you find any bugs.

This release of WIM Witch brings a new tab to the interface, and three new options to make offline servicing even more convenient. She can now import the default application association XML, stage a Start Menu layout XML file, and import registry settings from exported REG files..

The new settings can be found under the “Other Custom” tab.

Default Application Association

To leverage this feature, one must already have a XML file exported from a Windows reference machine in order to import the configuration into the offline image.

For information on how to export the file from a reference machine, see this link

Click the check box to enable the Default App Association feature. Then click select and browse to the XML file and click OK. The path and file name will be displayed.

Start Menu Layout

To leverage this feature one must have already exported a Start Menu layout xml file from a Windows reference machine.

For information on configuring and exporting the Start Menu layout template, see this link

Click the check box to enable the Start Menu layout feature, then click the select button. From there, simply select the XML file. If the name of the file is not “Layout Modification.XML”, WIM Witch can apply the layout, but will rename the file during the build process. This behavior will be noted in the log and console output.

Registry Keys

WIM Witch can now import registry keys from exported REG files. As with the other new features, the required files will need to have already been exported from a reference machine. Click the check box to enable the feature, then click select. The UI allows for multiple files to be added from a single folder.

The current support for the exported registry settings are for:

• HKLM\Software
• HKLM\System
• HKCU
• HKU\Default

Make It So

Once the required files have been selected, the options are ready to Make It So.

Below is a screen grab of the output regarding the new features during the build process.

Existing Saved Configurations and CM Package Info

For users with existing configurations saved or those updating images in ConfigMgr, some intervention will be required to update these saves with the new capabilities.

For config files, load one from the Save/Load tab, then select the new options under the Other Custom tab, and then save the configuration.

For updating ConfigMgr images, select the image package from the ConfigMgr tab. Once the values have been loaded, select the new features from the Other Custom tab, then click Make It So. The changes will be saved automatically.

Of course, if the new features are not needed, there is nothing to do.