anyone do the new ms updates?

[Bill Sanderson]

I've gone back to two of the XPSP3 machines--an old slow one, and a more
modern reasonably fast one.

I installed MBSA 2.1 and did a scan of each machine with default settings.
On each of them nothing was found missing with regards to patches. On both,
the app found an incomplete install. I rebooted both machines. On the
newer one, a Flash installation appeared on reboot. On the older one,
nothing like that appeared.

Re-ran MBSA, and the new one shows the partial install cleared--the old one
still shows it.

Will test some more machines--if something is masking the need for these
patches on my machines, it is pretty slick. I may go read the KB articles
first to see if I can figure out what's going on that way.

 

[Bill Sanderson]

I've now read the bulletins.

I first downloaded the IE7 cumulative update to one of the affected
machines. Somewhat to my surprise, it installed just fine.

I followed up with the rest of the applicable updates. The ADAM patch did
not install, probably because ADAM has never been installed on that machine.
Otherwise, they all installed without issue. MBSA, when run after all
patches were installed and the machine rebooted, still says all is fine.

In fact, I tweaked administrators and password expiry and got a green
shield.

Something is definitely wrong here, and I think before I muddy the waters
more, I'm going to find the time to take this to Microsoft PSS.

 

[Donald Anadell]

I've now read the bulletins.

I first downloaded the IE7 cumulative update to one of the affected
machines. Somewhat to my surprise, it installed just fine.

I followed up with the rest of the applicable updates. The ADAM patch did
not install, probably because ADAM has never been installed on that
machine. Otherwise, they all installed without issue.

MBSA, when run after all patches were installed and the machine rebooted,
still says all is fine.

Hi Bill,

That is a strange one. The only thing that comes to mind with regard to
MBSA not detecting the need for the Updates on your machine is that you were
possibly getting an older version of "Mssecure.xml" from the server(maybe
May's version of that detection file)?

You would think that if MBSA were getting the June version of
"Mssecure.xml" from the web that it would have detected the need for the
Updates on your machine.

Good luck,

Donald Anadell

 

[Bill Sanderson]

It was a fresh install of MBSA, with a fresh download of the XML file.

There's a new security advisory today from Microsoft:

http://www.microsoft.com/technet/security/advisory/954474.mspx

indicating a problem with System Center configuration manager distributing
updates to SMS. This has the effect that I am seeing, but my machines are
completely unmanaged except for me, and my wife's XP Home is not domain
joined, removing yet another variable.

 

[Bill Sanderson]

I've solved my mystery about machines failing to update. It is apparently
due to the presence of beta code on these systems--so this is not an issue
that will happen to most Windows XP users.

I've taken steps to enable these systems to update properly, and passed the
information on within Microsoft.

 

[Donald Anadell]

I've solved my mystery about machines failing to update. It is apparently
due to the presence of beta code on these systems--so this is not an issue
that will happen to most Windows XP users.

Thanks for the feedback Bill, glad you able to resolve the issue.

Good luck,

Donald Anadell