I am using Adobe MSP file with the Adobe Systems, Inc. Packages.
Okay, so that's an ADOBE-produced package, and you probably should be having this conversation with Adobe.
As noted, they have an established history of screwing up their packages.
When I go to Adobe Systems, Inc. Packages and create the Adobe 10.1.10 package
STOP! Why are you *creating* a package??? Adobe provides a catalog of Adobe Acrobat update packages ready to use!
Furthermore, Patch Manager is fully capable of synchronizing that catalog. All you need to do is turn it on.
HOWEVER... it seems that Adobe forgot to define PreRequisite Rules in their package definition for the Acrobat 10.1.10 update.... so it probably doesn't work correctly.
(It certainly doesn't work *efficiently*, even if it does work correctly.)
They made the same mistake in the Acrobat 10.1.9 package, but they properly defined the ruleset in the Acrobat 10.1.8 package.
I would suggest synchronizing the Adobe Acrobat 10 catalog, and then duplicating the Acrobat 10.1.10 package and adding back this missing pair of Processor Architecture rules.
I would also suggest adding a test for the presence of Adobe Acrobat v10. (There's no need for the WUAgent to cache and evaluate an Acrobat patch if Acrobat v10 is not installed!)
The final logic would look like this:
When ALL of the following...
Registry Key EXISTS (HKLM\Software\Adobe\Acrobat)
When ANY of the following...
Processor Architecture=x86
Processor Architecture=x64
Note, there may be a v10-specific registry key (e.g. HKLM\Software\Adobe\Acrobat\10 or HKLM\Software\Adobe\Acrobat10) -- you'll definitely want to test for the Acrobat TEN key so you can also eliminate Acrobat v8 and Acrobat v9 systems.
with the Adobe MSP file I do not get the Applicability rules and Installed Rules.
Ahh.. correct. My apologies. With MSP files you cannot specify Applicability Rules or Installed Rules because they are fully contained within the MSP.