Win2000 SP4 Update Rollup 1 reporting issue

I am having the issue with several Win2k systems reporting to my WSUS server
that the Update Rollup 1 is needed for installation, but the systems had
already had this update installed. Even after it has been downloaded from
WSUS and installs with reboot, it still reports the same status. I manually
uninstalled the rollup on one of the systems, and let it reinstall on its
own, but same result.

A common factor with these systems is that I believe they all may have had
the v1 release of the Update Rollup 1 installed before they were configured
to use the internal WSUS server, which is deploying v2.

I ran MBSA 1.2 against one of the systems to check the MDAC and MSXML
versions as suggested from another posting. The MSXML Parsers were out of
date, so I updated version 4.0 to SP2, per the recommendation (I did not
update 2.x and 3.x). MDAC reported no updates were needed. After a reboot,
the system continues to report that Update Rollup 1 is needed.

I have three systems currently reporting this, and I have not rolled out
WSUS to the entire company yet, so I anticipate many more. Is there a
solution for this problem? Should I just "not approve" the Update Rollup 1?
Thanks

"Brandon McGarvey" <> wrote in message
news:A1F67130-AC3C-4A8B-8F1B-
....
> I ran MBSA 1.2 against one of the systems to check the MDAC and MSXML
> versions as suggested from another posting. The MSXML Parsers were out of
> date, so I updated version 4.0 to SP2, per the recommendation (I did not
> update 2.x and 3.x).


Update MSXML 3.0 too anyway.

Dave Hawley referred to that one too.

<quote>
> In fact MSXML 4.0 has updated to SP7, which was only issued today.
> MBSA 1.2.1 now says that it needs to be SP5, which it says is the latest
> version!
> Go figure! I guess the database hasn't been updated yet.......
>
</quote>

E.g. I suspect the above 4.0 was a typo for 3.0
However, it is not clear if he installed that newer service pack
at the same time. In any case it couldn't hurt and it might help.


Good luck

Robert Aldwinckle
---

Updating 3.0 to SP7 seemed to worked on one of the problem systems. I will
have to try it on the other systems as well. Thanks

"Robert Aldwinckle" wrote:

> "Brandon McGarvey" <> wrote in message
> news:A1F67130-AC3C-4A8B-8F1B-
> ....
> > I ran MBSA 1.2 against one of the systems to check the MDAC and MSXML
> > versions as suggested from another posting. The MSXML Parsers were out of
> > date, so I updated version 4.0 to SP2, per the recommendation (I did not
> > update 2.x and 3.x).
>
>
> Update MSXML 3.0 too anyway.
>
> Dave Hawley referred to that one too.
>
> <quote>
> > In fact MSXML 4.0 has updated to SP7, which was only issued today.
> > MBSA 1.2.1 now says that it needs to be SP5, which it says is the latest
> > version!
> > Go figure! I guess the database hasn't been updated yet.......
> >
> </quote>
>
> E.g. I suspect the above 4.0 was a typo for 3.0
> However, it is not clear if he installed that newer service pack
> at the same time. In any case it couldn't hurt and it might help.
>
>
> Good luck
>
> Robert Aldwinckle
> ---
>
>
>
>