MS08-013 MS Office Patch

Usage and Config Patch
1

(imported topic written by SystemAdmin)

Hi,

MS Patch is relevant when deploy it and action reports back failed but View Action Info all the Action Script is show Completed.

Below is the patch deploy show failed:-

  1. MS08-14_Valnerabilities in Microsoft Excel Could Allow Remote Code Executio - Office 2000 SP3 (Local Install).bes

  2. MS08-13_Valnerabilities in Microsoft Excel Could Allow Remote Code Executio - Office 2000 - WIndows NT_20000_XP_2003 (Network Install).bes

3.MS08-13_Valnerabilities in Microsoft Excel Could Allow Remote Code Executio - Office 2000(Local Install).bes

4.MS08-13_Valnerabilities in Microsoft Excel Could Allow Remote Code Executio - Office 2000 SP3 (Local Install).bes

Thank You

2

(imported comment written by BenKus)

Do these help?

http://support.bigfix.com/cgi-bin/kbdirect.pl?id=129

http://support.bigfix.com/cgi-bin/kbdirect.pl?id=68

Ben

3

(imported comment written by SystemAdmin)

I have stopped it and deleted the action and redeploy again, still encounter the same problem

4

(imported comment written by Harald.Zarakowitis)

We experience the same problems with the patch MS08-016. The action scripts runs without failure but after that reboot the patch is still relevant and thus the status is Failed.

Does somebody have the same problem?

Some problem with the relevance maybe?

edit: we redeployed the action several times without success. (First with baselines, after that we did a single rollout)

Regards,

Harald

5

(imported comment written by MY6591)

We will investigate and let you know.

6

(imported comment written by jeremylam)

Which Fixlet message specifically for MS08-016? Do you have multiple Office products installed, such as both Office 2000 and Office 2003?

7

(imported comment written by SystemAdmin)

Hi,

Me too… waiting the solution…

8

(imported comment written by Harald.Zarakowitis)

Jeremy Lam

Which Fixlet message specifically for MS08-016? Do you have multiple Office products installed, such as both Office 2000 and Office 2003?

Yes, we figured that out too now. It is the case, that on most of our clients we have Office 2002, but also Outlook 2003 installed. The relevance of the patch does not consider that.

A colleague of mine came up with the following relevance to fix the problem:

exists folder (value 
"CommonFilesDir" of key 
"HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion" of registry as string & 
"\Microsoft Shared") whose (exists folder 
"Smart Tag" whose (exists file 
"IETAG.dll" whose (version of it = 
"11" and version of it < 
") of it) of it OR exists folder "OFFICE11
"  whose (exists file 
"MSO.dll" whose (version of it < 
"11.0.8202.0") of it) of it)

It would be great (and I mean really great) if the fixlets are changed to consider multiple office versions, because we rely on extensive custom web reports to report the patch status of specific patch, which is totally messed up because of this.

However, it does not seem to affect all Office patches.

9

(imported comment written by jeremylam)

Harald.Zarakowitis

It would be great (and I mean really great) if the fixlets are changed to consider multiple office versions, because we rely on extensive custom web reports to report the patch status of specific patch, which is totally messed up because of this.

However, it does not seem to affect all Office patches.

Hi Harald,

I believe this problem only exists on Microsoft patches that update shared components, but due to the large number of Office products that may contain their own version of the file in question, it is not an easy problem to solve. We will address this problem more closely in the future.