Using MBSA 2.2 getting error 'Cannot load security CAB file" when attempting to scan any remote systems

Question

Could scan all remote servers previously from same sources and version.  Replaced/updated all cabs and other files associated (C:\Documents and Settings\<username>\Local Settings\Application Data\Microsoft\MBSA\Cache) with no change.  Removed/re-installed
MBSA 2.2 with not effect.
Local scans appear to function fine, but do not wish to download MBSA on EVERY system we need to scan.
Settings for remote scan are: Check for security updates>Configure computers for Microsoft
Update and scanning prerequisites>Advanced Update Services
options:>Scan using
Microsoft Update only
Have attempted from different systems/OS's, with same results.  Checked firewall for any blocked traffic from both host and scanner, no entries.
Checked Technet/blogged for about two hours, without any positive results. Please advise/assist.
Regards,
AJ Lebeau
MCSE, MCP, MCP+I, CNA, ACNA, A+
Server Administrator
Progenics Pharmaceuticals
[email protected]
[phone]

Answer 1

Thank you for sending this to the MBSA forums!
If you haven't already, you may want to check the MBSA FAQ located here:
http://technet.microsoft.com/en-us/security/cc184922 specifically under the sections titled, "How can I scan a computer that is protected by a firewall" (to resolve potential DCOM connectivity issues), and "When attempting to scan a remote machine,
why do I see the error 'Cannot deploy security metadata?"
This is also a very misleading error message since the problem could be due to connectivity to the target (client) machines - nothing relating to the CAB file.  In any circumstance, you should not need to install MBSA on all of the target machines to
successfully assess their security state. 
Possible solutions include
Confirm the latest WUA client is installed on all target machines (with the files you've already placed in the cache directory, you can simply check the scan option to "Configure computers for Microsoft
Update and scanning prerequisites" - which will update and re-register each target machine with the latest WUA client and the ability to respond to requests from MBSA.
Check whether the target machines have limited disk space (unlikely)
Check DCOM settings on both the server - but more likely due to the failure to remotely scan - the target machines.
Change the scan options to further troubleshoot.  Specifically, 'Check for security updates' option uses a DCOM connection to the target WUA client while the other scan settings 'Check for weak passwords, etc." use specific UDP/TCP ports as indicated
in the System Requirements section of the MBSA help file and the MBSA FAQ.  Also use the 'Advanced Update Services options' to determine whether WSUS connectivity may be at issue.
Please let me know if that helps.
Doug Neal - Microsoft Update and MBSA