Today I had to deploy a Microsoft hotfix that would fix an issue we were experiencing. The hotfix was a msu file and although I had deployed many msu’s in the past, I realised that I hadn’t blogged the process. So here we are!
To deploy the msu I will be using the wusa.exe (Windows update standalone installer) that is built into most versions of Windows operating systems. You can find out more about wusa here: http://support.microsoft.com/kb/934307
The first thing I did was download the hotfix and store the resulting .msu file on my SCCM server where I normally keep all of my application source files.
Next up, I chose to create a new Application:
- Select to ‘Manually specify the application information’
- Complete the ‘General Information’ screen to your tastes…
- I chose to leave the ‘Application Catalog’ screen at the defaults as I will not be making this available to the catalog; rather it will be a required device deployment.
- Click the ‘Add’ button so that we can add a new deployment type.
- Select ‘Script Installer’ and to ‘Manually specifiy the deployment type information’
- For the General Information screen, complete any fields with the appropriate information. I chose to add ‘x64’ in the name as I downloaded the x64 msu so this deployment type will be for x64 computers only. Later, you could add a x86 deployment type if you needed to.
- Browse to where you have stored your msu file and then add the following for the:
wusa.exe "nameOfTheMsu.msu" /quiet /norestart
wusa.exe /uninstall "nameOfTheMsu.msu" /quiet /norestart
* Note that I chose to suppress reboots.
* Note that the screenshot below will look slightly different to yours as you go through the new application wizard as I made a typo in my original screenshot and fixed it after the application was complete – this gives you a slightly different view but essentially it’s the same.
- Click the ‘Add Clause’ button
- This is where we will add our detection rule. In this instance, I looked at the KB article from Microsoft for this particular msu and it showed me the name of the file that would be changed along with the new version number of the changed file. You will find this information on most hotfix KB’s:
- Here’s the current version on one of our affected computers…as you can see, the version number is older than the one listed in the hotfix (Step 9 above):
- Now we know what to look for, the detection rule is easy. Here’s what my resulting rule looked like which is based on the Microsoft KB:
- Click next!
- Change the user experience to ‘Install for system’ and ‘Whether or not a user is logged on’ (As I will be making this a required device deployment.)
- Click the Add button for our system requirement
- I simply chose all Windows 7 x64 computers as that is what this particular msu applies to:
- The completed requirement:
- I did not have any dependencies to add so I clicked next.
- Take a look at the Summary screen:
- We have success!
- At this point, we could add a secondary deployment type if we were going to deploy the x86 version of this MSU by clicking the add button. I am not so I clicked next.
- Another Summary:
- And we’re done.
All that’s left is to upload this to your distribution point and deploy it to your computer collection.