It’s been almost a year since the last release but I just uploaded DISM GUI 3.5 to the Codeplex site this morning. It contains a few background bug fixes and a few new features. For this version I have kept it compatible with the Windows 7 WAIK and DISM version.
- Added Edition Servicing tab
- Added the ability to apply and unattend file
- Added application servicing tab
It’s not a major release but adds most of the features available in the Windows 7 DISM program. You will notice that there is no “online” functionality to allow it to operate on the running OS. That is something I had planned to put in but was proving hard than I thought with the current version. I’m hoping to include that in version 4.0
Speaking of version 4.0. I don’t have a timeframe to release it yet but I do have some of the features planned.
- Online mode – Allow DISM to be used against the currently running OS.
- Windows ADK compatibility – The next version will rely on the Windows ADK and DISM version included in it.
- WinPE compatibility – I am planning on making the next version work inside WinPE.
- Powershell backend – This one is still up in the air but I may convert the backend to the new Powershell cmdlets instead of relying on DISM.exe.
- There might be more features added but this is what I am planning now. If you have a suggestion add it to the Codeplex site.
I have finally created a CodePlex project for DISM GUI. The latest version (3.1) can be found on the CodePlex site as well as the source code for what will eventually be version 4.0. So for anyone that wants to see the inner workings (and my sloppy code) of DISM GUI head on over to CodePlex to take a look. If you are interested in helping out with the development contact me through the Codeplex site.
From now on I will be keeping all releases of DISM GUI on the CodePlex site and remove it from my Skydrive account.
**An Updated version of DISM GUI can be found here**
Version 3.1 of DISM GUI is ready for download. No major changes in this just a few background changes and 2 usability updates based on feedback I received.
- Added a confirmation dialog box to the exit button. Now if you accidently click Exit you will be prompted to confirm exiting the program.
- The WIM location and path can now handle quotes in the text box.
- I’m working on cleaning up the code and eventually turning this into a Codeplex project. I really haven’t had a lot of time to work on it lately but hopefully early next year I can start on it. If you are interested in contributing to the Codeplex project when it goes live contact me
I was asked by a commenter (here you go Alan!) on expanding on how I use a Make and Model query to automatically assign applications to a specific hardware models. It’s a very easy and powerful feature of MDT and it makes installing those OEM supplied utilities a lot easier.
I’m going to assume that you already have your SSM packages created in your MDT Applications. If not refer to my post on them here.
The first thing you need to do is configure the MDT Configuration Database. There are many articles on the internet that already cover this (including the MDT Documentation) so I won’t rehash that information. One I found particularly good was this one. After you have configured that database and the rules make sure you update your WinPE boot images. If you don’t they will not be able to take advantage of the make and model queries.
Now that your database is configured and you have configured your rules (all explained in the previous link) you can use MDT to dynamically assign applications based on model. In the Deployment Workbench go to Advanced Configuration > Database > Make and Model.
Right click Make and Model and choose New. On the first screen you need to define your Make and Model as is represented in WMI. It’s important that the Make and Model fields exactly match the Name (Model) and Vendor (Make) attributes store in the WMI database. For those that don’t know how to find this information you can use the WMIC tool to display it. The below command returns the Make and Model information from WMI. Note that Name = Model and Vendor = Make.
wmic csproduct get /value
After you enter in the Make and Model information click on the Applications tab. Click Add and choose the SSM application that you want to assign to this model. You can assign as many as you want. Each application that you add to this make and model will be automatically assigned when you choose a deployment task sequence.
Boot from you WinPE image and choose your deployment task sequence. When you get to the screen to choose your applications the ones you previously added to the Applications tab should already be checked.
This is a great way to deploy OEM specific applications in an automated process but you can also do this with any application in MDT.
**An Updated version of DISM GUI can be found here**
Version 3.0 of DISM GUI is ready for download. I’ve done a lot of background changes to this version and implemented a few more of the DISM features. Some highlights of the changes.
- Added this blog URL to the About screen.
- Implemented all the options for the Package and Feature Management of DISM.
- Cleaned up a lot of the background code. Adding new features in the next release will be easier.
- Removed word wrap from the output window and made the entire output window larger.
- Implemented the remove driver functionality.
- Added the ability to set the recurse function for drivers instead of forcing it every time.
These are just a few highlights. In the next version I plan on adding the unattended servicing options as well as the WinPE options. If you have a suggestion or feedback leave a comment below or contact me through the About tab up top.
**Update** There is a new version of the DISM GUI that can be found in this post
Version 2.0 of my DISM GUI is ready for download. I’ve made many changes to the interface and internal workings of this version. Some highlights of the changes.
- You can now open the DISM.log file from the tools menu
- The DISM Command line that was run is also shown in the output window
- DISM now runs in the background thread and a progress bar is displayed while it runs. This prevents the application from displaying a blank command prompt while it runs.
- Added the ability to inject drivers into a mounted WinPE WIM files. DISM GUI will read all INF files in the folder and inject them into the WIM. I did not give the option to choose a single INF file. Also the /recurse switch is always used.
- Added the ability to run Cleanup WIM and Get Mounted WIM information from the GUI.
- You can now display the WIM information in the output window before mounting a WIM.
These are just a few of the improvements. Most of my work involves working with WinPE images so I focused on the features of DISM that support that. If you have a suggestion or feedback leave a comment below or contact me through the About tab up top.
**Update** There is a new version of the DISM GUI that can be found in this post.
Have you ever worked with DISM for some basic WIM management and thought this would be much easier with a GUI interface? I had heard a while back that Microsoft would eventually come out with a GUI DISM utility but I got tired of waiting.
The command line is fine for writing scripts and managing lots of WIM files but I often found myself using DISM in sparingly. Usually there is weeks or even months in between uses so I would often forget the syntax.
So this is a quick and dirty GUI I put together for automating some of the command lines for DISM. Right now it only allows you to mount and discount WIM files but I plan on expanding it’s functionality in the future.
- Windows 7
- Windows AIK 2.0
This may work on Vista SP2 but I don’t have a Vista machine with the WAIK installed on to test it with. If you try it on Vista and it works leave me a comment and let me know.