Following on from my last post I will now write up putting the convenience roll up into a ConfigMgr Application.  Please read my last post for details of prerequisites to installing this update.
Here they are once more

  • KB976932 – Service pack 1 for Windows 7 and Server 2008 R2 (KB976932)
  • KB3020369 – April 2015 Serving stack update (KB3020369)
  • KB3125574 – Convenience Roll Up (KB3125574)

ConfigMgr Application work
Create a new application and chose to manually specify the application information.
Give it a name and select the tick box highlighted if you want to deploy the app within a task sequence.
I like to give my applications an icon every time so I search the word “update” in an image search and steal one from the internet.
We then select to add a deployment type.
Again chose to manually specify the application settings and click next.  Then give it a name.
Now, within your source structure, you need to place the three files required.  (I’m assuming you already have Windows 7 SP1 installed as you really should by now. This too is a prerequisite!)
1. Update for KB3020369 (Service Stack Update)
2. Update for KB3125574 (Convenience Update Itself)
3. Installer.bat
The installer.bat file has two lines in it, one to install the service stack update and a second to install the convenience update.  Like so:

   1: wusa.exe KB3020369.msu /quiet /norestart

   2: wusa.exe KB3125574.msu /quiet /norestart

!{WARNING} I renamed my downloads to the KB numbers, do not blindly use the above code, check the actual names of your update files.
So, we now specify the content folder within your source structure.
1. Content location – Source folder which contains the three files
2. Installation Program – Installer.bat
3. Uninstall Program – %windir%System32wusa.exe /uninstall “KB3125574.msu”
Now we’re going to add a custom script as the detection clause like so..
We’re going to specify a PowerShell script, and the code will be:

   1: Get-Hotfix | Where-Object {$_.HotFixID -match "KB3125574"}

I always change my installation behaviour like so:
I don’t have any Requirements or Dependencies  so I next, next, finish through he rest of the options.
Close the deployment type and next, next finish through he rest of the wizard to create the application.
You now need to Distribute the content to your distribution points and the Deploy the application to a collection.  In my case I tested by deploying to my Pilot machine, you can see here the install was successful.
!{WARNING} I suggest you make this application Available and not Required in production.  The updates takes FOREVER to install and a slip up, such as an end user rebooting in the middle will more than likely cause you problems.  At least if its available, end users can install at their own convenience as long as they are warned it will take a while
I hope this is of use for you.