The fix in KB226417 provides no features with regard to the MSU functionality; nor did this update introduce the MSU packaging capability. The MSU and WUSA.EXE capabilities were created with the release of Microsoft Windows Vista in 2006. MSU files were created expressly for use with the standalone WUSA.EXE utility for those adminstrators/organizations who wanted to manage update deployments through a standalone utility. MSU files require the WUSA.EXE standalone installer, and neither WSUS, MU, nor the Windows Update Agent support the distribution of .msu files via those methodologies.
We dont directly support MSUs in the package editor, however it can be done.
In the package editor, you have to create a custom package (exe type).
The program that you want to run is pkgmgr.exe
You will need to take the extraction from the MSU (see MS link below for how to do this) and add them as additional files in the EW package editor for the custom package.
You must also packageboot enable the package and setup the package to execute the native windows pkgmgr.exe program that is in the windows system directory on Windows Vista/2008 and later.
Here is an article that talks about the MS specific part...
Glad to hear it. We just recently migrated these posts from the eminentware site to have all this information in one place. That's why you see it posted with the SW Community Team account.
How about using wusa.exe ? It handles the mess of extracting and using the .MSU contents. It can be found in the System dir on Windows machines. Here is a blurb from that MS article:
When you use Wusa.exe to install an update package, Wusa.exe expands the contents of the .msu file to a temporary folder. Then, Wusa.exe performs the following steps:
- Wusa.exe uses the Windows Update metadata in the .msu file to search for applicable updates.
- Wusa.exe copies the contents of the applicable updates to the Windows Update sandbox. The Windows Update sandbox is a protected folder.
- Wusa.exe calls the appropriate function in the Windows Update Agent API according to the mode in which you start Wusa.exe.
- When the Windows Update wizard completes the installation, the Windows Update Agent API returns a status. Then, Wusa.exe works synchronously with Windows Update Agent API.
Note Each update in an .msu update package is installed in a separate session. Only one instance of Wusa.exe runs when you use Wusa.exe. Wusa.exe does not modify the contents of the updates in .msu files. The Windows Update infrastructure performs the required actions according to the contents of the update.
When you start Wusa.exe in interactive mode, a welcome screen displays high-level information about the update. If you continue to install the update, Wusa.exe calls the appropriate function in the Windows Update Agent API to start the Windows Update wizard. The Windows Update wizard displays the Microsoft Software License Terms that are associated with the update package. Wusa.exe calls the Windows Update Agent API to continue the installation. Then, Wusa.exe waits until the Windows Update wizard finishes the installation.
To install an .msu update package, run Wusa.exe together with the full path of the file. For example, if the Windows6.0-KB934307-x86.msu file is in the D:\934307 folder, type the following command at a command prompt to install the update package:
You can also double-click the .msu file to install the update package.
Very nice. Thanks for sharing.
Would you be able to go into further detail about how you got this to work? I have a hotfix I am trying to push out but I'm not having any luck. As for the wusa.exe command, where exactly in the new package do you put it? Thanks!