fixes that have been superseded by newer files. The new hotfixes are not being
taken into consideration in the AP processing because these hotfixes can only be
obtained by request. This means that the AP update detection rules are still based
on the older fixes and will cause AP to incorrectly flag fixes that have been replaced
by a newer fixpack
I was told that these type of hotfixes could not be included and I assume it is because
APUP does not have the needed access. I experimented with the related .APM files to
see if I could get AP to flag the superseded fixes as being installed. I was able to do
this by adding a second KBxxxxxx.CAT file + md5sum under [FileDetection] to each KBxxxxxx.APM
in question. This seems to work and AP now flags the superseded KBxxxxxx files as installed.
This works on both an integrated RVM system where the hotfixes exist and a non-integrated
system where only the superseded fixes exist.
Is it possible to add the additional CAT files and their ms5sums as a second criteria to
the superseded KBxxxxxx.APM files or will this be bending things to far?
In case there is interest, here is a list of fixes that are being flagged as uninstalled.
KB951748 -> KB951163-oro hotfix (DNS Spoof)
KB958655 -> KB967756-oro hotfix (Update Windows Installer 4.5)
KB968537 -> KB972483-oro hotfix -> KB971250-oro hotfix (Kernel)
KB970653 -> KB974176-oro hotfix (Timezone Update)
KB961501 -> KB972483-oro hotfix (Print Spooler)
KB956744 -> KB958106-oro hotfix -> KB967885-oro hotfix -> KB972828-oro hotfix (RDP 6.1)
These hotfixes can also be obtained from
Edited by click-click, 28 October 2009 - 01:12 AM.