We've been using SMS 2.0 SUS since September 2003. The clients have always reported back within a few hours that an update is needed each time the mssecure.cab is updated.
Everything has been working fine until the Jan 14th update of the mssecure.cab. On the list of the update MS04-003 (832483) applies to all computers in the domain, the mssecure.cab shows this update, but none of the computers in the domain (800+) report as needing this update.
When I run MS Baseline Security analyzer by itself it reports that the update is needed. Therefore I don't know why SMS SUS is not seeing it.
We've been running the sms sus security update in expedited mode to hopefully force the new update to be seen, but to no avail.
Here's what I've done to troubleshoot this problem so far.
1. Redownloaded the mssecure.cab, redeployed it, and updated all sites with the update.(this was done to eliminate the idea the the original one might be corrupted.
2. Forced the expedited security update to run again. Waited a day for the clients to report back.
3. Checked %systemroot%\system32\vpcache\package#\1033 to insure the correct mssecure.cab was on a few selected computers, and it's reporting the correct version of mssecure.cab.
At this point I am stuck, so if anyone has suggestions on what I can do to correct this please respond.
Everything has been working fine until the Jan 14th update of the mssecure.cab. On the list of the update MS04-003 (832483) applies to all computers in the domain, the mssecure.cab shows this update, but none of the computers in the domain (800+) report as needing this update.
When I run MS Baseline Security analyzer by itself it reports that the update is needed. Therefore I don't know why SMS SUS is not seeing it.
We've been running the sms sus security update in expedited mode to hopefully force the new update to be seen, but to no avail.
Here's what I've done to troubleshoot this problem so far.
1. Redownloaded the mssecure.cab, redeployed it, and updated all sites with the update.(this was done to eliminate the idea the the original one might be corrupted.
2. Forced the expedited security update to run again. Waited a day for the clients to report back.
3. Checked %systemroot%\system32\vpcache\package#\1033 to insure the correct mssecure.cab was on a few selected computers, and it's reporting the correct version of mssecure.cab.
At this point I am stuck, so if anyone has suggestions on what I can do to correct this please respond.