Bugger. The new MBSA 2.x tools seems not capable of detecting administrative Office XP installations. Is that correct? After the download of the latest windowsupdateagent20 initiated by MBSA 2.0.1, a revisit to Windows Update tells me I'm missing 13 updates for Office XP. That's four more than MBSA 2.0.1's total and the remaining list of nine is not equivalent between the twos. Office Update

I'm late to this game and unhappy to lose mbsacli.exe /hf I hate it when developers add feature creep while losing backwards compatibility. Not to mention just plain broken apps. Here we've seemingly reverted to checking something other than file checksums/versions for Office XP. These were reported with mbsacli.exe /nd /nvc /wi /catalog [location] filename using mbsacli.exe ver. 2.0.6706

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 SUPPORT COMMUNICATION - SECURITY BULLETIN Document ID: c01460710 Version: 1 HPSBST02336 SSRT080071 rev.1 - Storage Management Appliance (SMA), Microsoft Patch Applicability MS08-026 to MS08-029 NOTICE: The information in this Security Bulletin should be acted upon as soon as possible. Release Date: 2008-05-19 Last Updated: 2008-05-19