Completed continue if {(size of it = 9212072 AND sha1 of it = “e912695e0c2fbe068a8fae5ef3ea9b8876535e27”) of file “Office2007-kb2509488-fullfile-x86-glb.exe” of folder “__Download”}
Yes, it’s the only thing that’s currently being identified as outstanding. Funny, that I’m actually running Office 2003 Small Business. Ran the “Repair” for Office successfully, but didn’t help. Can’t find any hint on where the problem lies.
we are seeing this as well for this patch. The action script details show completed but the Exit Code shows 17031 for most of the ones that failed. We deployed this patch to about 5000 machines as part of a baseline and the failure rate appears to be about 3% of the machines. This is a little bit higher than our usual failure rate but not overly alarming.
Researching the 17031 error and from what I found on Google is that it usually means that a prerequisite may not be installed (detection: Invalid Baseline).
OPatchInstall: Property ‘SYS.PROC.RESULT’ value ‘17031’
This code indicates that the version of the Office installation does not match the version that is expected. The patch is not applied.
I checked a few of the failures and some of them do have Office 2007 SP2 installed, a few did not. Since our failure rate was low enough I did not really research it much further than finding the error code and what that means.
do these systems have compatibility pack installed?
Some do and some dont
I spot checked ~15 machines and it looked like the ones that failed that have Office 2007 SP2 installed did not have the compatibility pack (except for one). Most of the machines that did have the compatibility pack installed did not have SP2 installed.
from running the update manually I get “The expected version of the product was not found on the system†. Then why is it showing relevant for the computer?
we’ve done some research on this and it looks like SP2 and compatibility pack are required, as tsikma is seeing. A baseline approach might do the trick:
baseline relevance: office 2007 installed
component: 64001
component: 64003
optional component: MS10-087 (superseded)
component: MS11-023
We’re looking into how best to modify the stock fixlets to reflect this without hiding existence of the vulnerability.
this issue should be corrected now. Per the content modification announcement:
“Fixlet 1102311 has been modified to check for the Office Compatibility Pack 2007. If it exists, but it’s outdated, the fixlet will fail. A second action has been added to automatically install the updated version of the compatibility pack if an outdated version of it is found on systems that are relevant for MS11-023.”
Is there any update available for the above mentioned issue as i have many machines failing this fixlet resulting in compliance issues and i have the same kind of issue with one more patch MS11-045.
We have Office Compatibility SP2 installed on our machines. Seems to have some issues with the relevance code written which makes the machine applicable but when try to install the same fails due to version mismatch.
Please confirm if any updates are available further on the same.
Here is what I’ve found. The machines that are failing have Office 2007 SP2 installed but not the compatability pack. The problem is the install of the compatability pack using BigFix fails. If I go to the machine and do a manual install it will work. So something appears to be wrong with the comp pack install part of BF. Looking at the file that the BigFix action is downloading from Microsoft it doesn’t appear to be the same as the one when you go to Microsoft’s site and look for compat pack for Office 2007 SP2.
Another thing I don’t understand about this one is that according to Microsoft’s website it doesn’t say anything about the compatability pack being vulnerable. It even goes on to say that Compatability Pack SP2 is not affected.
I have machines that have Office 2007 SP2 that say they are relevant but when I try to push out the patch neither of the actions work. They come back as a fail. I checked one of these machines and it doesn’t even have the Compatibility pack installed. So just to see what would happen I tried to manually install Ms11-023 and it said not expected version. I then installed the the Compatibility pack from the second link then tried again. Same result. I then tried to install the Compatibility Pack SP2 from the first link and it wouldn’t install because there was already a newer version.
Any idea what the heck is going on with this patch?
We are having a similar issue here with Office installs… In one of the previous posts you mentioned that installing the compatibility pack resolved your issue, but in one of the later ones you said that that fix was no longer. can you please confirm if compatability pack installation resolves the issue?