Monday, December 12, 2011 8:00 PM
We use MBSA 2.2 weekly to scan all our windows servers for missing updates, patches, etc. For most of the machines (100+) it works just fine. However, I am having intermittant issues with one server that sometimes scans normally and others generates an error.
The error has occured 3 of the last 5 weeks. But, it doesn't happen consistantly. So, it might be fine for one week, error the next and be fine the one after that.
The error is:
Computer has an older version of the client and security database demands a newer version. Current version is 7.4.7600.226 and minmum required version is 22.214.171.12478.
Please note the version numbers in the error message. I didn't invert those. The scan is scripted, from a remote box and works fine on our other servers. We have tried updating WUA on the server and that made not difference. The server is WS2003 SP2. Please, let me know if you have any ideas or need more information. I'm running out of hair to pull.
Tuesday, December 13, 2011 9:49 AM
Thank you for posting in the MBSA forums!
This error is misleading by suggesting the WUA client on the target machine has too low of a version. In reality, this is a bad error within MBSA that actually indicates MBSA cannot reach the WUA client on the remote machine.
There are a number of things that need to be checked. You may want to review these items from the MBSA FAQ:
Confirm the Automatic Update service is enabled and running on both the MBSA and the target machines
Search for the section in the FAQ that details DCOM troubleshooting to ensure a DCOM connection can be established to the remote machine
Check the FAQ item titled, "When attempting to scan a remote machine, why do I see the error "Cannot deploy security metadata (0x00000003)"?
I beleive one of those should help resolve the connectivity issue. Why this is sporadic, I'm not sure. I hope that helps.
Doug Neal - Microsoft Update and MBSA
- Marked As Answer by Doug NealMicrosoft Employee Wednesday, December 14, 2011 7:15 AM