KB873354 and KB873355 Verification??

[Shannon]

I'm trying to writ a wsf script for my company to verify if the KB873354 and
KB873355 patches have been installed. For KB873352 I used the IETAG.DLL and
verified the version. Does anyone know what files are updated with the
Project and Visio patches? Perhaps one from each I can use as verification
in my script?

 

[Bob Buckland ?:-\)]

Hi Shannon,

All three of those updates are related to
MS Security Bulletin 05-005
http://microsoft.com/technet/security/bulletin/ms05-005.mspx

KB873355 Project 2002 only updates MSO.DLL
KB873352 Office XP update modifies MSO.DLL and IETAG.DLL.
KB873354 Visio 2002 update modifies MSO.DLL and GDIPLUS.DLL
(supercedes MS04-028)

The MSO.DLL file replacement is the same version in each.

You could use both SMS and the MS Baseline Security Analyzer
or the Office Update Inventory tool to verify the status
as well. The links are in the security bulletin.

What is the script that you're using?

======
I'm trying to writ a wsf script for my company to verify if the KB873354 and
KB873355 patches have been installed. For KB873352 I used the IETAG.DLL and
verified the version. Does anyone know what files are updated with the
Project and Visio patches? Perhaps one from each I can use as verification
in my script? <<

 

[Shannon5872]

Because of confidentiality issues I am not able to post my script here..but
to summerize it basically looks at the version of IETAG.DLL and if it doesn't
match 10.0.6731.0 then it kicks off the update from a centralized
administrative install point.

So if they all update MSO.DLL is it necessary to run all the patches or can
I just get away with running the Office Update and Visio patch to update the
IETAG.DLL and GDIPLUS.DLL?

 

[Bob Buckland ?:-\)]

Hi Shannon,

My understanding is that it's recommended to run
all of the updates for resiliency. Otherwise
a repair or reinstall from a nonupdated source location
could 'restore' the older version of a file (i.e. you'd
be in an 'unmanaged' state.

=======
Because of confidentiality issues I am not able to post my script here..but
to summerize it basically looks at the version of IETAG.DLL and if it doesn't
match 10.0.6731.0 then it kicks off the update from a centralized
administrative install point.

So if they all update MSO.DLL is it necessary to run all the patches or can
I just get away with running the Office Update and Visio patch to update the
IETAG.DLL and GDIPLUS.DLL? >>
--
Let us know if this helped you,

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

Office 2003 Editions explained
http://www.microsoft.com/uk/office/editions.mspx

 

[Shannon5872]

Ok..so if I am to push out these updates via a silent windows script file is
it advisable for me to verify the versions of IETAG.DLL and GDIPLUS.DLL when
the script decides if the updates are needed on a particular machine? I
guess I'm looking to create some kind of a flag in the script to avoid it
running the updates on the same machine over and over when the end user
reboots other than creating a file flag on the end user's machine.