(imported topic written by SystemAdmin)
We’re seeing a lot of failures on MS09-062 (Reference #906281).
I attempted to manually deploy the download to several devices reporting the fixlet as relevant.
Error received is: “The expected version of the product was not found on the system.”
(imported comment written by ggerling91)
We are also seeing failures with MS09-062. Only with the 2 fixlets below.
MS09-062: Vulnerabilities in GDI+ Could Allow Remote Code Execution - Visual Studio 2008 Service Pack 1
MS09-062: Vulnerabilities in GDI+ Could Allow Remote Code Execution - Groove 2007 Gold/SP1
The other fixlets for MS09-062 are working fine.
(imported comment written by SystemAdmin)
Any update on this? This fixlet shows as our most applicable, but spot checking indicates these are all false positives.
Is there any additional information I could gather to help improve the relevance?
(imported comment written by SystemAdmin)
I didn’t see these posts over here in BES Deployment, but we are having the same issue. I posted the issue over in Patch Management forum.
(imported comment written by liuhoting91)
ggerling: We’ve published changed for the Visual Studio 2008 SP1 and Groove 2007 Gold/SP1. Hopefully that will get rid of the failures you’ve been experiencing…
mikelocklar: I have a few questions that should get us started looking into this problem: What version of office do you have installed on systems that seem to be showing up as relevant? Besides the main office suite, do you have any other office applications installed on those machines? What specific office suite have you installed?
(imported comment written by wu.roger91)
We have pcs that have Office 2003/2007, Project 2007, Visio 2002/2007. The MS09-062 - compatibility pack for 2003 is detecting relevant but fails to install due to wrong version pop-up when run locally. Would there be conflict in creating an accurate detection that looks for the shared file they may be using? In this scenario, the ms patch may also be confused as to what the version is installed to be applicable.
(imported comment written by SystemAdmin)
The largest batch of false positives are Office 2k7. Some of these devices may have Project and/or Visio installed. The only other oddity in our environment is that many of the Office 2k7 installations have Access 2k3 installed instead of Access 2k7.
(imported comment written by akummer)
Any news on that?
See also here: http://forum.landesk.com/support/thread/7779;jsessionid=F342F0C8DA178B05B7A906F529861779
Landesk did something…
It might be a version conflict with visio viewer or MS project.
(imported comment written by liuhoting91)
Sorry for the late reply. I usually check just the Patch Management forum topic, so that’s where you should throw these types of topics.
I think in general when you start getting into machines that have more than one instance of office installed, or Visio 2002/2007, you start running into shared files between the two sets of products overwriting one another, which confuses Microsoft’s products (the subject of many many known issues Microsoft Knowledge Base articles). These are a lot tougher to resolve when simply applying the patches manually with Microsoft doesn’t work properly.
Confused or not, our relevance still should be pointing you to the existence of vulnerable files on your system though.