A community where customers and the community can provide feedback to make a better product for everyone! For more details on how we prioritize request, please see:
Kofax has released version 5.0 of Kofax Power PDF. Previous versions (4.0 and 4.1) are already in the catalog. We would like to formally request the 5.0 fix-packs be added to the Patch My PC Catalog.
It is should be funcationally the same as the 4.0 and 4.1 fix packs and require minimal effort to adapt to the catalog.
Yeah, the issue is that DisplayVersion doesn't successfully cast to System.Version. Our detection scripts in Intune need them to be valid version numbers (with j segments in the structure, 6)
Thanks for replying Adam! I think the display version does get updated here- SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
I attached a screenshot showing it in my registry.
Yes I was taking the version from the file name and comparing it to what the registry shows so that it only runs the install if the file version is older than what the registry shows (what's currently installed).
This could probably be handled better by a custom detection method PowerShell script too.
Hi Philip. The vendor unfortunately doesn't write to the registry in a typical way. In WSUS, we have this flexibility to look elsewhere in the registry beyond SOFTWARE\(WOW6432NODE\)Microsoft\Windows\CurrentVersion\Uninstall. However for Intune, we are somewhat limited to only looking in these key paths for installed software.
From memory, the vendor doesn't correctly update DisplayVersion in these registry keys. From reading your script, I can see you extract the version file from the file name of the installer itself.
It looks like this is not available for Intune, only for Config Manager. I was able to create an update in Intune using a win32 app. I created a install.intunewin with the Intunewinapputil.exe and have a powershell script for the install and the detection method looks for the following file (currently fix pack 8) - C:\Program Files (x86)\Kofax\Power PDF 50\FixPack-5.0.0.8.0.23214.npi
I'm attaching the install.ps1. You can probably come up with better logic than me, but it should only install if Kofax Power PDF is installed and if the installed fixpack is older than the one in the file.
Yeah, the issue is that DisplayVersion doesn't successfully cast to System.Version. Our detection scripts in Intune need them to be valid version numbers (with j segments in the structure, 6)
Thanks for replying Adam! I think the display version does get updated here- SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\
I attached a screenshot showing it in my registry.
Yes I was taking the version from the file name and comparing it to what the registry shows so that it only runs the install if the file version is older than what the registry shows (what's currently installed).
This could probably be handled better by a custom detection method PowerShell script too.
Does this help?
Hi Philip. The vendor unfortunately doesn't write to the registry in a typical way. In WSUS, we have this flexibility to look elsewhere in the registry beyond SOFTWARE\(WOW6432NODE\)Microsoft\Windows\CurrentVersion\Uninstall. However for Intune, we are somewhat limited to only looking in these key paths for installed software.
From memory, the vendor doesn't correctly update DisplayVersion in these registry keys. From reading your script, I can see you extract the version file from the file name of the installer itself.
It looks like this is not available for Intune, only for Config Manager. I was able to create an update in Intune using a win32 app. I created a install.intunewin with the Intunewinapputil.exe and have a powershell script for the install and the detection method looks for the following file (currently fix pack 8) - C:\Program Files (x86)\Kofax\Power PDF 50\FixPack-5.0.0.8.0.23214.npi
I'm attaching the install.ps1. You can probably come up with better logic than me, but it should only install if Kofax Power PDF is installed and if the installed fixpack is older than the one in the file.
Any chance PMPC could add this for us?
Thanks for submitting the idea Adam, Ill take a look!