Multiple IMF Updates showing up?

On August 24, 2007, in Exchange, by  

Multiple IMF Updates showing up?

On my SBS 2003 R2 server I recently started getting the yellow ballon popup on my server telling me I have updates to approve. But when I look, it’s for two outdated IMF updates, one from late 2006 and the other from early 2007. I checked with some other SBS’ers and found that several of them have also encountered this issue, but since they didn’t know how to fix it, they were simply ignoring these unwanted IMF update requests.

So how does one get rid of them?

In my case, I have WSUS 3.0 installed on my server, and rely on the SBS management console to interact with WSUS. In order to clear up this issue and remove the old IMF entries, I had to go into the standard WSUS3 console (Administrative Tools > Microsoft WSUS 3.0) and then drill down Computers > All Computers > Update Services Server computers, and then clicked on the Status Report link located on the far right frame.

Page 2 of the Status Report report will show the updates that are waiting to be installed. In my case, I had seven (7) different IMF updates that, for some reason, were still there. Once I changed the approval status from ‘install’ to ‘not approved’, the irritating little Yellow balloon telling me I have updates
waiting to be approved disappeared!

Now, what caused this to happen in the first place? It’s only a guess on my part, but it seems to me I did not see this issue until sometime after doing the WSUS “mowing the grass” process for reducing the size of the WSUS database. It’s just a guess, but perhaps someone can confirm or refute this.

In either case, I hope this helps someone!


I copied this from Kevin’s blog post to help a certain someone (you know who you are) in Chicago getting the same March and November updates over and over again


One Response to Multiple IMF Updates showing up?

  1. Joseph says:

    Yes Susan, I do know who I am :).

    And I did have 7 “stuck” IMF updates which are all now in Not Approved status. I seem to remember doing a cleanup of the WSUS v3 database at about the same time this started happening, so maybe they are related.

    Thanks for the help.