Messages

May I suggest to your techs, to look in the powershell detection script structure, and add hash-type parameter and function to deal with file attribute detection (to match what ConfigMgr offers) much like you have a registry hash-parameter and function?

Bug - Adobe Digital Editions is not updating,
from
4.5.11.187212 released 2019,
to
4.5.11.187303 released 2020-04-14

We are using Config Manager (enterprise)

Problem is that the DisplayVersion, and File version are both 4.5.11 in both versions, so the detection method does not distinguish between them.  The only way to tell them apart is to look at the installed EXE, "C:\Program Files (x86)\Adobe\Adobe Digital Editions 4.5\DigitalEditions.exe", and compare the Modified date.

I looked at the parameters in the Powershell detection script, and there does not seem to be any way to seed possible file modified date(s) (ConfigManager can take a range).

Can this be fixed, so that Adobe Digital Editions Application Detection can see that the application needs updating?

Or, what are the implications if I just manually replace the powershell detection script with good-old-fashioned hand-crafted detection rule types that we previously had working (before we subsribed to PMPC), and leave the rest in place, until you can come up with a fix?

Thanks.